What does HRESULT 0x80110480 (COMADMIN_E_MIG_VERSIONNOTSUPPORTED) mean?

 
Previous Next
COMADMIN_E_REGDB_ALREADYRUNNING COMADMIN_E_MIG_SCHEMANOTFOUND

COMADMIN_E_MIG_VERSIONNOTSUPPORTED

COMADMIN_E_MIG_VERSIONNOTSUPPORTED is the failure HRESULT 0x80110480 (signed decimal -2146368384, unsigned decimal 2148598912). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0480.

COM+ catalog migration: exact meaning of COMADMIN_E_MIG_VERSIONNOTSUPPORTED

The installed COM+ registry database version cannot be migrated by this migration path. Catalog migration reads source-version metadata and rejects it as unsupported.

AllStat records this condition as “This version of the COM+ registry database cannot be migrated”.

Where COMADMIN_E_MIG_VERSIONNOTSUPPORTED occurs

Catalog migration is versioned schema transformation; a database copied from another release is not equivalent to an application package exported through COMAdmin. In the specific case of COMADMIN_E_MIG_VERSIONNOTSUPPORTED, record source OS/catalog version, destination version, backup provenance, and every intermediate upgrade requirement.

Evidence to collect before repair

  • For COMADMIN_E_MIG_VERSIONNOTSUPPORTED, preserve source and target OS/catalog versions; it anchors the failure to the real administration object.
  • Evidence for COMADMIN_E_MIG_VERSIONNOTSUPPORTED should include schema identifiers and servicing state, captured before a repair changes state.
  • Collect backup provenance and restore sequence when diagnosing COMADMIN_E_MIG_VERSIONNOTSUPPORTED; without it the symbolic HRESULT is underdetermined.
  • The COMADMIN_E_MIG_VERSIONNOTSUPPORTED investigation needs available application exports and component installers so the exact failing boundary remains reconstructable.

Diagnostic sequence for COMADMIN_E_MIG_VERSIONNOTSUPPORTED

  • For COMADMIN_E_MIG_VERSIONNOTSUPPORTED, preserve the original catalog backup.
  • At the COMADMIN_E_MIG_VERSIONNOTSUPPORTED boundary, verify a Microsoft-supported upgrade sequence.
  • The next COMADMIN_E_MIG_VERSIONNOTSUPPORTED diagnostic action is to repair COM+ servicing resources when schemas are missing.
  • To isolate COMADMIN_E_MIG_VERSIONNOTSUPPORTED, prefer export/redeployment for applications when direct migration is unsupported.
  • For COMADMIN_E_MIG_VERSIONNOTSUPPORTED, validate applications and activation after migration.

Retry and recovery

Use a supported upgrade sequence or export/redeploy applications through documented package operations.

Difference from nearby COMADMIN results

COMADMIN_E_SESSION concerns live administration compatibility; this value concerns persistent database migration.

Practical administration scenario

An old catalog backup is restored directly onto a much newer server without the required intermediate migration path.

Official Microsoft references for COMADMIN_E_MIG_VERSIONNOTSUPPORTED

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