The World’s Leading Microsoft .NET Magazine
Sign-In | Register
   
 
timstall

Donate Today!

Search Box

 

Calendar

««Mar 2010»»
SMTWTFS
  12
3
456
7
8
9
10
111213
14151617181920
21222324252627
28293031

My RSS Feeds








Mailing List

Most Popular Tags

                                                           

More Visual Studio.Net IDE errors - Part III

« H E Tools :: email
posted Thursday, 4 August 2005
I had mentioned before that I was having problems directly running web applications, so I resorted to manually attaching to the process. This worked fine for server code, but it was insufficient to debug client JavaScript. So, I needed to buckle down and fix it.

I kept getting the error: "Error while trying to run project: Unable to start debugging on the web server. The COM+ registry database detected a system error". I wasn't finding a solution with the associated help file.

Finally I installed the .Net 1.1 Service Pack 1, and that fixed it.

I also heard that running %WINDOWS%\system32\secedit.exe would fix the registry problem, but I have not personally tried it.

links: digg this    technorati    


comments (5)


1. jtaranto left...
Thursday, 15 September 2005 12:37 pm

Is there a .NET 1.0 Service Pack 1?


2. Tim Stall left...
Wednesday, 21 September 2005 8:14 am

Hey JTaranto, You can search the MSDN website. Check this out: http://www.microsoft.com/d ownloads/details.aspx?familyid=6978D761-4A92-4106-A9BC-83E78D4ABC5B&display lang=en


3. Aimee left...
Wednesday, 11 January 2006 10:22 am

Thanks! This worked for solving my problem. I too was receiving the error: "Error while trying to run project: Unable to start debugging on the web server. The COM+ registry database detected a system error".


4. Sayan left...
Friday, 1 September 2006 4:09 am

I have .NET 1.1 sp1 installed but am still getting this problem while running a VS2003 project. I have installed SV2005 but 2003 was before prior to 2005. It used to work before.


5. Adrian Higginbotham left...
Monday, 20 November 2006 5:23 pm

I ran into this problem also. I had already installed .NET Framework 1.1, .NET 1.1 Framework Service Pack 1, and .NET Framework 2.0.

I finally had success by uninstalling all .NET Framework versions from "Add or Remove Programs" in the control panel, then installing 1.1, then the 1.1 service pack, and then finalling installing 2.0.

It took a bit of time, but it worked.