What does HRESULT 0x8011042D (COMADMIN_E_COMP_MOVE_LOCKED) mean?

 
Previous Next
COMADMIN_E_SESSION COMADMIN_E_COMP_MOVE_BAD_DEST

COMADMIN_E_COMP_MOVE_LOCKED

COMADMIN_E_COMP_MOVE_LOCKED is the failure HRESULT 0x8011042D (signed decimal -2146368467, unsigned decimal 2148598829). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x042D.

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

COM+ refuses a component move because the source or destination application is protected or locked. MoveComponent evaluates both application endpoints before changing ownership of the component catalog entry.

AllStat records this condition as “The component move was disallowed, because the source or destination application is either a system application or currently locked against changes”.

Where COMADMIN_E_COMP_MOVE_LOCKED 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_LOCKED, record source and destination AppIDs, system-application status, active deployment locks, and concurrent administration activity.

Evidence to collect before repair

  • Evidence for COMADMIN_E_COMP_MOVE_LOCKED 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_LOCKED; without it the symbolic HRESULT is underdetermined.
  • The COMADMIN_E_COMP_MOVE_LOCKED investigation needs catalog lock/concurrent deployment timeline so the exact failing boundary remains reconstructable.
  • For COMADMIN_E_COMP_MOVE_LOCKED, preserve fresh Applications and Components collection snapshots; it anchors the failure to the real administration object.

Diagnostic sequence for COMADMIN_E_COMP_MOVE_LOCKED

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

Difference from nearby COMADMIN results

COMADMIN_E_COMP_MOVE_BAD_DEST means the destination disappeared; this value means an existing endpoint is not eligible for modification.

Retry and recovery

Choose ordinary unlocked applications and retry only after the catalog lock or protected target condition is removed.

Practical administration scenario

An administrator tries to move a component into the System Application and COM+ blocks the operation.

Official Microsoft references for COMADMIN_E_COMP_MOVE_LOCKED

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