Dear all,
Anyone got the following error when instantiating an OLE DLL. The error is Automation Server can't create object.
Printable View
Dear all,
Anyone got the following error when instantiating an OLE DLL. The error is Automation Server can't create object.
The object hasn't been registered. Use regsvr32 and register it manually.
No Bill the component has been registered correctly and is present in the registry
Either it's not a valid COM object (and can't be instantiated)
OR the registered version is incompatable with the one you're trying to use.
msdnexpert ;-)
Give us the context in which you are trying to create the object.
td.
The object is being created through an ASP page.
I agree with Simon.. If your problem is occurring when you are trying to instantiate, then it sounds like a version capability problem. Check your compatibility setting under Project Properties.
Another option is to use late binding for your DLL & force your program to grab the latest version from the registry at run-time. Although late binding can sacrifice performance. Hope this helps..
On a similar note.. I get the "ActiveX cannot create object" error AFTER my object is instantiated (using late binding). The puzzling part is (1) I have confirmed the object has been created (2) this error only appears when I try to use the DLL's methods (3) it only seems to occur on Win95 machines.
Ideas anyone?
May I join and ask a question of my own?
<Rebart>
How do you do late binding? What I do is everytime I make changes to my COM component, I have to recompile the EXE as well for it to associate itself with the new COM. Thanks