Another Microsoft headscratcher solved, thanks to another blog. But I only got past my sticking point with the help of a comment about halfway down a slew of comments on the post. So hopefully highlighting that helps someone else. Or if you’re still stuck, pour over the rest of the comments. Problems like these rarely have one neat solution for everybody. Here’s the text of the post reproduced:

Ever seen this error when debugging a web app in the VS.NET IDE:

Error while trying to run project: Unable to start debugging on the web server. You do not have permissions to debug. Verify that you are a member of the ‘Debugger Users’ group on the sever.

Well, search the net and you’ll get 100s of hits talking about .NET debugging options, IIS configurations, permissions, admin access, etc…. In my case everything checked out and still no luck. Well here’s another cause of this error: adding http://localhost to your Trusted Sites list…. Yup that’s right. Sounds simple, but that’s what did it in my case….

And the comment which got me debugging again:

Just wanted to share an additional tidbit. After trying everything listed here without success, I tried moving localhost from the IE “trusted sites” zone to the “local intranet” zone – and voila! Not sure what the difference is, but it worked.

Note the remarkable similarity, yet frustratingly subtle difference between the solution to this problem, and the one I posted about here.

Comments(0) - Join the Conversation

Andrew Crowe Categories: Technology