Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 920719 - Last Review: February 21, 2009 - Revision: 3.1
Error message after you click "ASP.NET Configuration" in Visual Web Developer 2005 on a computer that is running a 64-bit version of Windows Server 2003 or a 64-bit version of Windows XP: "Unable to connect to Visual Studio's Localhost Web Server"
Consider the following scenario:
- In Microsoft Visual Web Developer 2005, you create a new Web site project. In the New Web Site dialog box, you click File System in the Location box.
- You try to start the Microsoft ASP.NET Web Site Administration Tool for the Web site project.
- You do this on a computer that is running a 64-bit version of Microsoft Windows Server 2003 or a 64-bit version of Microsoft Windows XP.
In this scenario, you may receive the following error message immediately after you click
ASP.NET Configuration:
Unable to connect to Visual Studio's Localhost Web Server
This problem occurs because the ASP.NET registry keys are missing. The ASP.NET registry keys are missing when you install ASP.NET after the Enable32bitAppOnWin64 Microsoft Internet Information Services (IIS) metabase setting is set to a value of 1. Because IIS is configured to run in the 32-bit mode, the ASP.NET installation does not create the ASP.NET registry keys in the 64-bit registry. The ASP.NET installation creates the ASP.NET registry keys only in the 32-bit registry.
To resolve this problem, follow these steps.
Important This article does not apply to Windows Server 2008. Do not run these steps on a Windows Server 2008-based computer.
64-bit mode
- Click Start, click Run, type cmd, and then click OK.
- To enable the 64-bit mode, type the following command, and then press ENTER:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
- Type the following command, and then press ENTER:
cd C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727
- To install the 64-bit version of ASP.NET, type the following command, and then press ENTER:
aspnet_regiis –i
- Type the following command, and then press ENTER:
iisreset
32-bit mode
- Click Start, click Run, type cmd, and then click OK.
- To enable the 32-bit mode, type the following command, and then press ENTER:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
- Type the following command, and then press ENTER:
cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
- To install the 32-bit version of ASP.NET, type the following command, and then press ENTER:
aspnet_regiis –i
- Type the following command, and then press ENTER:
iisreset
After you follow these steps, Visual Web Developer 2005 can correctly locate the path of the WebDev.WebServer.exe file. Therefore, the Visual Web Developer 2005 test Web server can be turned on.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Steps to reproduce the problem
- Click Start, click Programs, and then click Microsoft Visual Web Developer 2005 Express Edition.
- Click File, and then click New Web Site.
- Click ASP.NET Web Site, and then click OK.
- In Solution Explorer, click ASP.NET Configuration.
You receive the error message that is mentioned in the "Symptoms" section.
Note This problem occurs when you configure IIS to run in the 32-bit mode before you install ASP.NET.
APPLIES TO
- Microsoft .NET Framework 2.0
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, 64-Bit Datacenter Edition
- Microsoft Windows XP Professional x64 Edition
| kbtshoot kbbug kbprb KB920719 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate