Printable View
JiwaInventory is a COM dll.Code:JiwaInventory.clsInventory inventory = new JiwaInventory.clsInventoryClass();
the code generates the following error: "Retrieving the COM class factory for component with CLSID {7DCA24D5-2378-400F-875A-6B9DDF7610E2} failed due to the following error: 80040154."
can anyone tell me what the error means (or where i could find out)? i have no documentation for the COM object.
Not too sure about your specifics but I found some hits on msdn that may help -
http://search.microsoft.com/results....-US&q=80040154
thanks for the help, but couldn't find anything useful.
where would i find out what error 80040154 means?
According to a forum post from one of the results of Rob's search, that error code means "class not registered". I can't vouch for the verisimilitude of that information though.
(Always wanted to use that word. Any Star Trek: Voyager fans may recall Tuvok having used it once... or they may have a life.) :)
i tried running "regsvr32 Interop.JiwaInventory.dll", but it gave the error "Interop.JiwaInventory.dll was loaded, but the DllRegisterServer entry point was not found. This file cannot be registered."Quote:
Originally Posted by jmcilhinney
That is a .NET assembly. You don't register .NET assemblies. You need to register the COM library that that assembly is designed to allow you to INTEROPerate with.
i tried registering the COM library associated with the .NET assembly but i got the same error.
where can i find a list of all COM objects that have been registered with windows?
I have limited knowledge when it comes to COM. You now know what I (think I) know. I'll leave you at the mercy of others from here.
Usually you can find out what the variaous meanings of the error code is by searching MS like I did.
Here are 7 more hits at MS.
thanks for the help on this...
it seems like the error code means the class is not registered (as posted by jm), but when i register the class with regsvr32 the same error appears.
Yes, but I think John posted in #6 about this. Maybe he can elaborate?
problem solved!
i removed the reference to the interop dll and added a reference to the COM dll, so VS would create a new interop dll.
must have been a problem somewhere in the old interop dll.