soneil66
asked on
Troubleshooting "Cannot create a file when that file already exists" errors in IIS when using host headers
I am trying to host multiple websites on a single server using IIS 6.0 via host headers. All of the websites are based on components of SBS 2003 and Windows 2003 SP2 including the Default Web Site, WSS 2.0 (aka "companyweb") and additional WSS 2.0 admin sites (Sharepoint Central Admin, Microsoft SharePoint Admin), and WSUS 3.0 SP1. All of these are default installations and only the Default Web Site (for OWA, OMA, Exchange, etc.) is ever really in use. I have no plans to use the additional components beyond how they currently interact on an SBS installation.
I am preparing to deploy WSS 3.0 SP1 for both local and remote access and, therefore, need this multiple website on a single server via host headers functionality to work. (I am aware of additional issues regarding configuration of SharePoint sites through Central Admin prior to IIS - but I'm not there yet.)
The Default Web Site is set to *All Unassigned*, as suggested, the rest are set to the same IP (192.168.128.1 is the private interface which is routed to a public interface, single IP address). The host headers in use for the existing additional sites are all registered as subdomains through my domain host; all point to the same static IP; all sites hosted on this server use the same port (80) and the same SSL (443), per just about every knowledge base article one finds on the net. (See attached screenshot.)
But when I go to start the sites, I get the blasted "IIS was unable to start the site. Another site may already be using the port you configured for this site. Please select a unused port for this site" error. The "Cannot create a file when that file already exists" error then appears in the Status column for each site.
I'm confused because I thought the configuration of the host headers either required or was able to function using the same ports with unique host headers. I've restarted IIS several times; I've rebooted after configuration several times; I've double-check the bindings in the Metabase Explorer and they all appear as configured. I haven't added any records to my local DNS because they've already been added/registered with my domain host.
A wildcard certificate is installed on all of the sites except the Default Web Site and "companyweb" site which maintain their original "publishing.xxx.xxx" certificates issued upon installation of SBS 2003. ISA Server 2004 SP3 is configured and running on the server - no changes have been made to this configuration.
In regards to the existing SharePoint installation - the SharePoint Central Administration site may be a holdover from a previous WSS 3.0 SP1 installation that unfortunately was broken during some early configuration stages. WSS 3.0 SP1 has been uninstalled for the moment; I thought SharePoint Central Admin site existed as part of the default SBS install and didn't want to hastily remove it. Anyway, I don't know if that variable throws something into the mix or not.
Any suggestions? I've mucked around with it enough on my own - I'm to the point where I feel a little dangerous and need assistance. :)
Much thanks.
iis-host-header-screenshot.jpg
I am preparing to deploy WSS 3.0 SP1 for both local and remote access and, therefore, need this multiple website on a single server via host headers functionality to work. (I am aware of additional issues regarding configuration of SharePoint sites through Central Admin prior to IIS - but I'm not there yet.)
The Default Web Site is set to *All Unassigned*, as suggested, the rest are set to the same IP (192.168.128.1 is the private interface which is routed to a public interface, single IP address). The host headers in use for the existing additional sites are all registered as subdomains through my domain host; all point to the same static IP; all sites hosted on this server use the same port (80) and the same SSL (443), per just about every knowledge base article one finds on the net. (See attached screenshot.)
But when I go to start the sites, I get the blasted "IIS was unable to start the site. Another site may already be using the port you configured for this site. Please select a unused port for this site" error. The "Cannot create a file when that file already exists" error then appears in the Status column for each site.
I'm confused because I thought the configuration of the host headers either required or was able to function using the same ports with unique host headers. I've restarted IIS several times; I've rebooted after configuration several times; I've double-check the bindings in the Metabase Explorer and they all appear as configured. I haven't added any records to my local DNS because they've already been added/registered with my domain host.
A wildcard certificate is installed on all of the sites except the Default Web Site and "companyweb" site which maintain their original "publishing.xxx.xxx" certificates issued upon installation of SBS 2003. ISA Server 2004 SP3 is configured and running on the server - no changes have been made to this configuration.
In regards to the existing SharePoint installation - the SharePoint Central Administration site may be a holdover from a previous WSS 3.0 SP1 installation that unfortunately was broken during some early configuration stages. WSS 3.0 SP1 has been uninstalled for the moment; I thought SharePoint Central Admin site existed as part of the default SBS install and didn't want to hastily remove it. Anyway, I don't know if that variable throws something into the mix or not.
Any suggestions? I've mucked around with it enough on my own - I'm to the point where I feel a little dangerous and need assistance. :)
Much thanks.
iis-host-header-screenshot.jpg
ASKER
Thanks for your reply. My understanding is that was the case with IIS prior to 6.0 however now, with a wildcard certificate, one can run multiple sites including SSL from a single IP address using host headers.
I would refer you to:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true
I would refer you to:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I haven't checked into this post in a week or so because I needed to gain some perspective and do some serious testing in different environments. I return now with the same link that Dov has offered above, since there are certain elements of IIS 6.0 that can only be configured through adsutil.vbs:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true
And while you can thereotically, and to a certain extent literally, host multiple web sites with a single IP in IIS 6.0...possibly in Small Business Server 2003...the real showstopper in this scenario is ISA Server 2004. See this article for an explanation of configuring ISA Server 2004 to work with Windows Sharepoint Services 3.0 using SSL on a single IP with host-to-host headers:
http://technet.microsoft.com/en-us/library/cc713327.aspx
(I feel obliged to leave a trail of breadcrumbs should anyone else come down this path...)
Because the server components are somewhat glued together in SBS, limitations arise when configuring web listeners (my head still hurts from thinking about it). Because you have to maintain the Default Web Site in SBS 2003 for OWA, OMA and RWW, it becomes difficult if not impossible to complete this configuration. I do believe it would work on a stand-alone IIS 6.0 server however (which is what the article is written for).
The best solution here when trying to host WSS 3.0 on SBS 2003 with a proper domain name and internet facing application extension is...buy another NIC. :0) (I already have the additional static IPs.)
Also, in terms of hosting multiple websites on a single IP in SBS, I believe contrary to most information you will find, you do not have to have ALL of the sites on the same port - in my testing it worked fine to leave the admin sites (WSS 2.0 admin, WSUS 2.0 admin, companyweb, etc.) on their assigned ports since each site only has to have a singular host header, port number or IP address, not necessarily all the same. Some sites, like the ones that only an admin is going to access, can remain identifible through a unique port number and do not have to be on port 80 or 443, as stated here:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true
And while you can thereotically, and to a certain extent literally, host multiple web sites with a single IP in IIS 6.0...possibly in Small Business Server 2003...the real showstopper in this scenario is ISA Server 2004. See this article for an explanation of configuring ISA Server 2004 to work with Windows Sharepoint Services 3.0 using SSL on a single IP with host-to-host headers:
http://technet.microsoft.com/en-us/library/cc713327.aspx
(I feel obliged to leave a trail of breadcrumbs should anyone else come down this path...)
Because the server components are somewhat glued together in SBS, limitations arise when configuring web listeners (my head still hurts from thinking about it). Because you have to maintain the Default Web Site in SBS 2003 for OWA, OMA and RWW, it becomes difficult if not impossible to complete this configuration. I do believe it would work on a stand-alone IIS 6.0 server however (which is what the article is written for).
The best solution here when trying to host WSS 3.0 on SBS 2003 with a proper domain name and internet facing application extension is...buy another NIC. :0) (I already have the additional static IPs.)
Also, in terms of hosting multiple websites on a single IP in SBS, I believe contrary to most information you will find, you do not have to have ALL of the sites on the same port - in my testing it worked fine to leave the admin sites (WSS 2.0 admin, WSUS 2.0 admin, companyweb, etc.) on their assigned ports since each site only has to have a singular host header, port number or IP address, not necessarily all the same. Some sites, like the ones that only an admin is going to access, can remain identifible through a unique port number and do not have to be on port 80 or 443, as stated here:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true
ASKER
Dov, thank you for your reply. I'm awarding this a grade of B because though the solution addresses the intial question posed, it doesn't address the wider scope of doing this on SBS. I also feel that I brought a fair amount of my own investigative skills to finding a solution as well that obviously does address the scope of the problem. It was a daunting question, btw, and your assistance is very much appreciated. S.O.
Try removing SSL for now, and see if that solves the issue.
Dov.