Advertisement
- Home
- Software
- Server Software
- Web Servers
- Microsoft IIS
- Troubleshooting "Cannot create a file when that file already exists...
Advertisement
- 1. meverest 481,381
- 2. tedbilly 307,988
- 3. Dave_Dietz 174,244
- 4. RubalJ 125,188
- 5. TechSoEasy 97,050
- 6. pcsmitpra 64,965
- 7. Abs_jaipur 62,223
- 8. tigermatt 60,375
- 9. cj_1969 59,832
- 10. Chris-Dent 54,465
- 11. hielo 52,885
- 12. Robbie_L... 52,574
- 13. Sembee 49,488
- 14. LeeDerby... 48,778
- 15. harperse 40,815
- 16. zephyr_hex 40,555
- 17. RobWill 38,547
- 18. brwwiggins 35,500
- 19. Paranorm... 32,975
- 20. kieran_b 29,759
- 21. b0lsc0tt 28,550
- 22. pcfreaker 28,280
- 23. servoadmin 27,340
- 24. Redwulf... 26,850
- 25. LegendZM 26,575
- 1. meverest 1,596,073
- 2. Dave_Dietz 1,575,622
- 3. tedbilly 396,556
- 4. humeniuk 244,493
- 5. Sembee 222,808
- 6. Chris-Dent 186,082
- 7. TechSoEasy 181,644
- 8. dnojcd 167,736
- 9. DireOrbAnt 155,014
- 10. harperse 150,983
- 11. alimu 147,067
- 12. AndresM 142,147
- 13. cj_1969 128,771
- 14. RubalJ 125,688
- 15. Silvers5 118,933
- 16. Wadski 102,970
- 17. fz2hqs 98,692
- 18. pcsmitpra 92,833
- 19. amit_g 86,791
- 20. Robbie_L... 81,824
- 21. Abs_jaipur 80,848
- 22. LeeDerby... 77,453
- 23. shambhus... 73,800
- 24. bigbillydot... 73,647
- 25. tigermatt 73,176
| 06.07.2008 at 01:09PM PDT, ID: 23466457 |
|
[x]
Attachment Details
|
||
|
[x]
The Solution Rating System
|
||
With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.
Your Input Matters If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
||
9.0
Troubleshooting "Cannot create a file when that file already exists" errors in IIS when using host headers
Asked by soneil66 in Microsoft IIS Web Server, MOSS-Sharepoint, SBS Small Business Server
Tags: Microsoft, SBS 2003, R2, SBS SP1, 2003 SP2, Exchange 2003 SP2, ISA 2004 SP3, IIS 6.0 hosting multiple websites, IIS 6.0
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.
Start Free Trial
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.
Start Free Trial
Attachments:
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628
