Funny ASP.NET Error - Could not start ASP.NET or ATL Server Debugging

by Erik Lane 3. September 2006 01:35

AAACK!!

I have an old application that I moved to a new folder to make some changes and test them out.  After moving the project files I update the webinfo file, create the app in IIS, etc.. to the get the web project to load.  I go ahead and make some changes and not I'm ready to debug.  All of the sudden I get hit with this message:  "Error while trying to run project: Unable to start debugging on the web server. Could not start ASP.NET or ATL Server Debugging. Verify that the ASP.NET or ATL server is currently installed on the server."

I try browsing the site directly in the browser and get a 404 error.  Hrm...something is up.

Tracking down things like this is really a resource hog.  I'm trying to get some coding done and I spend way too much time just trying debug my app.  Googling lead me down some narrow paths that were all the same...make sure, in IIS, the directory is an application, etc..  Someone has had this problem before, I know it.  The development world is too large for me to be the only one dealing with this.  If anyone has they've not blogged it/written about it...or I'm not as good at Googling as I thought I was.

Anywho, I eventually dig through support.microsoft.com and track down this KB article about Microsoft Security Bulletin MS05-004: ASP.NET path validation vulnerability.  Reading through the article you will see a section concerning ASP.NET performance impact after you install the security update.  In this section it references KB Article 894670 and this is the needle in the proverbial haystack.

Apparently it all comes down to a trailing backslash!  Holy Cow Batman!  This is on my local XP machine so this is screenie of the properties for my default site.  Remove that little backslash and all is good.

Hopefully this will help someone else down the road.

Giddy Up!

Tags:
Categories: Development & Geek Stuff
E-mail | Kick it! | DZone it! | del.icio.us
Permalink | Comments (3) | Post RSSRSS comment feed

Comments

Khalid
Khalid on 12/1/2007 4:00:00 PM

Maaaaaaaaaannnnn , thx very much you cant imagin how much you save time for me

Ben
Ben on 3/24/2009 5:33:10 PM

That was it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Thank-you, thank-you, thank-you, thank-you, thank-you, thank-you, thank-you, thank-you, thank-you, thank-you, thank-you.

Sean
Sean United States on 6/23/2009 8:23:45 PM

That was DEFINITELY it.  Thanks so much for this article!  You wouldn't believe all the harebrained solutions I found before coming across this one, and yet it was this simple little thing that did the trick!

Leave it to Microsoft for making the easiest, possibly most common solution the most difficult to find...

Comments are closed