VS.Net 2005 unable to start debugging
I’ve started on a web project for a client using VS.Net 2005 and the .Net 2.0 framework. This is the first project that I am undertaking in this framework and I am catching a few little teething issues as I go. Some of them are obvious and some not so obvious.
The most un-obvious one that i have come accross so far was related to being able to debug the project. I am set up working on my laptop which has both VS.Net 2003 and VS.Net 2005 installed. I’d had the “unable to start debugging on the webserver” errors before in VS.Net 2003 and am fairly comfortable with what has to be done to correct the issue. When I received that error this evening with VS.Net 2005 I followed the same path to try resolving it.
No good. Doesn’t work.
After chasing links in circles through the online help I found a link to this knowledge base article that gives instructions on editing the permissions on the metabase. Thankfully for my particular problem it was easy. At the top of the article it says:
Note If you are using ASP.Net 2.0 and you have to grant metabase permissions to a Windows user account, run the ASP.NET IIS Registration Tool command with the -ga option instead of using the tool that is shown here.
A quick check in “Local Users and Groups” on my laptop showed that the windows user account that ASP.NET runs under is ASPNET.
I ran
aspnet_regiis -ga ASPNET
and was back in business. Debugging is now working, pitty that my code is not - but that is another tale altogether.
Dylan Said,
March 22, 2006 @ 8:07 am
I recently installed vb.net 2005 express edition on my home box to get a bit of a feel about it, and I had a similar error when trying to run a project.
While I can’t remember the exact wording, the error was that it failed to start the debugger. The problem? (after much googling) My terminal services service was not running - I must have disabled it in a frenzy of game-performance-related disablement of system function. (or better security, perhaps?)
Anyway, after restarting the service everything worked fine, but it took a bit of googling to find the issue and from memory the 2003 install worked fine without it.
So it’s entirely possible to be working away with 2003 and upgrade to 2005 only to have it fail to work without explaination….. awesome!!
Me. Said,
March 22, 2006 @ 8:23 am
Yeah I found the fact that 2003 install works fine (in the correct sequence of course) and the 2005 doesn’t most annoying. I would have assumed that the 2003 install had issues and they could have rectified them in 2005. Oh well… Live and learn.
I wasn’t aware that I was running the Terminal Services service, but a quick check shows that it is
I find it interesting that VS2005 requires terminal services… but it works now, and that is the main thing.