The following error occurs when migrating users:
"Error 0xe3000005. Target object matched by the following high-priority matching rule: AdminDisplayName=F1F165A5C403C543B246F44D9953D6D6 has already been matched with another source object by the following low-priority matching rule: objectClass=top#person#organizationalPerson#user "
The same object participated in another job. For example, the user was synchronized or migrated from a different Source Domain, when there is more than one Domain involved in the migration and/or synchronization.
Possibility the source object has being deleted and the object recreated again in the source. The newly created object will have different ObjectGUID.
Possibility the new source object is created using copy object where the existing object had been participating in the migration and/or synchronization.
If custom XML file is in use to extend the schema.
RESOLUTION 1 For CAUSE 1:
Migration Manager uses Service Attributes to store matching information. When two objects are matched, the Global Unique Identifier (GUID) of the corresponding object is written to the Service Attribute selected to store information about matching. If the attribute has been already used for one Source Domain Migration, the same attribute can not be used for a Migration from the second Domain. The matching attribute can always be the same in Source Domains (no matter how many participate in synchronization/migration, as long as the synchronization job is one-way synchronization), but on the Target side the matching attribute should be different.
For example, if using extension attributes 14 and 15, they can be the same in Source Domain 1, Source Domain 2, Source Domain 3, etc. However, on the target side we can use extension attributes 14 and 15, only for the First Domain pair. For the pair "Source Domain 2 - Target Domain", different attributes will be needed on the Target side, for example, extension attributes 9 and 10. For the next pair "Source Domain 3 - Target Domain", yet another set of different attributes will need to be on the Target side, for example, extension attributes 7 and 8.
This can be configured by:
1. Right-clicking a Domain Pair.
2. Selecting Properties | "Object Matching".
3. Clicking "Service Attributes".
RESOLUTION 2 for CAUSE 1:
A non-standard Service Attribute is used that already contains a value in the field. To resolve the issue, clear the value from the field.
NOTE: Changing the Service Attributes requires a Full Directory Resync.
The attributes selected by default to store the matching information for different object classes are listed in Migration Manager for Active Directory User Guide.
As the documentation states, if performing an Exchange migration, you should not use admindisplayname. Instead you should use the extended attributes. If there is no Exchange in the forest, then by default the adminDescription attribute is used to store auxiliary information for all object classes and adminDisplayName attribute is used to store matching information for all object classes.
RESOLUTION for CAUSE 2:
Clean the service attribute mention in the target objects and lets the DSA re-stamp with the correct value.
RESOLUTION for CAUSE 4:
Make sure the custom XML file use in the console is the same in the DSA server.