Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 814717 - Last Review: December 3, 2007 - Revision: 4.5
BUG: "Unable to start debugging on the Web server" error message when you run an ASP.NET Web application
On This Page
SYMPTOMS
You create an ASP.NET Web application by using
localhost as the Web server, and you change the Web site setting in
Microsoft Internet Information Services (IIS) to use the specific
IP address for
Web Site Identification. Then, when you run
the application, you receive the following error message:
Error while trying to run project: Unable to start debugging on
the web server. Could not start ASP.NET or ATL Server
debugging.
Verify that ASP.NET or ATL Server is correctly installed on
the server.
CAUSE
This problem occurs because the debugger does not send the
debug action to IIS when you run the application. The debugger identifies your
computer as
localhost. However, in IIS, the
Web Site Identification of
the application is the IP address that you specified.
RESOLUTION
- In a text editor such as Notepad, open the
WebApplicationName.vbproj.webinfo file.
Note In a Visual C# .NET project, this is the WebApplicationName.csproj.webinfo file.
This file is located in
the application folder for the application project. - Locate the following line.
Visual Basic .NET <Web URLPath = "http://localhost/<WebApplicationName>/<WebApplicationName>.vbproj" />
Visual C# .NET <Web URLPath = "http://localhost/<WebApplicationName>/<WebApplicationName>.csproj" />
- Replace "localhost" with the IP Address of your computer as follows.
Visual Basic .NET <Web URLPath = "http://10.150.144.131/<WebApplicationName>/<WebApplicationName>.vbproj" />
Visual C# .NET <Web URLPath = "http://10.150.144.131/<WebApplicationName>/<WebApplicationName>.csproj" />
- Start Microsoft Internet Explorer. On the
Tools menu, click Internet
Options.
- In the Internet Options dialog box, click
the Security tab. Under Select a Web content zone to
specify its security settings, click Local Intranet,
and then click Sites.
- In the Local Intranet dialog box, click
Advanced.
- In the Add this Web Site to the zone box,
type the URL of your project, and then click Add.
- Close the application, and then open the application
again.
- On the Debug menu, click
Start.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft
products that are listed in the "Applies to"
section.
MORE INFORMATION
Steps to reproduce the problem
- In Microsoft Visual Studio .NET, create a new Web Application project or a new Web site project
by using Visual Basic .NET or Visual C# .NET. In the New
Project dialog box, type
http://localhost/testapp in the
location box.
- Click Start, click Run,
type inetmgr, and then click OK.
- In Internet Information Services (IIS) Manager, expand
(local computer), and then locate Default Web
Site.
- Right-click Default Web Site, and then
click Properties.
- In the Default Web Site Properties dialog
box, click the Web Site tab. In the IP
address list, click the IP address of your computer. Click
OK, and then close IIS Manager.
- On the Debug menu, click
Start.
REFERENCES
For more information, visit the following Microsoft
Developer Network (MSDN) Web site:
APPLIES TO
- Microsoft .NET Framework 2.0
- Microsoft .NET Framework 1.1
- Microsoft .NET Framework 1.0
- Microsoft Visual Basic .NET 2003 Standard Edition
- Microsoft Visual Basic .NET 2002 Standard Edition
- Microsoft Visual C# .NET 2003 Standard Edition
- Microsoft Visual C# .NET 2002 Standard Edition
| kbvs2005doesnotapply kbvs2005swept kbvs2002sp1sweep kbpending kberrmsg kbserial kbip kbwebserver kbwebforms kbwebbrowser kbbug KB814717 |
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
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please