What does HRESULT 0x8011044B (COMADMIN_E_CAN_NOT_START_APP) mean?

 
Previous Next
COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY COMADMIN_E_CAN_NOT_EXPORT_SYS_APP

COMADMIN_E_CAN_NOT_START_APP

Starting and controlling a COM+ application: exact meaning of COMADMIN_E_CAN_NOT_START_APP

The selected application type cannot be started as a COM+ server process. StartApplication detects a library application or application proxy, neither of which owns a standalone server process.

Windows describes this condition as “Failed to start application because it is either a library application or an application proxy”.

Where the result occurs

Administrative start/stop operations apply only to appropriate server applications with valid enabled components; they do not create executable contents or change application type. In the specific case of this result, record Activation property/application type and verify the script resolved the intended server application.

Evidence to collect before repair

  • Collect AppID, application type, Enabled property, and component count when diagnosing this result; without it the symbolic HRESULT is underdetermined.
  • Record StartApplication caller and exact target selector.
  • Preserve recent deployment and disablement events; it anchors the failure to the real administration object.
  • Evidence should include COM+ application process and System Application logs, captured before a repair changes state.

Diagnostic sequence

  • The next diagnostic action is to resolve the application by AppID.
  • To isolate it, verify it is an enabled server application.
  • Confirm at least one valid component is installed.
  • correct deployment/configuration before starting.
  • The next diagnostic action is to start once and validate activation rather than looping retries.

Practical administration scenario

Automation selects a library application by name and calls StartApplication, producing this type-specific rejection.

Retry and recovery

Start only server applications; activate library components through their client and use proxies to reach the remote server.

Difference from nearby COMADMIN results

COMADMIN_E_START_APP_NEEDS_COMPONENTS applies to an otherwise startable application that is empty.

Official Microsoft references


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