Home/ Questions/Q 6106179
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T14:03:07+00:00

I have a messy situation wrapping a couple of 3rd party COM components. Actually

  • 0

I have a messy situation wrapping a couple of 3rd party COM components. Actually it’s one COM component and several .NET assemblies. The .NET assemblies in turn depend on the same 3rd party’s internal COM component. When I have the COM DLLs registered, my code works fine (right now I’m testing from C#). When I don’t, it fails. What’s the best way to debug that?

I generated the SxS manifest by adding a reference to the COM components, setting Isolated=true, then extracting the resulting comClass elements from the manifest into my own SxS manifest. Also, it seems to create an Interop.XXX.dll file: what is that for?

Some example error messages:

"Retrieving the COM class factory for component with CLSID {012A4BEB-99EC-4A65-A4AF-7D09A20B5034} failed due to the following error: 80040154."

"HSREADWRITELib::ReadWriteData, CreateInstance"
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is the most basic failure you can get from reg-free COM, it is not using the manifest or the manifest is incorrect. Verify that your manifest has a <file> element that names the COM DLL and contains a <comClass> element with a “clsid” attribute that has the same guid as the one that the exception message is complaining about.

    Then make sure that the manifest is embedded in the client executable. You can see it with File + Open + File in Visual Studio, open the RT_MANIFEST node.

    • 0