Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 306172 - Last Review: January 19, 2004 - Revision: 3.3
INFO: Common Errors When You Debug ASP.NET Applications in Visual Studio .NET
This article was previously published under Q306172
SUMMARY
This article provides a list of articles that describe some
of the most common problems you encounter when you debug ASP.NET applications
in Visual Studio .NET.
MORE INFORMATION
- When you debug an ASP.NET application in Visual Studio
.NET, you may receive the following error message:
Error
while trying to run project: Unable to start debugging on the web server. The
project is not configured to be debugged.
For ASP.NET projects,
verify that you have a valid project file called 'Web.config' for the URL
specified and 'debug' is set to 'true' in that file.
For ATL Server
projects, verify that the 'DEBUG' verb is associated with your ISAPI
extension.
Would you like to disable future attempts to debug ASP.NET
pages for this project?
For additional information about how to resolve this
error message, click the article number below to view the article in the
Microsoft Knowledge Base: 306156Â
(http://kbalertz.com/Feedback.aspx?kbNumber=306156/EN-US/
)
PRB: Error "The Project Is Not Configured to Be Debugged" When You Debug ASP.NET Applications
- When you debug an ASP.NET application in Visual Studio
.NET, you may receive the following error message:
Error
while trying to run project: Unable to start debugging on the web server.
Server side-error occurred on sending debug HTTP request.
Make sure
the server is operating correctly. Verify there are no syntax errors in
web.config by doing a Debug.Start Without Debugging. You may also want to refer
to the ASP.NET and ATL Server debugging topic in the online documentation.
Would you like to disable future attempts to debug ASP.NET pages for this
project?
For additional information about how to resolve this error
message, click the article number below to view the article in the Microsoft
Knowledge Base: 306163Â
(http://kbalertz.com/Feedback.aspx?kbNumber=306163/EN-US/
)
PRB: Error "Unable to Start Debugging" When You Send Debug HTTP Request
- When you remotely debug an ASP.NET application in Visual
Studio .NET, you may receive the following error message:
Error while trying to run project: Unable to start debugging on
the web server. Access is denied. Check the DCOM configuration settings for the
machine debug manager. Would you like to disable future attempts to debug
ASP.NET pages for this project?
For additional information about how to resolve this error
message, click the article number below to view the article in the Microsoft
Knowledge Base: 306164Â
(http://kbalertz.com/Feedback.aspx?kbNumber=306164/EN-US/
)
PRB: 'Access Is Denied' Err Msg When You Debug ASP.NET Page
- When you debug an ASP.NET application in Visual Studio
.NET, you may receive the following error message:
Error
while trying to run project: Unable to start debugging on the web server. Would
you like to disable future attempts to debug ASP.NET pages for this project?
For
additional information about how to resolve this error message, click the
article number below to view the article in the Microsoft Knowledge Base: 306165Â
(http://kbalertz.com/Feedback.aspx?kbNumber=306165/EN-US/
)
PRB: Error "Unable to Start Debugging on the Web Server" When You Debug ASP.NET Applications
- When you debug ASP.NET pages, the Visual Studio .NET
Debugger may not stop on breakpoints.
For
additional information about how to resolve this problem, click the article
number below to view the article in the Microsoft Knowledge Base:
306169Â
(http://kbalertz.com/Feedback.aspx?kbNumber=306169/EN-US/
)
PRB: Visual Studio .NET Debugger Does Not Stop on Breakpoints When You Debug ASP.NET Pages
- When you debug an ASP.NET application in Visual Studio
.NET, you may receive the following error message:
Error
while trying to run project: Unable to start debugging on the web server.
Access is denied. Would you like to disable future attempts to debug ASP.NET
pages for this project?
Verify that you are a member of the
Administrators group and the Debugger Users group on the computer.
A non-administrator does not have the correct permissions to debug the default
ASP.NET worker process (Aspnet_wp.exe
on Microsoft Windows 2000 and Microsoft Windows XP, and W3wp.exe on Microsoft Windows Server 2003). - When you debug an ASP.NET application in Microsoft Visual
Studio .NET, you may receive the following Microsoft Development Environment
error message:
Error while trying to run project: Unable
to start debugging on the web server. The server does not support debugging of
ASP.NET or ATL Server applications. Run setup to install the Visual Studio .NET
server components. If setup has been run, verify that a valid URL has been
specified.
You may also want to refer to the ASP.NET and ATL Server
debugging topic in the online documentation. Would you like to disable future
attempts to debug ASP.NET pages for this project?
For additional
information about how to resolve this error message, click the article number
below to view the article in the Microsoft Knowledge Base: 318465Â
(http://kbalertz.com/Feedback.aspx?kbNumber=318465/EN-US/
)
PRB: Cannot Debug ASP.NET Web Application
REFERENCES
For more general information about ASP.NET, refer to the
following MSDN newsgroup:
APPLIES TO
- Microsoft ASP.NET 1.1
- Microsoft ASP.NET 1.0
- Microsoft Visual Studio .NET 2003 Professional Edition
- Microsoft Visual Studio .NET 2002 Professional Edition
- Microsoft Visual Studio .NET 2003 Enterprise Architect
- Microsoft Visual Studio .NET 2002 Enterprise Architect
- Microsoft Visual Studio .NET 2003 Enterprise Developer
- Microsoft Visual Studio .NET 2002 Enterprise Developer
- Microsoft Visual Studio .NET 2003 Academic Edition
- Microsoft Visual Studio .NET 2002 Academic Edition
| kbpubtypekc _ik kbdebug kberrmsg kbgrpdsasp kbinfo KB306172 |
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
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please