| Previous | Next |
| COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES | COMADMIN_E_AMBIGUOUS_APPLICATION_NAME |
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED is the failure HRESULT 0x8011045B (signed decimal -2146368421, unsigned decimal 2148598875). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x045B.
COM+ partition administration: exact meaning of COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED
An application containing imported components cannot be installed into a non-base partition. Partition installation checks component provenance and rejects registry-imported classes lacking full deployable metadata.
AllStat records this condition as “Applications that contain one or more imported components cannot be installed into a non-base partition”.
Where COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED occurs
Partitions are logical containers with explicit IDs, names, user defaults, application contents, and platform enablement; operations must use the intended partition rather than assume a global namespace. In the specific case of COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED, enumerate imported components, their CLSIDs, type-library/interface metadata, and target partition.
Evidence to collect before repair
- Collect installed-versus-imported provenance for every component when diagnosing
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED; without it the symbolic HRESULT is underdetermined. - The
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWEDinvestigation needs CLSID, DLL, type-library, and interface metadata so the exact failing boundary remains reconstructable. - For
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED, preserve source and destination partition IDs; it anchors the failure to the real administration object. - Evidence for
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWEDshould include the package/application used for partition installation, captured before a repair changes state.
Diagnostic sequence for COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED
- The next
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWEDdiagnostic action is to enumerate all components and identify imported entries. - To isolate
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED, obtain deployable binaries and metadata for those classes. - For
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED, replace imports with supported component installation. - At the
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWEDboundary, re-export the coherent application. - The next
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWEDdiagnostic action is to install into the non-base partition and verify interfaces and activation.
Practical administration scenario
A legacy application built by importing registered classes is exported and then targeted at a tenant partition.
Retry and recovery
Install components properly into a deployable application or keep the application in the base partition.
Difference from nearby COMADMIN results
COMADMIN_E_CANT_SUBSCRIBE_TO_COMPONENT can also involve imported components, but at event-subscription configuration rather than partition installation.
Official Microsoft references for COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED
- Microsoft: COMADMIN error codes
- Microsoft: what COM+ partitions are
- Microsoft: managing local COM+ partitions
- Microsoft: ICOMAdminCatalog2
- Microsoft: the COM+ catalog
Looking for a different code? Search another status or error code.