| Previous | Next |
| COMADMIN_E_INVALIDUSERIDS | COMADMIN_E_BADREGISTRYPROGID |
COMADMIN_E_NOREGISTRYCLSID
COM registration, type library, and component installation: exact meaning of COMADMIN_E_NOREGISTRYCLSID
The component CLSID registration is missing or corrupt. COM+ installation or catalog reconciliation tries to connect component metadata to the class registration under Windows.
Windows describes this condition as “The component's CLSID is missing or corrupt”.
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, verify the exact CLSID, InprocServer32 or LocalServer32 registration, architecture-specific registry view, and owning binary.
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
Reinstall/register the correct component through its supported installer and then repeat COM+ installation.
Difference from nearby COMADMIN results
COMADMIN_E_BADREGISTRYPROGID concerns ProgID data, while this value identifies the CLSID registration required to identify the class.
Practical administration scenario
A 32-bit component is registered only in the wrong registry view, so 64-bit COM+ administration cannot find its CLSID metadata.
CLSID-specific registry checks
Inspect the class registration in the registry view that matches the administration and component architecture. Record whether the CLSID key exists, whether its server path points to the expected signed binary, and whether AppID or TypeLib links refer to objects that still exist. An entry visible to a 32-bit diagnostic tool is not proof that the corresponding 64-bit view contains the class.
Do not manufacture a minimal CLSID key merely to pass catalog lookup. The owning installer may also need to register threading model, ProgID, type library, proxy/stub, categories, and application identity. A supported reinstall produces a coherent registration set and lets COM+ repopulate its split catalog view.
Official Microsoft references
Looking for a different code? Search another status or error code.