| Previous | Next |
| COMADMIN_E_MIG_SCHEMANOTFOUND | COMADMIN_E_CAT_UNACCEPTABLEBITNESS |
COMADMIN_E_CAT_BITNESSMISMATCH
COMADMIN_E_CAT_BITNESSMISMATCH is the failure HRESULT 0x80110482 (signed decimal -2146368382, unsigned decimal 2148598914). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0482.
COM+ binary architecture validation: exact meaning of COMADMIN_E_CAT_BITNESSMISMATCH
COM+ detects a mismatch between binary types participating in the operation. Component/package/partition processing compares architecture metadata and finds incompatible 32-bit and 64-bit artifacts or expectations.
AllStat records this condition as “There was a type mismatch between binaries”.
Where the result occurs
COM+ evaluates binary architecture across components, type libraries, proxy/stub DLLs, packages, and application settings; file extension or path alone does not establish bitness. In the specific case of this result, record PE machine type for every DLL/proxy/stub, application bitness settings, registry view, and target OS architecture.
Evidence to collect before repair
- preserve PE machine type and file hash for every binary; it anchors the failure to the real administration object.
- Evidence for it should include application component bitness setting, captured before a repair changes state.
- Collect type-library and proxy/stub architecture when diagnosing this result; without it the symbolic HRESULT is underdetermined.
- The result investigation needs target OS architecture and registry view so the exact failing boundary remains reconstructable.
Diagnostic sequence
- inventory all package binaries with architecture tools.
- At the boundary, replace corrupt or unknown files.
- The next this result diagnostic action is to separate incompatible architecture deployments.
- To isolate this result, configure the application for the intended component architecture.
- reinstall and test class activation in the matching process.
Retry and recovery
Deploy architecture-consistent binaries and configure the application for that component set.
Difference from nearby COMADMIN results
COMADMIN_E_CAT_UNACCEPTABLEBITNESS means a binary type is unknown or invalid, while this code means recognized types disagree.
Practical administration scenario
A 32-bit component package includes a 64-bit proxy/stub DLL and COM+ rejects the inconsistent set.
Official Microsoft references
- Microsoft: COMADMIN error codes
- Microsoft: Components collection
- Microsoft: ICOMAdminCatalog::InstallComponent
- Microsoft: configuring COM+ applications
- Microsoft: the COM+ catalog
Looking for a different code? Search another status or error code.