What does HRESULT 0x80110451 (COMADMIN_E_START_APP_DISABLED) mean?

 
Previous Next
COMADMIN_E_BASE_PARTITION_ONLY COMADMIN_E_CAT_DUPLICATE_PARTITION_NAME

COMADMIN_E_START_APP_DISABLED

COMADMIN_E_START_APP_DISABLED is the failure HRESULT 0x80110451 (signed decimal -2146368431, unsigned decimal 2148598865). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0451.

Exact meaning

AllStat records this condition as “You cannot start an application that has been disabled.” The selected COM+ application exists, but its catalog configuration prohibits an administrative start. ICOMAdminCatalog::StartApplication therefore stops before creating or resuming the server process.

This result describes an explicit configuration gate. It is not a timeout, process crash, missing component, authentication failure, or proof that COM+ activation infrastructure is unhealthy. An operator or deployment system may have disabled the application deliberately.

Why disabled state matters

COM+ application objects are stored in the Applications collection and expose configurable properties. A disabled application can represent maintenance, incident containment, staged deployment, retirement, or an incomplete configuration. Starting it automatically would bypass that administrative decision, so recovery requires understanding why the flag was set rather than merely looping StartApplication.

Resolve the target by AppID whenever possible. Names can be duplicated across partitions or selected incorrectly by automation, and enabling the wrong application is more dangerous than leaving the intended target stopped.

Evidence to collect

  • The application AppID, partition identifier, display name, application type, and current Enabled value read from a freshly populated Applications collection.
  • The exact target argument passed to StartApplication and the machine on which the COMAdmin catalog session is operating.
  • Catalog change history, deployment logs, incident records, and maintenance automation that may explain who disabled the application and for what reason.
  • The result of the last property save, including ErrorInfo entries if a previous enable/disable change partially failed.
  • Service-account and administrator identities involved in the change, while redacting passwords or other secrets.
  • The component count and server/library application type as supporting context, but only after confirming that disabled state is the immediate blocker.

Common operational branches

  • Incident response disabled the application to stop faulty or unsafe activations, and restart automation later treated every stopped application as eligible for recovery.
  • A deployment workflow creates or imports the application in a disabled state, expecting a later approval step that never occurred.
  • A rollback restores catalog configuration from a snapshot where the application was intentionally disabled.
  • The script resolves an application by an ambiguous or stale name and reaches another catalog object whose Enabled property is false.
  • A property update was made in memory but SaveChanges was not called, so the persistent catalog still contains the disabled value.
  • Remote administration is connected to a different computer or partition than the operator expects; the similarly named local application may be enabled while the actual target is not.

Diagnostic sequence

  • Connect to the intended COM+ catalog server and retrieve the Applications collection.
  • Locate the object by AppID and partition, then repopulate the collection before reading Enabled; do not rely on a cached object retained across another administration session.
  • Confirm that the disabled state is authorized to change. Review maintenance windows, incident tickets, deployment gates, and ownership before enabling production code.
  • When enablement is approved, set the property through the catalog object and call SaveChanges. Inspect collection ErrorInfo if the save reports object-level failures.
  • Re-read the persisted object to prove that Enabled is now true on the correct machine and partition.
  • Call StartApplication once. If a different HRESULT follows, diagnose that new stage separately rather than continuing to treat the application as disabled.

Practical scenario

During an incident, operations disables a COM+ order-processing application to prevent new activations. A generic health script later sees no running process and calls StartApplication, receiving COMADMIN_E_START_APP_DISABLED. The safe response is to preserve the containment decision and escalate for approval; changing retry intervals cannot make the start valid.

Retry and recovery policy

Repeated start attempts are deterministic while the catalog property remains false. Retry only after an authorized configuration change has been saved and verified. Do not make “enable on failure” the default behavior: that can reverse a security, maintenance, or incident-control action without context.

If enablement succeeds but starting still fails, retain both events. The first confirms a catalog-state transition; the subsequent HRESULT identifies the next independent boundary, such as application type, missing components, service availability, or activation.

Distinguishing nearby COMADMIN results

  • COMADMIN_E_START_APP_NEEDS_COMPONENTS means the application lacks executable component entries; it is not simply disabled.
  • COMADMIN_E_CAN_NOT_START_APP applies when the selected application type cannot be started through this operation.
  • COMADMIN_E_CAN_NOT_START_APP and activation failures should be investigated only after the enablement gate has been cleared.
  • CO_E_CLASS_DISABLED can be observed by a client attempting component activation; this COMADMIN result is specifically from the administrative application-start operation.

Telemetry and change control

Record AppID, partition, server name, old and new Enabled values, COMAdmin caller, change-request identifier, catalog save result, and the later start result. A high-quality alert should say that policy blocked the start and link to the disabling event; labeling it merely “COM+ failed to launch” loses the central diagnostic fact.

Official Microsoft references

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