ERROR_DS_CROSS_DOMAIN_CLEANUP_REQD - 8491 (0x212B)
A cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state.
Updated: Feb 21, 2026
Technical Background
This error code, ERROR_DS_CROSS_DOMAIN_CLEANUP_REQD, is a specific technical issue encountered during directory service operations in the Windows operating system. It indicates that a cross-domain move operation has failed due to an inconsistency where two versions of the same object exist—one in the source domain and one in the destination domain.
Error Details
The error ERROR_DS_CROSS_DOMAIN_CLEANUP_REQD (8491, 0x212B) is triggered when a directory service operation attempts to move an object from one domain to another but encounters a situation where the object already exists in both domains. This inconsistency requires cleanup and resolution to restore system consistency.
Common Causes
- Invalid Parameter Values: The parameters provided for the cross-domain move operation were incorrect or inconsistent, leading to the failure.
- Incorrect Object Type: The operation attempted to move an object that is not supported by the directory service in a cross-domain context.
- Exceeding Limits: The system may have encountered limits on concurrent operations or resource constraints that prevented the successful completion of the move.
Real-World Context
This error typically occurs during domain management tasks, such as restructuring domains within an Active Directory forest. It is crucial to ensure that all necessary steps are taken to prevent such inconsistencies and maintain system integrity.
Is This Error Critical?
Yes, this error can lead to data inconsistency and operational issues if not addressed promptly. It is critical to resolve the issue by removing one of the duplicate objects to restore a consistent state in the directory service.
How to Diagnose
- Review Operation Context: Verify that the cross-domain move operation was initiated correctly and that all necessary permissions were granted.
- Validate Parameters: Ensure that the parameters passed to the operation are correct and complete, including object identifiers and domain names.
- Confirm Object Types: Check that the objects being moved are of a type supported by the directory service for cross-domain operations.
How to Resolve
- Correct Parameter Usage: Double-check all input parameters to ensure they are accurate and complete.
- Adjust Operation Context: If necessary, adjust the operation context or environment to avoid resource constraints or other issues that may have caused the failure.
- Restore Data: In some cases, restoring data from a backup might be required if the object has been modified in both domains.
Developer Notes
Developers should ensure robust error handling and validation mechanisms are in place when performing cross-domain operations to prevent such inconsistencies. Regularly updating and validating directory service configurations can also help mitigate this issue.
Related Errors
ERROR_DS_OBJECT_MOVE_FAILED(8490, 0x212A): Indicates a failure during the move operation.ERROR_DS_CROSS_DOMAIN_OBJ_INCOMPLETE(8503, 0x216B): Occurs when an object is moved but not fully replicated across domains.
FAQ
Q: What does the error ERROR_DS_CROSS_DOMAIN_CLEANUP_REQD indicate?
A: It indicates that a cross-domain move operation failed due to two versions of the same object existing in both source and destination domains, requiring cleanup.
Q: How can I prevent this error from occurring?
A: Ensure proper validation of parameters and object types before performing cross-domain operations. Regularly update and validate directory service configurations to maintain consistency.
Summary
The ERROR_DS_CROSS_DOMAIN_CLEANUP_REQD (8491, 0x212B) error is a specific issue encountered during cross-domain operations in Windows directory services. It highlights the need for careful parameter validation and proper handling of object types to maintain system consistency. Addressing this error promptly is crucial to prevent data inconsistencies and operational issues.