.Net 3.5 sp1 unable to start debugging on web server

.net-3.5visual-studio-2008

When trying to debug my web application, I'm getting an "unable to start debugging on the web server" error then with html displayed right after in the same pop up. All the inline code in the html shows an exception e.g object reference not set, unhandeled exception was generate, etc.

I tried all the suggestions on google to no avail: Windows Authentication in IIS is on, aspnet_regiis -i gives me the "Failed to initialize properly 0xc0000005" error.

This problem only occurs under .Net 3.5 SP1, 3.5 works fine and I made sure it's SP1 by uninstalling and reinstalling it twice. And I also made sure nothing has changed except for the .Net SP1.

Running Win XP,
VS 2008, IIS on same box

Any help would be appreciated, thanks

Best Answer

Turns out it's a special case. Posting here just in case others have the same set-up. The problem is caused by Symantec Endpoint Protection MR5. Rolling back to MR4 did the trick. Additional info: http://www.symantec.com/connect/forums/aspnetwpexe-could-not-be-started-error-code-failure-c0000005-when-sep1105-installed

Thanks to all those that have replied.

Related Solutions

R – XmlSerializer changes in .NET 3.5 SP1

In SP1 does the foo.Bar property get properly deserialized?

In pre SP1 you wouldn't be able to deserialize the object because the set method of the Bar property is private so the XmlSerializer doesn't have a way to set that value. I'm not sure how SP1 is pulling it off.

You could try adding this to your web.config/app.config

<system.xml.serialization> 
  <xmlSerializer tempFilesLocation="c:\\foo"/> 
</system.xml.serialization>

That will put the class generated by the XmlSerializer into c:\foo so you can see what it is doing in SP1 vs RTM

Change .NET Framework version of application pool to 3.5

The 3.5 framework still runs on top of the 2.0 CLR so what you are seeing is correct.

Scott Hanselman has a nice blog post about the details of this:

The marketing term ".NET Framework 3.5" refers to a few things. First, LINQ, which is huge, and includes new language compilers for C# and VB. Second, the REST support added to Windows Communication Foundation, as well as, third, the fact that ASP.NET AJAX is included, rather than a separate download as it was before in ASP.NET 2.0. There's a few other things in .NET 3.5, like SP1 of .NET 2.0 to fix bugs, but one way to get an idea of what's been added in .NET 3.5 is to look in c:\windows\assembly.

Best Answer

Related Solutions

R – XmlSerializer changes in .NET 3.5 SP1

Change .NET Framework version of application pool to 3.5

Related Topic