Error DN Read (On Discovery)Created: 2012-04-20 08:09:59
Modified: 2017-06-04 20:27:18
Tags: Errors Troubleshooting UnitySync
Discovery works by gathering a list of all the DN’s in the Source directory first; then each individual DN is queried to obtain the attributes/values.
Error DN Read errors occur in rare cases when the DN was deleted or moved between the initial query and the attribute query. Normally this is a one-off issue of bad timing and doesn’t reoccur.
If this problem persists on every Discovery, UnitySync may be having trouble obtaining consistent information from your selected DC. In this case, it is advisable to run a test using an alternate DC in your Source forest. We recommend you use the DC that is the Global Catalog. For this, you may need to obtain a temporary key to test an additional IP. Request a temporary key from [firstname.lastname@example.org]9mailto:email@example.com).
Before entering your temporary key in the UnitySync UI, make sure to copy and save your permanent key to another location. Enter your temporary key and click Save.
On the General tab, click Copy to create a test connection.
On the Source tab of your new test connection, enter the IP of the alternate DC/GC from the source forest. Click Apply.
On the General tab, enable Discovery only (maybe Simulation, but not Synchronization right now). Leave Synchronization disabled until you are satisfied with the results of your Discovery/Simulation.
Run the connection to verify your results. If your Discovery from the DC/GC is still unsuccessful, change the source port to 3268 (GC) and try the Discovery/Sim again.
If problems persist, contact firstname.lastname@example.org and forward the latest Discovery logs.