07 August 2008
"The Project Is Not Configured to Be Debugged" error message pops while debugging
The core reason for this error is due to the permissions in the application. In a rare circumstance, if the web.config file is not there, then this error message would occur. Even after ensuring that the web.config file is present, if this message occurs, try to check the permissions in IIS.
The following steps would help solve the problem:-
- Go to IIS, open the properties for this project.
- In the properties page, choose the Directory tab.
- Choose "Scrits Only" option in the Execute permissions box.
- Apply change and retry debugging.
» "Unable to Start Debugging" error when executing .NET application
Similar articles
» "Unable to Start Debugging" error when executing .NET application
"Unable to Start Debugging" error when executing .NET application
A common error which is encountered while running an ASP.NET application is "Unable to Start Debugging". The complete error would look like :-
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?
Though it would look complex on the first look, the resolution for this problem is simple. The probem would be with the Web.Config file whose xml would not be well formed.
Check if all the opening and closing tags in the XML is apt. Also check for the upper case and lower case of the xml contents.