-
Título
Migration job hangs and DSA log contains the message "Configurator Statistics: Counting ADAM statistics -
Descrição
In the Progress display the migration job completes the Initializing step and then as soon as it starts the Migration step the job appears to hang. The DSA reports the following:
5/18/2010 3:28:53 PM (GMT-05:00) Target JobID:2 -> Finishing Partial Sync handler
5/18/2010 3:28:53 PM (GMT-05:00) Target JobID:2 -> Handler PartialSync finished with 10 objects. Time = 0.000930 sec.
5/18/2010 3:28:53 PM (GMT-05:00) Target JobID:2 -> Handler Security started with 10 objects
5/18/2010 3:28:53 PM (GMT-05:00) Target JobID:2 -> Security handler started with 10 objects
5/18/2010 3:28:53 PM (GMT-05:00) Target JobID:2 -> Saving old SecurityDescriptor attributes
5/18/2010 3:29:46 PM (GMT-05:00) Configurator Statistics: Counting ADAM statistics for job: F2B8D23685739B498203A323ED99A10A.
5/18/2010 3:29:46 PM (GMT-05:00) Configurator Statistics: ADAM statistics counted for job: F2B8D23685739B498203A323ED99A10A, time: 0.000816026.
The last two lines from the log above repeat every two minutes. The following solutions do not help to fix the problem.
SOL36209 - Directory Synchronization Agent (DSA) Stops, "Counting ADAM statistics for job" written repeatedly to DSA.log - https://support.quest.com/Search/SolutionDetail.aspx?id=SOL36209
SOL46153 - INTERNAL: DSA Controller Service Stops and the following appears in the DSA log file: Configurator Statistics: ADAM Configurator Statistics: Counting ADAM statistics for job - https://support.quest.com/Search/SolutionDetail.aspx?id=SOL46153 -
Causa
The DSA log indicates that the DSA was trying to save the Security Descriptor attribute just before it failed.
5/18/2010 3:28:53 PM (GMT-05:00) Target JobID:2 -> Saving old SecurityDescriptor attributes -
Resolução
The Migration job had the "Security Description migration rule:" set to merge. The rule was set to skip and the migration completed.
The "Security Description migration rule:" in the Synchronization job was set to merge.Note: it was observed that the issue may be caused by downloaded but not applied Windows Updates on DSA machine. Applying Windows Updates and reboot may resolve the issue.
-
Informações adicionais
Extended logging for the DSA may need to be enabled to get the details in the log as noted above. Please see the following solution for details.
SOL11485 - How to enable extended verbose logging of QMM Directory Synchronization Agent services. - https://support.quest.com/Search/SolutionDetail.aspx?id=SOL11485