What does HRESULT 0x80110446 (COMADMIN_E_APPLID_MATCHES_CLSID) mean?

 
Previous Next
COMADMIN_E_OBJECTNOTPOOLABLE COMADMIN_E_ROLE_DOES_NOT_EXIST

COMADMIN_E_APPLID_MATCHES_CLSID

COMADMIN_E_APPLID_MATCHES_CLSID is the failure HRESULT 0x80110446 (signed decimal -2146368442, unsigned decimal 2148598854). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0446.

COM+ catalog object and collection state: exact meaning of COMADMIN_E_APPLID_MATCHES_CLSID

The proposed COM+ application ID collides with an installed class CLSID. Application creation validates global GUID namespaces before adding the new AppID.

AllStat records this condition as “A CLSID with the same GUID as the new application ID is already installed on this machine”.

Evidence to collect before repair

  • The COMADMIN_E_APPLID_MATCHES_CLSID investigation needs collection name, parent key, object key, and application/partition ID so the exact failing boundary remains reconstructable.
  • For COMADMIN_E_APPLID_MATCHES_CLSID, preserve the exact administration method and pending property values; it anchors the failure to the real administration object.
  • Evidence for COMADMIN_E_APPLID_MATCHES_CLSID should include ErrorInfo entries and COM+ System Application events, captured before a repair changes state.
  • Collect a fresh Populate result taken before any repair when diagnosing COMADMIN_E_APPLID_MATCHES_CLSID; without it the symbolic HRESULT is underdetermined.

Where COMADMIN_E_APPLID_MATCHES_CLSID occurs

The authoritative state is the logical COM+ catalog exposed through COMAdmin collections, not a single registry key or an old in-memory object. In the specific case of COMADMIN_E_APPLID_MATCHES_CLSID, resolve the GUID as both AppID and CLSID and identify the binary owning the existing class registration.

Diagnostic sequence for COMADMIN_E_APPLID_MATCHES_CLSID

  • To isolate COMADMIN_E_APPLID_MATCHES_CLSID, recreate the catalog session and repopulate the relevant hierarchy.
  • For COMADMIN_E_APPLID_MATCHES_CLSID, resolve objects by stable identifiers rather than display names.
  • At the COMADMIN_E_APPLID_MATCHES_CLSID boundary, compare pending values with collection property metadata.
  • The next COMADMIN_E_APPLID_MATCHES_CLSID diagnostic action is to save the smallest coherent change set and inspect ErrorInfo.
  • To isolate COMADMIN_E_APPLID_MATCHES_CLSID, verify the committed object by repopulating after SaveChanges.

Retry and recovery

Generate a new application GUID and preserve the existing class identity; do not delete a valid CLSID to reuse it.

Practical administration scenario

A deployment template accidentally reuses a component CLSID as the new application AppID.

Difference from nearby COMADMIN results

COMADMIN_E_APPLICATIONEXISTS reports an existing application, while this code reports a cross-kind GUID collision.

Official Microsoft references for COMADMIN_E_APPLID_MATCHES_CLSID

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