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

COMADMIN_E_CAN_NOT_START_APP is the failure HRESULT 0x8011044B (signed decimal -2146368437, unsigned decimal 2148598859). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x044B.

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.

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

Where COMADMIN_E_CAN_NOT_START_APP 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 COMADMIN_E_CAN_NOT_START_APP, 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 COMADMIN_E_CAN_NOT_START_APP; without it the symbolic HRESULT is underdetermined.
  • The COMADMIN_E_CAN_NOT_START_APP investigation needs StartApplication caller and exact target selector so the exact failing boundary remains reconstructable.
  • For COMADMIN_E_CAN_NOT_START_APP, preserve recent deployment and disablement events; it anchors the failure to the real administration object.
  • Evidence for COMADMIN_E_CAN_NOT_START_APP should include COM+ application process and System Application logs, captured before a repair changes state.

Diagnostic sequence for COMADMIN_E_CAN_NOT_START_APP

  • The next COMADMIN_E_CAN_NOT_START_APP diagnostic action is to resolve the application by AppID.
  • To isolate COMADMIN_E_CAN_NOT_START_APP, verify it is an enabled server application.
  • For COMADMIN_E_CAN_NOT_START_APP, confirm at least one valid component is installed.
  • At the COMADMIN_E_CAN_NOT_START_APP boundary, correct deployment/configuration before starting.
  • The next COMADMIN_E_CAN_NOT_START_APP 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 for COMADMIN_E_CAN_NOT_START_APP

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