| Previous | Next |
| COMADMIN_E_USERPASSWDNOTVALID | COMADMIN_E_REMOTEINTERFACE |
COMADMIN_E_CLSIDORIIDMISMATCH
COMADMIN_E_CLSIDORIIDMISMATCH is the failure HRESULT 0x80110418 (signed decimal -2146368488, unsigned decimal 2148598808). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0418.
COM registration, type library, and component installation: exact meaning of COMADMIN_E_CLSIDORIIDMISMATCH
CLSID or IID metadata in the application file does not match the corresponding component binaries. InstallApplication compares packaged class/interface identities with DLL or type-library metadata and detects disagreement.
AllStat records this condition as “Application file CLSIDs or IIDs do not match corresponding DLLs”.
Evidence to collect before repair
- The result investigation needs CLSID/IID/LIBID values and 32/64-bit registry view so the exact failing boundary remains reconstructable.
- preserve component, type-library, and proxy/stub paths with hashes; it anchors the failure to the real administration object.
- Evidence for it should include loader or DllRegisterServer/DllGetClassObject result, captured before a repair changes state.
- Collect COM+ installation ErrorInfo and relevant event records when diagnosing this result; without it the symbolic HRESULT is underdetermined.
Where the result occurs
The COM+ catalog presents a split view of RegDB and Windows class/type-library registration, so the failing stage must be identified before editing either store. In the specific case of this result, preserve package and binary hashes, enumerate CLSIDs/IIDs from the type library, and identify which artifact came from a different build.
Diagnostic sequence
- To isolate this result, verify the exact binary architecture and dependencies.
- load and inspect the matching type library without substituting another version.
- At the boundary, repair registration using the component installer.
- The next it diagnostic action is to install rather than import when full interface metadata is required.
- To isolate it, repopulate the catalog and test class activation after repair.
Retry and recovery
Rebuild and re-export a coherent package from one release; never edit GUIDs inside the package to force installation.
Practical administration scenario
A package contains a new DLL beside an old exported catalog manifest, so the interface GUID sets no longer agree.
Difference from nearby COMADMIN results
COMADMIN_E_REMOTEINTERFACE concerns missing or changed interface information, while this code establishes an identity mismatch with the DLLs.
Official Microsoft references
- Microsoft: COMADMIN error codes
- Microsoft: the COM+ catalog
- Microsoft: ICOMAdminCatalog::InstallComponent
- Microsoft: installing new components
- Microsoft: Components collection
Looking for a different code? Search another status or error code.