DSA.log shows "Error 0xa910007d. SID has conflict on target . Will not be added to sIDHistory (4328942)

DSA.log shows "Error 0xa910007d. SID has conflict on target . Will not be added to sIDHistory

DSA.log shows an error similar to:

The SID value is already present in SID history of another target user. For example, the user has been already migrated to the target domain under a different name or mismatched to a different account.

1. Run a query against the target domain to find the conflicting object that is preventing the sIDHistory from being applied. For example:

LDIFDE can be used to find an object based on the sIDHistory attribute. For example to locate the account having sIDHistory 01050000000000051500000076D1202E73994FC728E43A7310050000 run the following command. The "\" character in the LDAP filter denotes each pair of characters as a HEX value. ldifde -f C:\temp\Output.txt -r "(SIDHistory=\01\05\00\00\00\00\00\05\15\00\00\00\76\D1\20\2E\73\99\4F\C7\28\E4\3A\73\10\05\00\00)" sAMAccountName sIDHistory LDIFDE will be able to find the correct account but when outputting the sIDHistory it will write it as a Base64 string. e.g.: dn: CN=nmove002,OU=z_Migrate,DC=target,DC=com sIDHistory:: AQUAAAAAAAUVAAAAdtEgLnOZT8co5DpzEAUAAA== To verify the SID in the output use dsquery instead e.g: dsquery * -Filter "(SIDHistory=\01\05\00\00\00\00\00\05\15\00\00\00\76\D1\20\2E\73\99\4F\C7\28\E4\3A\73\10\05\00\00)" -Attr sAMAccountName sIDHistory sAMAccountName sidHistory nmove002 S-1-5-21-773902710-3343882611-1933239336-1296