Unable to start debugging on the web server. The web server is not configured correctly.

CyclingFoodmanPA posted on Friday, March 23, 2007

Ok, I have been battling with this for a while. I was able to get everything to work on my home computer, came to work, did the same things, (per Rocky's instructions) and I am getting this error. It is bugging the he double toothpicks out of me! At home I have Visual Studio 2005 Professional and at work I have Visual Studio 2005 Standard (yea, I have better everything at home). Both machines are running Win XP w/SP2 and using a local data portal. Hey, I get that to work before I start messing with the complicated stuff. Now, if I go to IE and run http://localhost/PTWebvb, the app. runs and does fine. It is when I am in Visual Studio and press F5 in debug mode that it craps out. Now, the error message says "Click Help for more information." but guess what, no help button. Gotta love Microsoft. Anyway, the full message is as follows: "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." Well, the last part lied. Ran it outside of the debugger and all was ok. And yes, this is the VB version and I am getting ready to do the C Sharp example and let's see what happens there!

Thank you in advance for your assistance.

CyclingFoodmanPA replied on Friday, March 23, 2007

Ok, I got things to work with the C Sharp example. It was pretty easy based on Rocky's instructions as I know from getting things to work at home. So, it is not the Standard vs Professional version of Visual Studio 2005 that is the problem as I was able to get the CS sample to work here. Now, I notice on the vb example I see "Build Succeeded" on the bottom before I get the "Unable...." message so I know the build succeeded. So, any ideas on where to go from here. I am going back to check my IIS configuration between the 2 examples, but I am 99.9% sure I did things correctly.

Vertigo1 replied on Tuesday, June 19, 2007

I'm now getting this whilst trying to get the PTWeb app up and running on a new machine. Don't have the book to hand as it's at home.

Anyone find a solution?

dbsaxman replied on Monday, February 04, 2008

Just wanted to share a tip, FYI. My scenario was such that IIS was installed AFTER Visual Studio 2005. A colleague had seen a similar problem with VS 2003. We did two things to fix it, and now I am able to run the PTWeb app under VS 2005 / IIS 5.1:

1. We ran ASPNET_REGIIS.EXE (under the WINNT\Microsoft.NET\Framework\v2.0.50727 directory, with a "/i" parameter, at the command line).

2. We enabled Windows integrated security in IIS.

The "unable to debug" error went away and the PTWeb app now runs.

-Dave

ClaytonHoyt replied on Wednesday, April 30, 2008

Hi All

I am getting this same error but under slightly different circumstances. We are using client certificates accessed from a common access card. Because of this, we have to debug under SSL. I get this same error when using SSL but if I turn off the common access card requirements and SSL, I do not get any errors at all.

I have tried all the above on 2 different computers and nothing helps. Oddly, if I publish the site and turn on client certs with SSL, it works fine on the staging server.

Any thoughts?

Clay

probe replied on Wednesday, February 18, 2009

Had this "debugging" problem going from 3.6.0 to 3.6.1 in ptweb.

What is missing is the Everyone user on the PTWeb catalog in the 3.6.1 track. Just add that user under the security tab for the PTWeb catalog and anonymous access should be "enabled" for your website. To enable debugging check Integrated Windows Authentication in your IIS virtual root.

good luck.

JoeFallon1 replied on Friday, February 01, 2008

Try this:

In IE Trusted sites add localhost (without the http://)

Be sure to turn off Visual Studio and then re-start it after making this change.

Also, you can try to add 127.0.0.1 (the loopback address) as a trusted site.

Joe