Category:Active Directory
Last Updated:2011-08-03
The way the Discovery works, it gathers a list of all the DN's in the source directory; following that, 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 intial query and the attribute query. Normally this is a one off (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. Recommend you use the DC that is the Global Catalog. For this, you may need to obtain a temp key.dat.
If you already have a permanent key.txt, rename it i.e. \Simplesync-v5\global\key-permanent.txt
Copy in the temporary key.txt i.e. \UnitySync-v1.xx\Global\key.txt
(Or copy to Help About and click Save Key.)
On the source tab of your connection, enter the IP of the alternate DC/GC from the source forest. Click Apply.
On the General tab, enable Discovery only (maybe Sim, but not Sync). Leave sync disabled until you are satisfied with the results of your Discovery/sim.
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 sync again.
If problems persist, contact Support@dirwiz.com and forward the latest Discovery logs.