| Previous | Next |
| COMADMIN_E_NOSERVERSHARE | COMADMIN_E_BADREGISTRYLIBID |
COMADMIN_E_DLLLOADFAILED
COM registration, type library, and component installation: exact meaning of COMADMIN_E_DLLLOADFAILED
A DLL required by COM+ administration could not be loaded. Component installation or registration reaches the loader before any registrar or class-factory work can occur.
Windows describes this condition as “DLL could not be loaded”.
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, collect loader error, architecture, dependency resolution, search path, file signature, and whether the file is blocked or damaged.
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 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.
- Record COM+ installation ErrorInfo and relevant event records.
Diagnostic sequence
- Verify the exact binary architecture and dependencies.
- load and inspect the matching type library without substituting another version.
- The next 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
Deploy a compatible binary with all dependencies and repeat the supported installation operation.
Difference from nearby COMADMIN results
COMADMIN_E_DLLREGISTERSERVER occurs after successful loading; COMADMIN_E_COMPFILE_LOADDLLFAIL is the component-file analysis variant.
Practical administration scenario
A 64-bit administration process is given a 32-bit-only DLL path and loader validation fails before registration.
Official Microsoft references
Looking for a different code? Search another status or error code.