What does HRESULT 0x8011081B (COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS) mean?

 
Previous Next
COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_1_0_FORMAT COMADMIN_E_COMP_MOVE_SOURCE

COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS

COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS is the failure HRESULT 0x8011081B (signed decimal -2146367461, unsigned decimal 2148599835). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x081B.

Legacy-component placement across COM+ partitions: exact meaning of COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS

At least one legacy component is being placed in a non-base partition, which COM+ forbids. The partition exists and the package may be readable, but the component model is not compatible with isolated non-base placement.

AllStat records the Windows SDK description as “Legacy components may not exist in non-base partitions.”

Where COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS occurs

The result is produced during partition-aware installation, move, copy, or import after COM+ classifies the component and destination partition.

Typical cause branches

  • an imported legacy component is targeted at a tenant/non-base partition.
  • an application containing legacy classes is moved out of the base partition.
  • a package built from the base partition is installed into a non-base partition without compatibility review.
  • automation checks only package format and misses the legacy component classification.

Evidence to collect before changing the catalog

  • destination partition ID and whether it is the base/global partition.
  • component CLSIDs, installation/import provenance, type libraries, and registration ownership.
  • source application/partition and exact move/copy/install method.
  • package manifest and COM+ ErrorInfo naming the affected component when available.

Diagnostic sequence for COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS

  • identify every component COM+ classifies as legacy.
  • confirm the business requirement for non-base isolation.
  • keep the component/application in the base partition or replace it with a partition-compatible implementation.
  • rebuild the package or move plan around the supported placement.
  • test activation routing and security after the corrected deployment.

Retry and recovery

Retry only after changing destination to the base partition or removing/replacing the legacy component. Partition recreation does not alter component compatibility.

What this HRESULT does not establish

The HRESULT does not mean all components in the application are legacy. Identify the specific classes before redesigning the entire deployment.

Difference from nearby COMADMIN results

COMADMIN_E_PARTITION_MSI_ONLY concerns package form; COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_1_0_FORMAT concerns export representation. This value concerns runtime/catalog placement in a non-base partition.

Practical administration scenario

A tenant rollout moves an old imported COM component from the global application into a dedicated partition and COM+ rejects the placement.

Developer and operations guidance

Record component CLSIDs, legacy/import status, source and destination partition IDs, method, package hash, and the first component-specific ErrorInfo entry.

Official Microsoft references for COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS

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