What does HRESULT 0x80110426 (COMADMIN_E_COMPFILE_GETCLASSOBJ) mean?

 
Previous Next
COMADMIN_E_COMPFILE_LOADDLLFAIL COMADMIN_E_COMPFILE_CLASSNOTAVAIL

COMADMIN_E_COMPFILE_GETCLASSOBJ

COMADMIN_E_COMPFILE_GETCLASSOBJ is the failure HRESULT 0x80110426 (signed decimal -2146368474, unsigned decimal 2148598822). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0426.

COM+ component-file analysis: exact meaning of COMADMIN_E_COMPFILE_GETCLASSOBJ

COM+ loaded the DLL but could not obtain a class object from it. Component inspection calls the module class-factory path, commonly through DllGetClassObject, and that stage fails.

AllStat records this condition as “GetClassObject failed in the DLL”.

Where the result 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 this result, record requested CLSID, DllGetClassObject result, exported entry points, registration/type-library class list, and binary version.

Evidence to collect before repair

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

Diagnostic sequence

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

Practical administration scenario

A DLL exports DllGetClassObject but returns CLASS_E_CLASSNOTAVAILABLE for a CLSID declared in the package.

Retry and recovery

Use a binary that implements the declared classes and repair the package metadata before reinstalling.

Difference from nearby COMADMIN results

COMADMIN_E_COMPFILE_CLASSNOTAVAIL means the DLL lacks classes listed by the type library; this value focuses on obtaining the class object.

Official Microsoft references

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