| Previous | Next |
| COMADMIN_E_SYSTEMAPP | COMADMIN_E_COREQCOMPINSTALLED |
COMADMIN_E_COMPFILE_NOREGISTRAR
COMADMIN_E_COMPFILE_NOREGISTRAR is the failure HRESULT 0x80110434 (signed decimal -2146368460, unsigned decimal 2148598836). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0434.
COM registration, type library, and component installation: exact meaning of COMADMIN_E_COMPFILE_NOREGISTRAR
The component file references registrar functionality that is not available. COM+ discovers a registrar dependency in component metadata but cannot instantiate or locate it.
AllStat records this condition as “The component registrar referenced in this file is not available”.
Where COMADMIN_E_COMPFILE_NOREGISTRAR 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 COMADMIN_E_COMPFILE_NOREGISTRAR, record registrar CLSID/progID, registration, binary path, architecture, and package contents.
Evidence to collect before repair
- Evidence for
COMADMIN_E_COMPFILE_NOREGISTRARshould include CLSID/IID/LIBID values and 32/64-bit registry view, captured before a repair changes state. - Collect component, type-library, and proxy/stub paths with hashes when diagnosing
COMADMIN_E_COMPFILE_NOREGISTRAR; without it the symbolic HRESULT is underdetermined. - The
COMADMIN_E_COMPFILE_NOREGISTRARinvestigation needs loader or DllRegisterServer/DllGetClassObject result so the exact failing boundary remains reconstructable. - For
COMADMIN_E_COMPFILE_NOREGISTRAR, preserve COM+ installation ErrorInfo and relevant event records; it anchors the failure to the real administration object.
Diagnostic sequence for COMADMIN_E_COMPFILE_NOREGISTRAR
- At the
COMADMIN_E_COMPFILE_NOREGISTRARboundary, verify the exact binary architecture and dependencies. - The next
COMADMIN_E_COMPFILE_NOREGISTRARdiagnostic action is to load and inspect the matching type library without substituting another version. - To isolate
COMADMIN_E_COMPFILE_NOREGISTRAR, repair registration using the component installer. - For
COMADMIN_E_COMPFILE_NOREGISTRAR, install rather than import when full interface metadata is required. - At the
COMADMIN_E_COMPFILE_NOREGISTRARboundary, repopulate the catalog and test class activation after repair.
Difference from nearby COMADMIN results
COMADMIN_E_REGISTRARFAILED means the registrar ran and reported errors; this code means the referenced registrar could not be used.
Retry and recovery
Install the required registrar or rebuild the component package to use an available supported registration path.
Practical administration scenario
A component package names a custom registrar DLL that was omitted from the destination deployment.
Official Microsoft references for COMADMIN_E_COMPFILE_NOREGISTRAR
- 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.