| Previous | Next |
| COMADMIN_E_MIG_VERSIONNOTSUPPORTED | COMADMIN_E_CAT_BITNESSMISMATCH |
COMADMIN_E_MIG_SCHEMANOTFOUND
COMADMIN_E_MIG_SCHEMANOTFOUND is the failure HRESULT 0x80110481 (signed decimal -2146368383, unsigned decimal 2148598913). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0481.
COM+ catalog migration: exact meaning of COMADMIN_E_MIG_SCHEMANOTFOUND
The schema version required for COM+ registry-database migration is missing. Migration selects a source schema and cannot locate its transformation metadata in RegDB.
AllStat records this condition as “The schema version to be migrated could not be found in the COM+ registry database”.
Where COMADMIN_E_MIG_SCHEMANOTFOUND 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_SCHEMANOTFOUND, record catalog version, schema identifiers, installation/servicing state, and whether migration resources match the OS build.
Evidence to collect before repair
- Evidence for
COMADMIN_E_MIG_SCHEMANOTFOUNDshould include source and target OS/catalog versions, captured before a repair changes state. - Collect schema identifiers and servicing state when diagnosing
COMADMIN_E_MIG_SCHEMANOTFOUND; without it the symbolic HRESULT is underdetermined. - The
COMADMIN_E_MIG_SCHEMANOTFOUNDinvestigation needs backup provenance and restore sequence so the exact failing boundary remains reconstructable. - For
COMADMIN_E_MIG_SCHEMANOTFOUND, preserve available application exports and component installers; it anchors the failure to the real administration object.
Diagnostic sequence for COMADMIN_E_MIG_SCHEMANOTFOUND
- At the
COMADMIN_E_MIG_SCHEMANOTFOUNDboundary, preserve the original catalog backup. - The next
COMADMIN_E_MIG_SCHEMANOTFOUNDdiagnostic action is to verify a Microsoft-supported upgrade sequence. - To isolate
COMADMIN_E_MIG_SCHEMANOTFOUND, repair COM+ servicing resources when schemas are missing. - For
COMADMIN_E_MIG_SCHEMANOTFOUND, prefer export/redeployment for applications when direct migration is unsupported. - At the
COMADMIN_E_MIG_SCHEMANOTFOUNDboundary, validate applications and activation after migration.
Difference from nearby COMADMIN results
COMADMIN_E_MIG_VERSIONNOTSUPPORTED means the version is known but unsupported; this value means the needed schema cannot be found.
Retry and recovery
Repair the COM+ installation or use a valid catalog backup and supported migration path.
Practical administration scenario
A partially serviced system has a catalog version marker but lacks the matching migration schema resources.
Official Microsoft references for COMADMIN_E_MIG_SCHEMANOTFOUND
- Microsoft: COMADMIN error codes
- Microsoft: the COM+ catalog
- Microsoft: deploying COM+ applications
- Microsoft: ICOMAdminCatalog::InstallApplication
- Microsoft: automating COM+ administration
Looking for a different code? Search another status or error code.