You may experience a problem where the DSA stops and never completes. Once the DSA stops processing, the only information written to the DSA.log file is the following, approximately every two minutes:
(GMT-05:00) Configurator Statistics: Counting ADAM statistics for job: 404DF011EAAADA4997B73EF98E97B5E6.
(GMT-05:00) Configurator Statistics: ADAM statistics counted for job: 404DF011EAAADA4997B73EF98E97B5E6, time: 0.34884.
The DSA may always stop when processing certain object(s). When these object(s) are excluded from the sync, the problem is resolved. Also, the "Quest Directory Synchronization Agent Controller Service" where the DSA is installed may stop when this happens.
What is causing this?
This issue is encountered when the Directory Sync Agent attempts to process an Active Directory attribute that contains a DN with Binary Property Type: ENSURE YOU SKIP THESE ATTRIBUTES IN BOTH DIRECTIONS IN CASE OF TWO WAY SYNCHRONIZATION
Currently, the following three attributes have been seen most commonly to contain this property type:
To work around the issue, configure the Directory Sync Agent to skip the three attributes mentioned for each of the available object classes.
More information on how to skip attributes can be found in the Migration Manager for AD User Guide.