What does HRESULT 0x80110429 (COMADMIN_E_COMPFILE_NOTINSTALLABLE) mean?

 
Previous Next
COMADMIN_E_COMPFILE_BADTLB COMADMIN_E_NOTCHANGEABLE

COMADMIN_E_COMPFILE_NOTINSTALLABLE

COMADMIN_E_COMPFILE_NOTINSTALLABLE is the failure HRESULT 0x80110429 (signed decimal -2146368471, unsigned decimal 2148598825). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0429.

COM+ component-file analysis: exact meaning of COMADMIN_E_COMPFILE_NOTINSTALLABLE

The supplied file contains no installable COM+ components or usable component information. COM+ completes basic file inspection but finds neither discoverable components nor registration metadata suitable for installation.

AllStat records this condition as “The file does not contain components or component information”.

Where COMADMIN_E_COMPFILE_NOTINSTALLABLE 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_NOTINSTALLABLE, verify that the file is actually a COM server, exposes classes, carries a type library or registrar information, and matches the intended architecture.

Evidence to collect before repair

  • Evidence for COMADMIN_E_COMPFILE_NOTINSTALLABLE 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_NOTINSTALLABLE; without it the symbolic HRESULT is underdetermined.
  • The COMADMIN_E_COMPFILE_NOTINSTALLABLE investigation needs type-library LIBID/version and declared coclasses so the exact failing boundary remains reconstructable.
  • For COMADMIN_E_COMPFILE_NOTINSTALLABLE, preserve DllGetClassObject behavior for the expected CLSIDs; it anchors the failure to the real administration object.

Diagnostic sequence for COMADMIN_E_COMPFILE_NOTINSTALLABLE

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

Difference from nearby COMADMIN results

COMADMIN_E_COMPFILE_BADTLB says expected metadata cannot be loaded; this result can mean there is no applicable component metadata at all.

Retry and recovery

Select the correct component binary or add supported registration metadata during the build.

Practical administration scenario

An operator selects a helper DLL that contains utility code but no COM coclasses, so the install wizard cannot add components.

Official Microsoft references for COMADMIN_E_COMPFILE_NOTINSTALLABLE

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