Detecting Installed IIS - installing SQL 2005 Standard

I've seen lots of posts but few if any solutions to this apparently common problem.

I'm experiencing a variant - installing SQL 2005 (RTM) on a brand new machine with Server 2003 Standard Ed. SP1, the setup program frequently pauses on steps identified as "Detecting Installed IIS". Setup eventually moves on, but it's taking ages to finish the install.

I've installed this exact version of several identical machines, but this is the first where I've encountered this behavior.

Does anyone have any input on what's really happening here and what to do about it?I guess no one really knows... :)

In my case, I believe that the cause was a DNS issue that caused all name resolution requests to time out. Others have reported issues related to firewalls or antivirus software.|||

Thanks for posting your solution, Carl. What was the DNS issue you were hitting? Did you have to change some settings to get it working? And approximately how long was the slow install? Hours? This issue has appeared a few times on here and I don't think we have a good answer yet other than DNS/firewall/anti-virus issues.

Thanks,
Sam Lester (MSFT)

|||

Now this is stressing the way-back machine!

The slow install was, as I recall, something on the order of 2-5 minutes each time something tried to detect IIS (and it happens several times during the install).

If I recall, the solution was to configure TCP/IP on the install machine to use the local domain controller for DNS rather than my upstream providers' DNS server.

Detecting Installed IIS - installing SQL 2005 Standard

I've seen lots of posts but few if any solutions to this apparently common problem.

I'm experiencing a variant - installing SQL 2005 (RTM) on a brand new machine with Server 2003 Standard Ed. SP1, the setup program frequently pauses on steps identified as "Detecting Installed IIS". Setup eventually moves on, but it's taking ages to finish the install.

I've installed this exact version of several identical machines, but this is the first where I've encountered this behavior.

Does anyone have any input on what's really happening here and what to do about it?I guess no one really knows... :)

In my case, I believe that the cause was a DNS issue that caused all name resolution requests to time out. Others have reported issues related to firewalls or antivirus software.|||

Thanks for posting your solution, Carl. What was the DNS issue you were hitting? Did you have to change some settings to get it working? And approximately how long was the slow install? Hours? This issue has appeared a few times on here and I don't think we have a good answer yet other than DNS/firewall/anti-virus issues.

Thanks,
Sam Lester (MSFT)

|||

Now this is stressing the way-back machine!

The slow install was, as I recall, something on the order of 2-5 minutes each time something tried to detect IIS (and it happens several times during the install).

If I recall, the solution was to configure TCP/IP on the install machine to use the local domain controller for DNS rather than my upstream providers' DNS server.

Detecting Installed IIS - installing SQL 2005 Standard

I've seen lots of posts but few if any solutions to this apparently common problem.

I'm experiencing a variant - installing SQL 2005 (RTM) on a brand new machine with Server 2003 Standard Ed. SP1, the setup program frequently pauses on steps identified as "Detecting Installed IIS". Setup eventually moves on, but it's taking ages to finish the install.

I've installed this exact version of several identical machines, but this is the first where I've encountered this behavior.

Does anyone have any input on what's really happening here and what to do about it?I guess no one really knows... :)

In my case, I believe that the cause was a DNS issue that caused all name resolution requests to time out. Others have reported issues related to firewalls or antivirus software.|||

Thanks for posting your solution, Carl. What was the DNS issue you were hitting? Did you have to change some settings to get it working? And approximately how long was the slow install? Hours? This issue has appeared a few times on here and I don't think we have a good answer yet other than DNS/firewall/anti-virus issues.

Thanks,
Sam Lester (MSFT)

|||

Now this is stressing the way-back machine!

The slow install was, as I recall, something on the order of 2-5 minutes each time something tried to detect IIS (and it happens several times during the install).

If I recall, the solution was to configure TCP/IP on the install machine to use the local domain controller for DNS rather than my upstream providers' DNS server.

sql

detach 6.5 compatible database in studio - HOW?

I've got two databases showing in the studio tree, but they are marked 6.5 compatible and cannot be expanded. Worse, there is no way (apparently) in the menu of either database to remove, delete or detach them.

How can I get these out of the system?

Thanks in advance.

randyv

What about using the TSQL statement for dropping / detaching the databases ? (DROP DATABASE / sp_detach)

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

No, that doesn't work because it is grayed out... It finally dawned on me that since I could not take any action directly on the database due to compatibility problems, but that the database was from 2000, there was no reason the level could not be increased.

To make sure I had no problem with the application, this is what I did. I backed up the database on the 2000 server, then restored it as a different database. Then I changed the compatibility level on that restored database to 80.

Next I backed that databased up and copied the .bak file to the other server running 2005.

Then I restored that .bak file as the existing 6.5 level database with a restore over existing database flag turned on.

Presto ! Problem solved. It is taking the long way around the problem, but there is no other option open, apparently.

|||

Try to run this transact sql script against your database:

USE databaseName
GO
EXECUTE sp_dbcmptlevel databaseName , 90
GO
EXEC sp_updatestats
GO

detach 6.5 compatible database in studio - HOW?

I've got two databases showing in the studio tree, but they are marked 6.5 compatible and cannot be expanded. Worse, there is no way (apparently) in the menu of either database to remove, delete or detach them.

How can I get these out of the system?

Thanks in advance.

randyv

What about using the TSQL statement for dropping / detaching the databases ? (DROP DATABASE / sp_detach)

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

No, that doesn't work because it is grayed out... It finally dawned on me that since I could not take any action directly on the database due to compatibility problems, but that the database was from 2000, there was no reason the level could not be increased.

To make sure I had no problem with the application, this is what I did. I backed up the database on the 2000 server, then restored it as a different database. Then I changed the compatibility level on that restored database to 80.

Next I backed that databased up and copied the .bak file to the other server running 2005.

Then I restored that .bak file as the existing 6.5 level database with a restore over existing database flag turned on.

Presto ! Problem solved. It is taking the long way around the problem, but there is no other option open, apparently.

|||

Try to run this transact sql script against your database:

USE databaseName
GO
EXECUTE sp_dbcmptlevel databaseName , 90
GO
EXEC sp_updatestats
GO

detach 6.5 compatible database in studio - HOW?

I've got two databases showing in the studio tree, but they are marked 6.5 compatible and cannot be expanded. Worse, there is no way (apparently) in the menu of either database to remove, delete or detach them.

How can I get these out of the system?

Thanks in advance.

randyv

What about using the TSQL statement for dropping / detaching the databases ? (DROP DATABASE / sp_detach)

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

No, that doesn't work because it is grayed out... It finally dawned on me that since I could not take any action directly on the database due to compatibility problems, but that the database was from 2000, there was no reason the level could not be increased.

To make sure I had no problem with the application, this is what I did. I backed up the database on the 2000 server, then restored it as a different database. Then I changed the compatibility level on that restored database to 80.

Next I backed that databased up and copied the .bak file to the other server running 2005.

Then I restored that .bak file as the existing 6.5 level database with a restore over existing database flag turned on.

Presto ! Problem solved. It is taking the long way around the problem, but there is no other option open, apparently.

|||

Try to run this transact sql script against your database:

USE databaseName
GO
EXECUTE sp_dbcmptlevel databaseName , 90
GO
EXEC sp_updatestats
GO