You may encounter an Internal DSA Error in the dsa.log that occurs when the DSA is searching for conflicts:
22/05/2010 11:14:35 PM (GMT+10:00) COM AcAdSwitches Starting conflict searching
22/05/2010 11:14:35 PM (GMT+10:00) Common AcAdSwitches Error 0xe1000005. Internal DSA error
22/05/2010 11:14:35 PM (GMT+10:00) Activation AcAdSwitches Mail Switch, "Apply" method done
22/05/2010 11:14:35 PM (GMT+10:00) Activation AcAdTaskHandler Task Handler, switch "MailSwitch" returned error -520093691
This may be caused by an object with an invalid proxyaddress. One example would be an "empty" X500 address. This entry would appear in ADSIedit like the following:
x500:
Normally an x500 address should have something after the colon:
X500:/o=orgname/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=John.Smith
To resolve this issue, find the object in the source (one way sync) or source or target (two way sync) Exchange Org that has an invalid proxyaddress and remove it.
You can export a list of objects with invalid proxyaddresses using the LDIFDE command. The example below will return objects with a few known types of invalid addresses, but may not find all of them.
ldifde -s SERVERNAME -r "(|(proxyaddresses=*@)(proxyaddresses=*:)(proxyaddresses=*.))" -f output.txt
Replace SERVERNAME with the nearest domain controller. This will output a list of users to "output.txt" - examine this list and remove the invalid proxyaddresses from these users and attempt the synchronization again.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center