Sometimes I love it when products tell you to do something that you can't. My most recent was this message from Visual Studio 2005 (the real deal, no beta here).
Unable to start debugging on the web server. Unable to connect to the web server. Verify that the web server is running and that incoming HTTP requests are not blocked by a firewall.
Click Help for more information.
<ok button>
The part you can't do? Click Help. There is no Help to click.
If you happen to run into this gem, the problem was security based (turned anonymous authentication off and the worker process for asp.net didn't have access rights).
3 comments:
I have the same problem but can not figure out how to set anonymous authentication on to solve it as you did. Could you email me at
lvargas at indra.com
Unfortunately, I seem to have the same problem without it being the permissions — I've just added ASPNET and Debugger Users to the folders and it just doesn't wanna play ball.
I bloody hate integrating IIS into Visual Studio debugging; it so rarely works perfectly.
Ach well, thanks for being one of the two links on Google :o)
There are a few other things you can check on. If you have a few minutes, let me know what security settings you have on the folder containing the code. Also, you may want to try and re-register ASP with IIS (something like regiis -i, but read up on it first). Also, are you able to browse page without debugging?
Post a Comment