CODEWITHSUNDEEP
comcom-interop
Tija
Tija

Reputation: 1737

IClassFactory failed due to the following error: 800a0153

I'm trying to reference a com component and it is throwing the below error.

Creating an instance of the COM component with CLSID {xxx} from the IClassFactory failed due to the following error: 800a0153.

Specifically the error gets thrown when I try to instantiate an object. I checked that

  1. The project being built for x86 processors which it is
  2. The com object is registered using regsvr32, and is available in the registry.

I can also see the methods in the object browser, so I know .net is finding it.

Any ideas on what I'm missing?

Upvotes: 3

Views: 11827

Answers (3)

Chris Dickson
Chris Dickson

Reputation: 12135

As noted in my comment to Hans' answer, this error code is FACILITY_CONTROL, which is supposed to relate to OLE/ActiveX controls, and has an error code which lies in the standard range (i.e. for Microsoft use) defined in OleCtl.h, but is not documented in the Win32 header files so is probably internal to a Microsoft product such as Visual Basic.

Can you tell us anything else about the COM component you are trying to use?

If the COM component was written using Visual Basic, I think it's probable that what you are seeing is equivalent to the Runtime Error 339 which users of Visual Basic see if they try to reference an OCX control which has some of its dependencies missing. You might look at the dependencies of the COM server's DLL/EXE using Depends.exe and see whether you have them all present on your machine.

Upvotes: 1

Hans Passant
Hans Passant

Reputation: 942119

This is an error code that's specific to the component. If you don't have documentation that explains what the code might mean then you'll need support from the vendor.

Upvotes: 1

RQDQ
RQDQ

Reputation: 15579

Back when I had to do a lot of COM work, I used COM Explorer quite a bit from these guys:

http://download.cnet.com/COM-Explorer/3000-2206_4-10022464.html?tag=mncol;lst

I had to install it last year to debug a bizarre COM registration issue with Office plugins.

Also, I have no affiliation with these guys whatsoever (and it looks like the company might be toast anyway).

Upvotes: 0

Related Questions