| Previous | Next |
| COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES | COMADMIN_E_AMBIGUOUS_APPLICATION_NAME |
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED
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.
Windows describes this condition as “Applications that contain one or more imported components cannot be installed into a non-base partition”.
Where the result 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 this result, 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 this result; without it the symbolic HRESULT is underdetermined.
- Record CLSID, DLL, type-library, and interface metadata.
- Preserve source and destination partition IDs; it anchors the failure to the real administration object.
- Evidence should include the package/application used for partition installation, captured before a repair changes state.
Diagnostic sequence
- The next diagnostic action is to enumerate all components and identify imported entries.
- To isolate it, obtain deployable binaries and metadata for those classes.
- replace imports with supported component installation.
- re-export the coherent application.
- The next diagnostic 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
Looking for a different code? Search another status or error code.
