| Previous | Next |
| COMADMIN_E_COMPFILE_BADTLB | COMADMIN_E_NOTCHANGEABLE |
COMADMIN_E_COMPFILE_NOTINSTALLABLE
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.
Windows describes this condition as “The file does not contain components or component information”.
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, 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 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 this result; without it the symbolic HRESULT is underdetermined.
- Record type-library LIBID/version and declared coclasses.
- Preserve DllGetClassObject behavior for the expected CLSIDs; it anchors the failure to the real administration object.
Diagnostic sequence
- prove the deployment selected the intended binary.
- The next diagnostic action is to resolve loader and dependency failures before registry changes.
- To isolate it, compare type-library declarations with implemented class factories.
- rebuild binary and metadata from one source revision.
- rerun InstallComponent and inspect the resulting Components collection.
Difference from nearby COMADMIN results
COMADMIN_E_COMPFILE_BADTLB says expected metadata cannot be loaded; it 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
Looking for a different code? Search another status or error code.