On 31/01/2018 09:48, Vincent LEPETIT wrote:
I had some same error with some user account.For example : anv. 31 09:17:44 - ERROR - Error while looking for (&(objectClass=user)(sAMAccountName=amuller)) in ou=Etudiants,dc=PSL,dc=local: javax.naming.CommunicationException: Request: 3 cancelled; remaining name 'ou=Etudiants' janv. 31 09:17:44 - ERROR - Error while synchronizing ID {uid=amuller}: org.lsc.exception.LscServiceException: javax.naming.CommunicationException: Request: 3 cancelled; remaining name 'ou=Etudiants' This user is in source ldap but not in destination ad. My destination basdn focus on this ou=Etudiants and i don’t have this error message for lot of other users account in this ou. How can i explain this ?
Hi, We see that LSC gets an error when requesting information for these records from your AD. Depending on how you have configured LSC, it will try and figure out what action is needed (adding the record, updating its attributes ...). Could you share your LSC configuration? -- Soisik _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
