| Previous | Next |
| COMADMIN_E_COMPFILE_NOREGISTRAR | COMADMIN_E_SERVICENOTINSTALLED |
COMADMIN_E_COREQCOMPINSTALLED
COM+ installation identity and duplicate state: exact meaning of COMADMIN_E_COREQCOMPINSTALLED
Another component from the same DLL is already installed in a way that constrains this installation. COM+ enforces co-installation requirements for classes implemented by a shared component binary.
Windows describes this condition as “A component in the same DLL is already installed”.
Where the result occurs
COM+ installation updates the catalog, class registration, type-library metadata, and files as one supported deployment workflow; a duplicate result must be resolved at that workflow boundary. In the specific case of this result, enumerate all CLSIDs in the DLL, their current application assignments, versions, and installation method.
Evidence to collect before repair
- Preserve application ID, CLSID, component DLL path, version, and hash; it anchors the failure to the real administration object.
- Evidence should include existing Components and Applications collection entries, captured before a repair changes state.
- Collect installer/package identity and previous deployment result when diagnosing this result; without it the symbolic HRESULT is underdetermined.
- Record registry and catalog ownership for the conflicting identifier.
Diagnostic sequence
- enumerate the existing application and component before changing anything.
- decide whether the operation is install, update, repair, or migration.
- The next diagnostic action is to use the owning installer or COMAdmin method for the chosen path.
- To isolate it, avoid manual deletion of only catalog or registry fragments.
- repopulate and compare the resulting identities and file versions.
Retry and recovery
Manage the DLL’s component set coherently—update, remove, or install related classes according to the package design.
Difference from nearby COMADMIN results
COMADMIN_E_COMPONENTEXISTS concerns the same component identity; it is driven by a co-required component from the same DLL.
Practical administration scenario
A DLL implements two tightly related classes, and deployment tries to install only the second into an incompatible application.
Official Microsoft references
Looking for a different code? Search another status or error code.