Edit

Debugging Web Applications: Errors and Troubleshooting

  • Article

You may encounter the following errors when attempting to debug Web applications.

Site Uses IP Address

This error occurs when the debugger tries to auto-attach to a Web application that is using an IP address. This issue occurs if you change Web site identification to use specific IP address in IIS.

For more information, see Error: Site Uses IP Address

A Security Check Failed Because the IIS Admin Service Did Not Respond

This error occurs when the IIS Admin Service doesn't respond. This result usually indicates that there's a problem with the IIS installation. First, verify that the service is running using the Services tool from Administrative Tools.

For more information, see Error: A Security Check Failed Because the IIS Admin Service Did Not Respond.

ASP.NET Not Installed

This error occurs when ASP.NET isn't installed correctly on the computer that you are trying to debug. This result might mean that ASP.NET was never installed or that ASP.NET was installed first and IIS was installed later.

For more information, see Error: ASP.NET Not Installed.

Debugging Failed Because Integrated Windows Authentication Is Not Enabled

Authentication of the user who requested debugging was prevented by an authentication error. This error can occur when you try to step into a Web application or an XML Web service. One cause of this error is that integrated Windows authentication isn't enabled. To enable it, follow the steps in "To enable integrated Windows authentication."

For more information, see Error: Debugging Failed Because Integrated Windows Authentication Is Not Enabled.

The Web Server Has Been Locked Down and Is Blocking the DEBUG Verb

Stepping into a Web application or XML Web service failed because the IIS lockdown tool has been run and URLScan has been installed and activated. This condition blocks IIS from receiving the DEBUG verb.

For more information, see Error: The Web Server Has Been Locked Down and Is Blocking the DEBUG Verb.

Timeout While Debugging Web Services

When you are stepping into an XML Web service from calling code, the call may sometimes time out, with the result being that you cannot continue debugging.

For more information, see Error: Timeout While Debugging Web Services.

Unable to Start Debugging on the Web Server

When you try to debug an ASP.NET application running on a Web server, you may get this error message: Unable to start debugging on the Web server.

For more information, see Error: Unable to Start Debugging on the Web Server.

The Web Server Could Not Find the Requested Resource

Due to security considerations, IIS has returned a generic error.

For more information, see Error: The Web Server Could Not Find the Requested Resource.

The Web Server Is Not Configured Correctly

An IIS configuration issue may result in this error.

For more information, see Error: The web server isn't configured correctly.

See also