Interface not registered (0x80040155) on return from COM call

▲
2
▼

I'm making a synchronous cross-process COM call that executes successfully, but when I check the HRESULT returned it's the aforementioned 0x80040155, or "Interface not Registered" and the out parameter doesn't contain any data.

Is there a way to re-register COM executibles? I'm not even sure that this would fix it, so is there an alternative way to fix this?

This problem appears to be localized to a particular system, as it works successfully on other systems.

c++
com
asked on Stack Overflow Nov 23, 2010 by dlanod

2 Answers

▲
1
▼

Most COM executables can be registered by running COMserver.exe /regserver

answered on Stack Overflow Nov 23, 2010 by Motti
▲
0
▼

After registering the COM executables, I still received the same Interface not Registered error.

I was able to get rid of the exception by repairing Visual Studio. You can do by clicking Repair in the setup wizard, or in Visual Studio 2017, open the Visual Studio Installer then click Additional Choices -> Repair.

answered on Stack Overflow Aug 2, 2017 by Kyle Williamson • edited Aug 2, 2017 by Kyle Williamson

User contributions licensed under CC BY-SA 3.0