What does HRESULT 0x8011044A (COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY) mean?

 
Previous Next
COMADMIN_E_REQUIRES_DIFFERENT_PLATFORM COMADMIN_E_CAN_NOT_START_APP

COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY

COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY is the failure HRESULT 0x8011044A (signed decimal -2146368438, unsigned decimal 2148598858). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x044A.

Exporting COM+ applications and proxies: exact meaning of COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY

The selected COM+ application proxy cannot itself be exported. ExportApplication classifies the target as an application proxy rather than a server application suitable for proxy generation or package export.

AllStat records this condition as “Application Proxy is not exportable”.

Evidence to collect before repair

  • The COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY investigation needs application ID and type so the exact failing boundary remains reconstructable.
  • For COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY, preserve component install-versus-import provenance; it anchors the failure to the real administration object.
  • Evidence for COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY should include interface/type-library/proxy-stub metadata, captured before a repair changes state.
  • Collect export options, destination path, and ErrorInfo when diagnosing COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY; without it the symbolic HRESULT is underdetermined.

Where COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY occurs

COM+ export behavior depends on application type and complete installation metadata; system applications, proxies, and imported components have deliberate export limitations. In the specific case of COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY, record application type, source machine role, original server application, and requested export options.

Diagnostic sequence for COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY

  • To isolate COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY, resolve the server application on its owning machine.
  • For COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY, verify components were installed with complete metadata.
  • At the COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY boundary, select package versus proxy export intentionally.
  • The next COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY diagnostic action is to use a writable clean destination.
  • To isolate COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY, inspect the produced package and test on a controlled target.

Retry and recovery

Export the server application on its owning server or retain the existing proxy package; do not chain proxy exports.

Practical administration scenario

An administrator connects to a client machine and attempts to export the installed proxy as though it were the server application.

Difference from nearby COMADMIN results

COMADMIN_E_CAN_NOT_EXPORT_SYS_APP blocks the System Application, whereas this code blocks an application proxy.

Official Microsoft references for COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY

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