What does HRESULT 0x8011042E (COMADMIN_E_COMP_MOVE_BAD_DEST) mean?

 
Previous Next
COMADMIN_E_COMP_MOVE_LOCKED COMADMIN_E_REGISTERTLB

COMADMIN_E_COMP_MOVE_BAD_DEST

COMADMIN_E_COMP_MOVE_BAD_DEST is the failure HRESULT 0x8011042E (signed decimal -2146368466, unsigned decimal 2148598830). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x042E.

Moving a component between COM+ applications: exact meaning of COMADMIN_E_COMP_MOVE_BAD_DEST

The destination application for a component move no longer exists. A move request holds a destination identity that becomes stale before COM+ commits the catalog change.

AllStat records this condition as “The component move failed because the destination application no longer exists”.

Where COMADMIN_E_COMP_MOVE_BAD_DEST occurs

A component move changes catalog ownership and service configuration; both source and destination applications must remain valid, mutable, and explicitly identified throughout the operation. In the specific case of COMADMIN_E_COMP_MOVE_BAD_DEST, repopulate Applications, verify the destination AppID, and correlate concurrent uninstall or deployment operations.

Evidence to collect before repair

  • Evidence for COMADMIN_E_COMP_MOVE_BAD_DEST should include component CLSID and current application ID, captured before a repair changes state.
  • Collect source and destination AppIDs and application types when diagnosing COMADMIN_E_COMP_MOVE_BAD_DEST; without it the symbolic HRESULT is underdetermined.
  • The COMADMIN_E_COMP_MOVE_BAD_DEST investigation needs catalog lock/concurrent deployment timeline so the exact failing boundary remains reconstructable.
  • For COMADMIN_E_COMP_MOVE_BAD_DEST, preserve fresh Applications and Components collection snapshots; it anchors the failure to the real administration object.

Diagnostic sequence for COMADMIN_E_COMP_MOVE_BAD_DEST

  • At the COMADMIN_E_COMP_MOVE_BAD_DEST boundary, repopulate both endpoints immediately before the move.
  • The next COMADMIN_E_COMP_MOVE_BAD_DEST diagnostic action is to reject system, proxy, or missing applications.
  • To isolate COMADMIN_E_COMP_MOVE_BAD_DEST, stop conflicting deployment rather than forcing catalog edits.
  • For COMADMIN_E_COMP_MOVE_BAD_DEST, perform the move through COMAdmin.
  • At the COMADMIN_E_COMP_MOVE_BAD_DEST boundary, verify interfaces, roles, and component properties in the destination.

Difference from nearby COMADMIN results

COMADMIN_E_KEYMISSING can describe any absent catalog key, while this value identifies the destination side of a component move.

Retry and recovery

Select a current destination application and restart the move; never redirect automatically by friendly name.

Practical administration scenario

A second administrator deletes the target application after a script resolves it but before the component move executes.

Official Microsoft references for COMADMIN_E_COMP_MOVE_BAD_DEST

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