Error in DSA log when running DSA job using "Merge objects with corresponding contacts" option (4299869)

The following error is found in DSA.LOG file:

01/30/07 15:05:38 (GMT-04:00) COM AcAdSwitches Updating object: <GUID=228A2AB87E2AA34C9DC9362FCAEF6BFA>
01/30/07 15:05:38 (GMT-04:00) COM AcAdSwitches Deleting object: <GUID=91A79A991BF979469D162604255F7A12>
01/30/07 15:05:38 (GMT-04:00) COM AcAdSwitches Error 0xea0000a6. Cannot delete conflicted contact "<GUID=91A79A991BF979469D162604255F7A12>"
LDAP error 0xa. Referral (0000202B: RefErr: DSID-031006E0, data 0, 1 access points
ref 1: 'gc._msdcs.ROOT.LOCAL:3268').

This behaviour is by design.

1. Please verify if contacts are residing in the target domain. Depending on the target forest design, it is possible that contacts reside in a domain other than the target. For example it a child or root domain. In this case DSA will still determine the SMTP address conflict by querying the GCs and will attempt to delete the corresponding contact. However the GC queried will return the referral to the DC in the different domain and DSA will log the error.
 

2. Verify if the contacts are members of a group in a different domain. This may have caused the LDAP referral. Removing the target contact membership from these groups should allow the DSA merge to succeed.

3. In some very rare circumstances this behavior was caused by the conflict found on the source side. Error similar to the following is recorder in DSA log:

10/20/2008 10:24:42 AM (GMT-05:00) COM AcAdSwitches Conflict(s) on source found
10/20/2008 10:24:42 AM (GMT-05:00) COM AcAdSwitches Found conflict(s) on attribute proxyAddresses
10/20/2008 10:24:42 AM (GMT-05:00) COM AcAdSwitches Conflicted value: smtp:User@domain.com
10/20/2008 10:24:42 AM (GMT-05:00) COM AcAdSwitches Conflicted contact object: CN=User,OU=OUName,DC=domain,DC=local

It is against Microsoft AD design to have multiple objects with the same proxyAddresses attribute values. Please resolve such conflicts prior to starting migration.

As a workaround to the scenario outlined in #1, the contacts could be migrated via an INTRA- Forest migration to the destination domain, then merged properly with the orignal sync or migration session. During this action the "reconnect mailbox" option should be enabled, because without the option checked all exchange attributes will be left in original objects. new contacts are mail-disabled. so when DSA starts to create the mailboxes it will search in the Global Catalog for conflicts and find original contacts in 3rd domain.

STATUS:
Enhancement request CR0206345 has been submitted to Development for consideration in a future release of Migration Manager for AD.