Several Phenomena and solutions that ASP. NET cannot be debugged

Symptom 1: Debugging cannot be started on the Web server. An authentication error occurs when you communicate with the Web server.
Or you cannot start debugging on the Web server. Debugging failed because integrated Windows authentication is not enabled.

The reason may be: failed authentication or insufficient permissions.

Solution: select the specified application on the default IIS website.Program, Click "properties"> "Directory Security"> "edit" for identity authentication and access control, and "Integrated Windows Authentication" is checked.

Bytes ---------------------------------------------------------------------------------------------------------------
Symptom 2: Debugging cannot be started on the Web server. The Web server is incorrectly configured. See Help for common configuration errors. Running a webpage outside the debugger may provide further information.

The reason may be that debugging is not enabled for the application on the Web server.

Solution: select the specified application on the default IIS website, and click "enable debugging" in "properties"> "ASP. NET"> "Edit configuration"> "application.

Bytes ---------------------------------------------------------------------------------------------------------------
Symptom 3: open an apsx instance in the development environment and prompt it in the error list,
Error 1 E: \ XXXXX \ yyyyy. ascx: ASP. NET runtime error: "/lm/w3svc/225492951/root/XXXXX" is not a valid IIS application.

The reason may be: failed authentication or insufficient permissions.

Solution: Follow the solution of symptom 1. If not, insert the Visual Studio disc, run the installer, and select "repair/reinstall ".

Related links:
Error: unable to start debugging on the Web Server
Http://msdn2.microsoft.com/zh-cn/library/dwesw3ee (vs.80). aspx

Error: Debugging failed because integrated Windows authentication is not enabled
Http://msdn2.microsoft.com/zh-cn/library/x8a5axew (vs.80). aspx