tags:

views:

3863

answers:

4

Today, everytime I try to open any .Net application I get:

CLR error: 80004005
The program will now terminate.

Any suggestions?!

+5  A: 

I'd start with downloading and re-installing the .NET framework.

Jeff Donnici
I ran the installer in "repair" mode, and it seemed to resolve the issue. Thanks! Unfortunately, I am still confused to how the FX was corrupted... oh well.
Nescio
Other responses mention permissions issues, so maybe the "repair" mode simply re-set the necessary file/OS permissions for you. In any case, I'm glad it worked.
Jeff Donnici
+1  A: 

A quick search suggests this:

"If you get a Run-time error 80131522 "No Server registered or could not load class for CLSID ...", it is because you are trying to run the VB executable from a directory other than where the .NET assembly is located. This also happens if you try to run the vb code in interactive mode. This can be solved by installing the .NET assembly into the global application cache"

(http://bytes.com/forum/thread353655.html)

In an ASP.NET context, it appears this is related to file permissions:

The error code for the failure is 80004005. This error can be caused when the worker process account has insufficient rights to read the .NET Framework files. Please ensure

(http://weblogs.asp.net/jambrose/archive/2004/09/01/224226.aspx)

amdfan
A: 

I believe 0x80004005 is (usually) an ACCESS DENIED error - so start with that in mind. If you're on Vista+, try running it as admin. Otherwise, Process Monitor should help you track it down.

Mark Brackett
A: 

I'm experiencing something similiar on a client machine. a WinForm application in .Net 2.0. The server has .NET Framework 2.0 w/ SP1 and WSE 2.0 installed. It's running Windows Server 2000 and has 2GB of RAM dedicated to it.

I've read about reinstalling the .Net Framework, which I really don't want to tell my client to do. Other than that, I've read about compatibility....

Any suggest?

SaguiItay