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

Detecting IIS

Good Morning,

My name is Erin. When attempting to install SQL Server Express on Windows XP Home Edition Service Pak 2, the installation freezes at "Detecting IIS...". I have been bopped around Microsoft Support since Monday. I even opened a case, but I have no success. Does anyone have any ideas on how to get around this problem? Any help would be greatly appreciated. Great question Erin.

There are several threads in the Setup Forum that may help.

Check out
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130608&SiteID=1
and
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=54363&SiteID=1|||I made it through the installation of Net.Framework 2.0. with the SDk kit. I've installed the SQLServer, Express without any problems. Now I need to configure the Startup kit for SDK, and Net Framework 2.0. I finally got the configuration wizard, and I am asked if I have the IIS installed on my computer. I don't think I can get the IIS on the Home, ed. There may be a substitute. I ran into a support I believe some time ago. I am looking now. Thought I was alone where this matter is concerned. Will get back if I find the support for IIS.

Detecting IIS

Good Morning,

My name is Erin. When attempting to install SQL Server Express on Windows XP Home Edition Service Pak 2, the installation freezes at "Detecting IIS...". I have been bopped around Microsoft Support since Monday. I even opened a case, but I have no success. Does anyone have any ideas on how to get around this problem? Any help would be greatly appreciated. Great question Erin.

There are several threads in the Setup Forum that may help.

Check out
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130608&SiteID=1
and
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=54363&SiteID=1|||I made it through the installation of Net.Framework 2.0. with the SDk kit. I've installed the SQLServer, Express without any problems. Now I need to configure the Startup kit for SDK, and Net Framework 2.0. I finally got the configuration wizard, and I am asked if I have the IIS installed on my computer. I don't think I can get the IIS on the Home, ed. There may be a substitute. I ran into a support I believe some time ago. I am looking now. Thought I was alone where this matter is concerned. Will get back if I find the support for IIS.