What does HRESULT 0x8011080A (COMADMIN_E_APP_NOT_RUNNING) mean?

 
Previous Next
COMADMIN_E_OBJECT_DOES_NOT_EXIST COMADMIN_E_INVALID_PARTITION

COMADMIN_E_APP_NOT_RUNNING

COMADMIN_E_APP_NOT_RUNNING is the failure HRESULT 0x8011080A (signed decimal -2146367478, unsigned decimal 2148599818). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x080A.

Runtime state of a COM+ server application: exact meaning of COMADMIN_E_APP_NOT_RUNNING

The application is present in the catalog but no current running application instance satisfies the requested operation. This differs from a missing catalog object and from a process that is already paused or recycled.

AllStat records the Windows SDK description as “The specified application is not currently running”.

Where COMADMIN_E_APP_NOT_RUNNING occurs

The result arises in runtime-control work such as pause, recycle, dump, or instance queries after COM+ resolves the application definition. Library applications also require special care because they do not own a separate server process.

Evidence to collect before changing the catalog

  • application type, AppID, activation setting, and current Components collection.
  • live application-instance IDs and PIDs from COM+ tracking.
  • service/application events showing start, stop, crash, recycle, or disabled state.
  • the lifecycle API, requested target, and timing relative to deployment or configuration changes.

Typical cause branches

  • the server application stopped normally or failed before the control request.
  • the request arrived between shutdown/recycle and creation of the replacement instance.
  • the target is a library application with no independently running Dllhost process.
  • automation resolved the correct application definition but an obsolete instance or PID.

Diagnostic sequence for COMADMIN_E_APP_NOT_RUNNING

  • verify that the catalog application is a server application capable of running independently.
  • query current instances rather than trusting a previously stored PID.
  • start the application only when its configured startup contract permits it.
  • wait for recycle completion when a replacement process is expected.
  • repeat the original control operation against the newly resolved instance.

Practical administration scenario

An operator requests a process dump just after a scheduled recycle has retired the old Dllhost and before the replacement receives its first activation.

Retry and recovery

Retry can be appropriate after the application starts or a recycle transition completes. Do not blindly start an intentionally stopped or disabled application merely to clear an administrative error.

Difference from nearby COMADMIN results

COMADMIN_E_OBJECT_DOES_NOT_EXIST means the target object or instance cannot be found; this code says the application definition exists but is not running. COMADMIN_E_START_APP_DISABLED concerns policy that prevents starting it.

What this HRESULT does not establish

The HRESULT does not prove a crash. Normal stop, idle shutdown, recycle, library activation, or disabled policy can all produce an absence of a running instance.

Developer and operations guidance

Capture AppID, application type, instance/PID resolution, requested lifecycle action, start/stop/recycle events, disabled state, and transition timestamps.

Official Microsoft references for COMADMIN_E_APP_NOT_RUNNING

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