| Previous | Next |
| COMADMIN_E_CLSIDORIIDMISMATCH | COMADMIN_E_DLLREGISTERSERVER |
COMADMIN_E_REMOTEINTERFACE
COMADMIN_E_REMOTEINTERFACE is the failure HRESULT 0x80110419 (signed decimal -2146368487, unsigned decimal 2148598809). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0419.
COM registration, type library, and component installation: exact meaning of COMADMIN_E_REMOTEINTERFACE
Required interface information is missing or changed for remote use. COM+ validates interface, type-library, or proxy/stub information needed to configure or export a remotely callable component.
AllStat records this condition as “Interface information is either missing or changed”.
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, compare registered IIDs, type-library versions, proxy/stub CLSIDs, and imported-versus-installed component status.
Evidence to collect before repair
- preserve CLSID/IID/LIBID values and 32/64-bit registry view; it anchors the failure to the real administration object.
- Evidence for it should include component, type-library, and proxy/stub paths with hashes, captured before a repair changes state.
- Collect loader or DllRegisterServer/DllGetClassObject result when diagnosing this result; without it the symbolic HRESULT is underdetermined.
- The result investigation needs COM+ installation ErrorInfo and relevant event records so the exact failing boundary remains reconstructable.
Diagnostic sequence
- verify the exact binary architecture and dependencies.
- At the boundary, load and inspect the matching type library without substituting another version.
- The next this result diagnostic action is to repair registration using the component installer.
- To isolate this result, install rather than import when full interface metadata is required.
- repopulate the catalog and test class activation after repair.
Retry and recovery
Install the component with complete interface metadata and regenerate any application proxy from the corrected server application.
Difference from nearby COMADMIN results
COMADMIN_E_CLSIDORIIDMISMATCH detects explicit identity disagreement; this value can reflect absent or changed remote-interface metadata.
Practical administration scenario
An imported component lacks type-library and marshaling information, so proxy generation cannot describe its remote interfaces.
Remote-interface metadata checks
Inventory every interface intended for cross-process or cross-computer use. Record each IID, type-library version, proxy/stub CLSID or automation-marshaling eligibility, and whether COM+ learned the component through installation or only through registry import. A class can activate locally while still lacking the interface description required to build a usable application proxy.
Compare the current binary and type library with the metadata captured when the application was packaged. Interface removal, IID reuse, a stale proxy/stub DLL, or importing a class without full type information creates a different failure boundary from a missing CLSID or bad ProgID. Reinstall complete interface metadata and regenerate the proxy rather than editing an exported package.
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.