This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 42%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHS%3C/text%3E%3C/svg%3E)
Hi,
I have changed an interface in the existing legacy VB 6.0 ActiveX DLL, but after the change unable to create the object from another server (DCOM). Below are the steps followed to deploy the component
1. After the change, rebuilt the VB 6.0 DLL with version compatibility option set as "No Compatibility"
2. Then registered the newly generated TLB (also replaced the physical file from where the other components are importing the TLB file)
3. Compiled all the dependent components (services built on VC++)
4. Deployed the new DLL in the server and register it (using regsvr32 command).
5. Registered the components again using component service tool
6. Replaced the service (.EXE) in the other server machine
When I launch the application , CoCreateInstanceEx which is trying to create the interface from another server is getting failed with return value 0x80040155.
Please help me out the to resolve the issue .
I have changed an interface in the existing legacy VB 6.0 ActiveX DLL
This is a violation of one of the basic COM rules. Once an interface is published it is immutable and cannot be changed. Refer to Interface Design Rules.
If you have only deployed your changes to one server then every other machine that attempts to instantiate the COM object is using obsolete information.
Did you change the IID of the interface?
since interface has been changed VB 6.0 IDE will generate new IID, it won't allow to use the same IID. I have compiled the dependent client application using the newly generate TLB.
Is there any thing to done on client side.
At a minimum you need to deploy the new dll to every client and register it and the related type library. Client applications need to be rebuilt to reference the new interface. It's as if you were completely deploying a brand new application.
By the way, please use Comments instead of Answers for discussion and follow-ups. You can convert your your posted answer to a comment. Answers are intended to be used for posts that provide solutions.