-
Title
DSA error: Common AcAdTaskHandler LDAP error 0x20. No Such Object (0000208D: NameErr: DSID-031001 -
Description
All migration sessions do not complete, there is no timing out, just nothing happens.
Log contains entries like:
09/17/07 16:55:41 (GMT-07:00) Common AcAdTaskHandler LDAP error 0x20. No Such Object (0000208D: NameErr: DSID-031001AD, problem 2001 (NO_OBJECT), data 0, best match of:
09/17/07 16:55:41 (GMT-07:00) Common AcService Error 0x80070002. The system cannot find the file specified.
and later
09/17/07 16:55:41 (GMT-07:00) Configurator SCA: Quering service status (QueryServiceStatus, service: AeDSACtrl_SAI584820).
09/17/07 16:55:41 (GMT-07:00) Configurator SCA: Query service status result: type 'Win32 own process', current state: 'Running', controls accepted: 'stop, pause and continue, shutdown', win32 exit code: '0', service specific exit code: '0', check point: '0', wait hint: '0' (QueryServiceStatus, service: AeDSACtrl_SAI584820).
09/17/07 16:55:41 (GMT-07:00) Configurator SCA: No progress during wait hint. Progress time: '200', current wait hint: '0'.
this is where DSA times out and "hangs". -
Cause
One of the files used by DSA got corrupted.
-
Resolution
Re-installing DSA on the same computer might not help but installing a new DSA on another computer has proven to resolve the problem.
For instructions how to install a new DSA please see SOL35842:
https://support.quest.com/SUPPORT/index?page=solution&id=SOL35842
If new DSA works fine then this new DSA could be used in future or the old one could be re-installed to resolve the problem.
In some situations (when re-installing DSA is not desired or does not help) this approach can be used:
1. Delete all existing (and failed) migration sessions. Before doing this please read the following Quest KB articles - SOL45104 and SOL45091:
https://support.quest.com/SUPPORT/index?page=solution&id=SOL45104
https://support.quest.com/SUPPORT/index?page=solution&id=SOL45091
If you have directory synchronization configured and working then deleting migration sessions is not a concern.
2. Restart the migration server.
3. Launch Migration Manager and confirm directory synchronization is stopped.
4. Close Migration Manager.
5. Rename the three .xml files (jobs.xml, activation.xml, resolver.xml) on the DSA machine, files can be found under %Program Files%\Quest Software\Migration Manager\DSA\CONFIGS\
6. Launch Migration Manager, create a new migration session and migration should work now, error should disappear.
Note: this procedure will require a full resynchronization.