Article ID: 327283 - Last Review: July 28, 2005 - Revision: 3.1 FIX: You cannot create Web projects on Windows Server 2003 in Visual Studio .NET 2002This article was previously published under Q327283 On This PageSYMPTOMSWhen you use Visual Studio .NET 2002 to create a new Web
project, and you connect to Microsoft Windows Server 2003 as the Web server, a
Web Access Failed dialog box appears and you receive the
following error message: The default Web access mode for
this project is set to file share, but the project folder at
'http://localhost/WebApplication1' cannot be opened with the path
'c:\inetpub\wwwroot\WebApplication1'. The error returned was: Unable to create web project 'WebApplication1'. The file path 'c:\inetpub\wwwroot\WebApplication1' does not correspond to the URL 'http://localhost/WebApplication1'. The two need to map to the same server location. HTTP Error 404: Not Found CAUSEThis problem occurs because Microsoft Internet Information
Services 6.0 (IIS) blocks all file name extensions that are not explicitly
mapped. By default, the .tmp file name extension is not mapped on IIS 6.0 for
security reasons. During the process of creating a Web project, Visual Studio .NET 2002 tests to confirm that the URL and the UNC path match. To do this, Visual Studio .NET writes a file that has the .tmp file name extension to the server, and then requests this file from the server through an http request. Because the .tmp file name extension is not mapped on IIS 6.0, IIS returns HTTP Error 404. This causes Visual Studio .NET to return the error message described in the "Symptoms" section. Note This problem does not occur when you use Visual Studio .NET 2003 because this version uses a file that has the .htm file name extension for this process. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft Visual Studio .NET 2002. For more information, click the following article number to view the article in the Microsoft Knowledge Base:837234
(http://support.microsoft.com/kb/837234/
)
List of bugs that are fixed in Visual Studio .NET 2002 Service Pack 1
WORKAROUNDThere are three workarounds for this problem:
STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
This problem was corrected in
Microsoft Visual Studio .NET 2002 Service Pack 1.
MORE INFORMATIONSteps to Reproduce the Behavior
REFERENCES For additional information, click the following article
number to view the article in the Microsoft Knowledge Base: 240225
(http://support.microsoft.com/kb/240225/EN-US/
)
Description of Adsutil and MetaEdit Utilities Used to Modify the Metabase
| Article Translations
|
Back to the top
