| Previous | Next |
| ERROR_DS_PDC_OPERATION_IN_PROGRESS | ERROR_DS_ILLEGAL_XDOM_MOVE_OPERATION |
ERROR_DS_CROSS_DOMAIN_CLEANUP_REQD
The move stopped after creating inconsistent object state
A coordinated cross-domain move has several stages: validate the source, create or update the destination representation, transfer security-principal state, and remove the old source object. If the sequence fails after destination creation, both domains can retain versions of the principal. The error therefore calls for reconciliation, not an immediate blind retry.
Locate both copies by GUID, SID, account name, and distinguished name. Establish which object should remain authoritative, then follow a documented cleanup or rollback procedure while preserving audit evidence and access-control continuity. Check memberships, SPNs, UPN, password state, and SID history before deleting anything. Replication should be healthy first; deleting one copy on a stale controller can allow the unwanted version to reappear or leave references pointing to the wrong principal.
What to inspect
- Inventory source and target objects and their security identifiers.
- Compare memberships and unique account attributes before cleanup.
- Verify replication convergence after removing the unwanted copy.
References
- MS-ADTS: cross-domain move stages
- MS-ADTS: move validation and cleanup constraints
- Microsoft: restoring security principals and memberships
Looking for a different code? Search another status or error code.