Error creating instance of COM class

Question

0.00/5 (No votes)

See more:

I'm trying to connect to a COM dll on a remote server.

My code is as follows:

Type type = Type.GetTypeFromProgID("ourType.ourClass", "ourServer", true);
Object instance = Activator.CreateInstance(type);

GetType works perfectly but CreateInstance falls over with the following error:

Retrieving the COM class factory for remote component with CLSID {ourCLSID} from machine ourServer failed due to the following error: 80040154.

I'm fairly confident that the object on the remote server is registered correctly.

From what I've found so far, the error code can often indicate problems with 64-bit programs trying to talk to 32-bit objects and the suggested remedy is usually to rebuild the calling application for x86. I've tried that (and even tried targeting .NET 2.0 for good measure) and I still get the 80040154 error.

Has anyone run into this before?

Posted 6-Mar-15 0:06am

PeejayAdams

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CHill60 · Answer 1 · 2015-03-06T00:43:00

Things to try ...

1. Download the Sysinternals[^] tools (esp. ProcMon and ProcExp) - you can find out if there is another DLL that the problem one needs that isn't registered properly (it's always been this issue when I've come across similar problems)

2. Try re-registering the DLL - remember this needs to be registered on the PC not the remote server and if it is 32-bit needs to be registered with the version of regsvr32.exe that is in %windir%\SysWOW63 not the one in %windir%\System32

3. If neither of those work then use the ProcMon and other sysinternals tools to gain further insight into what is happening - see the link for details of how they work. I really do recommend them.