Monday, January 19, 2009

Unable to Start Debugging on the Web Server

Unable to Start Debugging on the Web Server

I hate that, and it seems that every time I (or a co-worker) gets the error “Unable to Start Debugging on the Web Server” on a machine when attempting to debug an ASP.NET project, I have to scramble to remember what to look at. Here's a few things that has worked for me to get things working so you can debug your ASP.NET project when/if you ever get this error:

  • Make sure that IIS is configured to use Integrated Windows Authentication. Look for the checkbox on the Authentication Method dialog launched from the Directory Security tab of the site properties.
  • Make sure that HTTP Keep Alives are enabled. You'll find that checkbox on the Web Site tab of the properties dialog, in the connections section.
  • This one is strange, but it seemed to do the trick for many out there, add http://localhost to the trusted sites in Internet Explorer. To tell the truth, this seems to be a fix for the symtoms, not actually fixing the problem itself, but if it works it works. BTW, you'll have to uncheck the “Require server verification (https:) for all sites in this zone“ checkbox to add it as a trusted site.

Good luck.

(For main source of the above article Click Here)


The following error may occur when trying to run/debug an ASP.NET 2.0 web app, when the web server is not configured properly:

"Unable to start debugging on the web server. The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the debugger may provide further information."

This is usually caused because of one or both of the following problems:

  1. The directory the web app resides in has not been registered as a web application.
  2. The correct ASP.NET version has not been set for the web app (note that this cannot be set until 1. has been sorted out).

To fix problem 1:

  1. Open the IIS admin app.
  2. Right click on your app's directory (/virtual dir) and select Properties.
  3. On the Directory tab, under Application Settings, next to Application Name there will be a 'Create' button - click it. Once the dir has been registered as a web app then this button will say 'Remove'.
  4. Click Apply (or OK).

To fix problem 2:

  1. Open the IIS admin app.
  2. Right click on your app's directory (/virtual dir) and select Properties.
  3. Select the ASP.NET tab.
  4. Select the correct ASP.NET version. Note that this field is disabled if the dir has not been set as an application (see above).
  5. Click Apply (or OK).

(For main source of the above article Click Here)


No comments:

Popular Posts