-
Titre
Target JobID:0 - throwing out a pair (trg AdsPath = LDAP://server.company.com/CN=Test User ,OU -
Description
Target JobID:0 -> throwing out a pair (trg AdsPath = LDAP://server.company.com/CN=Test User ,OU=Users ,DC=company, DC=com) according to the LEAVE rule is written to the DSA log during a migration session and the AD object is not migrated.
Common JobID:0 -> Skipping already exist error. is also written to the log with reference to the AD object in the migration session.
-
Cause
An object exists in the target domain which matches the source object being migrated. The migration session was executed with "Never merge: skip accounts that match any accounts on target".
Alternatively, the issue could be caused by source object being already stamped with migration-related attributes
-
Résolution
Verify the target AD object should be matched to the source AD object, and does not belong to a different user.
Configure a new Migration Session. In Select Target Container, select "Merge and move the objects to the new OU" or "Merge and leave the account where it was before the migration" in the "When merging with existing accounts on the target" section.
Also, please check in domain pair, object matching, service attributes, <select appropriate class for source domain>, what attributes are used for stamping. Then validate if source object's attributes are already populated. It may be needed to wipe those attributes on the source.
Issue like this could be caused when there are remains of the old migration project to domain, that became the source and migrated objects are still carrying stamping from the old project.