What does HRESULT 0x80110809 (COMADMIN_E_OBJECT_DOES_NOT_EXIST) mean?

 
Previous Next
COMADMIN_E_OBJECT_PARENT_MISSING COMADMIN_E_APP_NOT_RUNNING

COMADMIN_E_OBJECT_DOES_NOT_EXIST

COMADMIN_E_OBJECT_DOES_NOT_EXIST is the failure HRESULT 0x80110809 (signed decimal -2146367479, unsigned decimal 2148599817). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0809.

Missing object at a COMAdmin operation boundary: exact meaning of COMADMIN_E_OBJECT_DOES_NOT_EXIST

One of the specified catalog objects or application instances cannot be found. The value is intentionally broad; the calling method and input object type determine whether the missing item is an application, component, process instance, or another catalog record.

AllStat records the Windows SDK description as “One of the specified objects cannot be found”.

Where COMADMIN_E_OBJECT_DOES_NOT_EXIST occurs

Methods such as InstallApplication and RecycleApplicationInstances document this result for different targets. Diagnosis must therefore begin with the exact method signature and the identifier variant, not with a global search for similarly named applications.

Typical cause branches

  • an object was deleted or an application reinstalled after its key was cached.
  • a friendly name resolved on one server or partition but the operation ran against another.
  • an application-instance GUID or process mapping expired after shutdown or recycling.
  • the caller supplied the wrong object type, key format, or collection generation.

Evidence to collect before changing the catalog

  • COMAdmin method name and complete non-secret target variant.
  • catalog server, partition, AppID, CLSID, instance ID, process ID, and collection generation.
  • fresh Populate/GetCollectionByQuery2 results for the same stable identifier.
  • deployment, recycle, shutdown, and deletion events preceding the failure.

Diagnostic sequence for COMADMIN_E_OBJECT_DOES_NOT_EXIST

  • identify the object type required by the specific method.
  • reconnect and resolve the target by GUID/key on the actual server and partition.
  • distinguish a missing definition from a missing live application instance.
  • stop using cached catalog objects after install, delete, move, or recycle operations.
  • recreate or restart only when authoritative state says the object should exist.

Retry and recovery

A retry is safe after refreshing identifiers or recreating the intended object. Retrying with the same stale instance GUID or wrong partition produces the same outcome.

What this HRESULT does not establish

The code does not say that the application package was never installed and does not distinguish object types on its own. That information must come from the API call and input identifiers.

Difference from nearby COMADMIN results

COMADMIN_E_APP_NOT_RUNNING applies when the application definition exists but has no running instance. COMADMIN_E_OBJECT_PARENT_MISSING concerns a child attached to an invalid parent, not a standalone lookup failure.

Practical administration scenario

A monitoring tool stores an application-instance GUID, COM+ recycles the process, and the later recycle request targets the retired instance identifier.

Developer and operations guidance

Log method, variant type, stable IDs, server/partition, collection timestamp, resolution result, and recent lifecycle event. Avoid logging only the display name because names can be ambiguous.

Official Microsoft references for COMADMIN_E_OBJECT_DOES_NOT_EXIST

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