What does HRESULT 0x80110483 (COMADMIN_E_CAT_UNACCEPTABLEBITNESS) mean?

 
Previous Next
COMADMIN_E_CAT_BITNESSMISMATCH COMADMIN_E_CAT_WRONGAPPBITNESS

COMADMIN_E_CAT_UNACCEPTABLEBITNESS

COMADMIN_E_CAT_UNACCEPTABLEBITNESS is the failure HRESULT 0x80110483 (signed decimal -2146368381, unsigned decimal 2148598915). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0483.

COM+ binary architecture validation: exact meaning of COMADMIN_E_CAT_UNACCEPTABLEBITNESS

A supplied binary has an unknown or unacceptable architecture type. COM+ inspects a component or package file and cannot classify it as a supported binary for the target catalog operation.

AllStat records this condition as “A binary of unknown or invalid type was provided”.

Where COMADMIN_E_CAT_UNACCEPTABLEBITNESS 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 COMADMIN_E_CAT_UNACCEPTABLEBITNESS, capture PE headers, file integrity, architecture tools output, package source, and target platform.

Evidence to collect before repair

  • Evidence for COMADMIN_E_CAT_UNACCEPTABLEBITNESS should include PE machine type and file hash for every binary, captured before a repair changes state.
  • Collect application component bitness setting when diagnosing COMADMIN_E_CAT_UNACCEPTABLEBITNESS; without it the symbolic HRESULT is underdetermined.
  • The COMADMIN_E_CAT_UNACCEPTABLEBITNESS investigation needs type-library and proxy/stub architecture so the exact failing boundary remains reconstructable.
  • For COMADMIN_E_CAT_UNACCEPTABLEBITNESS, preserve target OS architecture and registry view; it anchors the failure to the real administration object.

Diagnostic sequence for COMADMIN_E_CAT_UNACCEPTABLEBITNESS

  • At the COMADMIN_E_CAT_UNACCEPTABLEBITNESS boundary, inventory all package binaries with architecture tools.
  • The next COMADMIN_E_CAT_UNACCEPTABLEBITNESS diagnostic action is to replace corrupt or unknown files.
  • To isolate COMADMIN_E_CAT_UNACCEPTABLEBITNESS, separate incompatible architecture deployments.
  • For COMADMIN_E_CAT_UNACCEPTABLEBITNESS, configure the application for the intended component architecture.
  • At the COMADMIN_E_CAT_UNACCEPTABLEBITNESS boundary, reinstall and test class activation in the matching process.

Difference from nearby COMADMIN results

COMADMIN_E_CAT_BITNESSMISMATCH compares valid but incompatible types; this value rejects the binary type itself.

Retry and recovery

Replace the file with a valid supported COM binary built for the deployment platform.

Practical administration scenario

A package mistakenly includes a non-PE data file under a DLL name and COM+ cannot accept its bitness.

Official Microsoft references for COMADMIN_E_CAT_UNACCEPTABLEBITNESS

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