What does HRESULT 0x80110427 (COMADMIN_E_COMPFILE_CLASSNOTAVAIL) mean?

 
Previous Next
COMADMIN_E_COMPFILE_GETCLASSOBJ COMADMIN_E_COMPFILE_BADTLB

COMADMIN_E_COMPFILE_CLASSNOTAVAIL

COMADMIN_E_COMPFILE_CLASSNOTAVAIL is the failure HRESULT 0x80110427 (signed decimal -2146368473, unsigned decimal 2148598823). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0427.

COM+ component-file analysis: exact meaning of COMADMIN_E_COMPFILE_CLASSNOTAVAIL

The DLL does not implement one or more components listed in its type library. COM+ compares coclass declarations with class factories exposed by the component file.

AllStat records this condition as “The DLL does not support the components listed in the TypeLib”.

Where COMADMIN_E_COMPFILE_CLASSNOTAVAIL occurs

This HRESULT is raised while COM+ inspects a proposed component file for classes, type information, and class factories before it can create usable catalog components. In the specific case of COMADMIN_E_COMPFILE_CLASSNOTAVAIL, enumerate coclasses in the exact type-library version and test each CLSID against the binary class factory.

Evidence to collect before repair

  • Evidence for COMADMIN_E_COMPFILE_CLASSNOTAVAIL should include exact file path, hash, PE architecture, and signature, captured before a repair changes state.
  • Collect loader diagnostics and dependent-module list when diagnosing COMADMIN_E_COMPFILE_CLASSNOTAVAIL; without it the symbolic HRESULT is underdetermined.
  • The COMADMIN_E_COMPFILE_CLASSNOTAVAIL investigation needs type-library LIBID/version and declared coclasses so the exact failing boundary remains reconstructable.
  • For COMADMIN_E_COMPFILE_CLASSNOTAVAIL, preserve DllGetClassObject behavior for the expected CLSIDs; it anchors the failure to the real administration object.

Diagnostic sequence for COMADMIN_E_COMPFILE_CLASSNOTAVAIL

  • At the COMADMIN_E_COMPFILE_CLASSNOTAVAIL boundary, prove the deployment selected the intended binary.
  • The next COMADMIN_E_COMPFILE_CLASSNOTAVAIL diagnostic action is to resolve loader and dependency failures before registry changes.
  • To isolate COMADMIN_E_COMPFILE_CLASSNOTAVAIL, compare type-library declarations with implemented class factories.
  • For COMADMIN_E_COMPFILE_CLASSNOTAVAIL, rebuild binary and metadata from one source revision.
  • At the COMADMIN_E_COMPFILE_CLASSNOTAVAIL boundary, rerun InstallComponent and inspect the resulting Components collection.

Difference from nearby COMADMIN results

COMADMIN_E_CLSIDORIIDMISMATCH can involve package-to-binary identity differences; this value specifically says declared components are unavailable from the DLL.

Retry and recovery

Rebuild the DLL and type library from the same source/version, then reinstall the coherent pair.

Practical administration scenario

A stale type library still advertises a removed coclass after the DLL implementation was simplified.

Official Microsoft references for COMADMIN_E_COMPFILE_CLASSNOTAVAIL


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