What does HRESULT 0x80110403 (COMADMIN_E_KEYMISSING) mean?

 
Previous Next
COMADMIN_E_OBJECTINVALID COMADMIN_E_ALREADYINSTALLED

COMADMIN_E_KEYMISSING

COMADMIN_E_KEYMISSING is the failure HRESULT 0x80110403 (signed decimal -2146368509, unsigned decimal 2148598787). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0403.

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

The requested object key no longer resolves in the COM+ catalog. A related collection, PopulateByKey request, update, or delete references a catalog item that is absent in the current generation.

AllStat records this condition as “The object was not found in the catalog”.

Where COMADMIN_E_KEYMISSING 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_KEYMISSING, log the parent collection, key type, object ID, and whether the collection was repopulated after another administrator changed the catalog.

Evidence to collect before repair

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

Diagnostic sequence for COMADMIN_E_KEYMISSING

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

Practical administration scenario

A component key cached by a management process becomes stale after the application is reinstalled, and a later property update returns this HRESULT.

Retry and recovery

Refresh the hierarchy and resolve a current key; recreate the object only when deployment state proves that it should exist.

Difference from nearby COMADMIN results

COMADMIN_E_NOTINREGISTRY concerns Windows registry lookup, while this value concerns the COM+ catalog key.

Official Microsoft references for COMADMIN_E_KEYMISSING

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