What does HRESULT 0x80110411 (COMADMIN_E_NOREGISTRYCLSID) mean?

 
Previous Next
COMADMIN_E_INVALIDUSERIDS COMADMIN_E_BADREGISTRYPROGID

COMADMIN_E_NOREGISTRYCLSID

COMADMIN_E_NOREGISTRYCLSID is the failure HRESULT 0x80110411 (signed decimal -2146368495, unsigned decimal 2148598801). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0411.

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.

AllStat records this condition as “The component's CLSID is missing or corrupt”.

Where COMADMIN_E_NOREGISTRYCLSID 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_NOREGISTRYCLSID, verify the exact CLSID, InprocServer32 or LocalServer32 registration, architecture-specific registry view, and owning binary.

Evidence to collect before repair

  • For COMADMIN_E_NOREGISTRYCLSID, preserve CLSID/IID/LIBID values and 32/64-bit registry view; it anchors the failure to the real administration object.
  • Evidence for COMADMIN_E_NOREGISTRYCLSID 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 COMADMIN_E_NOREGISTRYCLSID; without it the symbolic HRESULT is underdetermined.
  • The COMADMIN_E_NOREGISTRYCLSID investigation needs COM+ installation ErrorInfo and relevant event records so the exact failing boundary remains reconstructable.

Diagnostic sequence for COMADMIN_E_NOREGISTRYCLSID

  • For COMADMIN_E_NOREGISTRYCLSID, verify the exact binary architecture and dependencies.
  • At the COMADMIN_E_NOREGISTRYCLSID boundary, load and inspect the matching type library without substituting another version.
  • The next COMADMIN_E_NOREGISTRYCLSID diagnostic action is to repair registration using the component installer.
  • To isolate COMADMIN_E_NOREGISTRYCLSID, install rather than import when full interface metadata is required.
  • For COMADMIN_E_NOREGISTRYCLSID, 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

For COMADMIN_E_NOREGISTRYCLSID, 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 for COMADMIN_E_NOREGISTRYCLSID

Looking for a different code? Search another status or error code.