Troubleshooting LDAPSync issues are often much easier at the command line where you can do an immediate invocation of the job without having to continually refresh DA and wait for the job to be executed.
On the 6.7 SP1 server I’ve seen “already initialized” errors when invoking LDAPSync so the order of the classpath jars is important:
cd %DM_HOME%\bin java -classpath c:\documentum\config;c:\progra~1\documentum\dctm.jar;%DM_HOME%\lib\jss42.jar;%DM_HOME%\lib\dmldap.jar;%DM_HOME%\lib\server-impl.jar com.documentum.ldap.LDAPSync -docbase_name-user_name -full_sync true -method_trace_level 10
I haven’t seen the same issues on the CS 7.1 server so you can stick with the basic syntax of the command
cd %DM_HOME%\bin java com.documentum.ldap.LDAPSync -docbase_name-user_name -password -full_sync true -method_trace_level 10