Server Error in '/' Application.

[Guest]

My colleague and I are trying to setup a working project on our machines. The
environment is as follows
Windows XP Pro
..NET framework 2.0

I get this exccption

Server Error in '/' Application.
Retrieving the COM class factory for component with CLSID
{CFCCCF6B-F9C9-4B7E-80F9-8550EBFF2837} failed due to the following error:
80070005.

when running the .net application but no problem when running the classic
asp application off the same physical and virtual folder. My colleague has
no problem launching either of them, even though he has certain problem
getting some web services to work with his application. Any help or comments
will be much appreciated.

 

[Cowboy \(Gregory A. Beamer\)]

Office application, or uses some Office bits?
http://blog.crowe.co.nz/archive/2006/03/02/589.aspx

 

[Guest]

Thanks for the reply. But it still won't work after I followed your steps.

 

[Juan T. Llibre]

Try searchng the Windows registry for :
{CFCCCF6B-F9C9-4B7E-80F9-8550EBFF2837}

That way, you'll identify the component that's failing.

 

[Cowboy \(Gregory A. Beamer\)]

To hit on what Juan has stated:

1. Windows key + R or Start >> Run
2. Regedit then Enter
3. F3 - or View >> Find
4. CFCCCF6B-F9C9-4B7E-80F9-8550EBFF2837

Should be under the classes root, if I remember correctly. There is another
way, as well ... the OLE Viewer, but I think that only ships with older
versions of Visual Studio (pre .NET). It is faster, but only good if the
component in question is registered. But, the same is true of the registry.

 

[Guest]

I followed you two's suggestion and found the violating key in the registry.
I thought that since I have the dll on my machine for me to register, It
would be OK for me to delete that entry in the registry and try to register
it again, little did I know that I'd be stuck with the same error and with
the same error and the same exact id. Is there a way to retrieve the key
that I just deleted? What would be my options even if I can still retrieve
that register key? Thanks.

 

[Juan T. Llibre]

If you know which dll was referenced :

drive:\windows\system32\regsvr32 drive:\directorypath\the.dll

should re-register it.

 

[Guest]

Juan,

I did but the one in registery before is located in a different path, and I
don't know if it makes difference.