Thanks Jonathan, I am using latest branch lsc-core-1.2-SNAPSHOT-dist.zip 12/07/2010 04:32 and same results. I still get the extra commas. I will file as a bug.
Is there perhaps any other way to correspond to the destination DN without using ldap.search? Jonathan Clarke <[email protected]> 07/10/2010 05:59 PM To [email protected] cc [email protected] Subject Re: [lsc-users] Errors Syncing between Domino and Active Directory (resent in plain text) Hi, On 09/07/10 23:11, [email protected] wrote: > I am trying to sync contact info between our Lotus Domino and AD ldap > directories. I am able to bind to and apparently read both directories. I > am using mail as a pivot attr. I want to sync and never delete or create > new objects. However, when attempting to use an ldap.search in the DST > directory (AD) to find the corresponding user, I am getting the following > errors due to what seems a space between CN and BaseDN: > > Jul 09 11:38:15 - INFO - Starting sync for MySyncTask > Jul 09 11:38:15 - INFO - Connecting to LDAP server ldap://<domino > domain>:38 > 9/ o=our company as cn=<domino-admin> > Jul 09 11:38:16 - INFO - Connecting to LDAP server > ldap://WINDOWS-DOMAIN-CONTROLLER1:389/dc=windowsdomain,dc=com as > CN=WindowsAdmin,OU=Blah,OU=Blah,DC=WindowsDomain,DC=com > Jul 09 11:38:16 - ERROR - Error while adding entry CN=John Doe,OU=Users,O > U=Country, in directory :javax.naming.InvalidNameException: Invalid name: > CN=John Doe,OU=Users,OU=Country,,dc=WindowsDomain,dc=com; remaining name ' > CN=John Doe,OU=Users,OU=Country,' > Jul 09 11:38:16 - ERROR - Error while synchronizing ID CN=John Doe,OU=Use > rs,OU=Country,: java.lang.Exception: Technical problem while applying > modifica > tions to directory > dn: CN=John Doe,OU=Users,OU=Country,,dc=WindowsDomain,dc=com <---Note > the null space between commas I see. The dn used is a result of the "lsc.tasks.MySyncTask.dn" setting, with the baseDn from "dst.java.naming.provider.url" appended. In your case, it looks like the "ldap.search" method may be returning an extra comma... This is quite possibly a bug which was recently fixed. Which version of LSC are you using? Assuming you're running 1.2.0, I suggest you try the latest 1.2-SNAPSHOT (soon to be released as 1.2.1), which contains a fix in the ldap.search method... See http://tools.lsc-project.org/files. > Also...to confirm, is it the ' -c ' switch that causes entries to be > deleted? For some reason I think I have nuked a few active directory > machine accounts while testing (I have tried using cn instead of mail), > whereas I thought condition.delete = false would have overridden... Yes the "-c" switch is for --clean, the operation which searches for all entries in the destination (dstService.filterAll), checks they exist in the source (srcService.filterId) and removes them from the destination if not. Using this switch can cause entries in the destination to be nuked for several reasons: - your filterId(s), filterAll(s) and pivotAttrs are set up wrong and entries aren't being matched correctly - you have entries in the destination that aren't in the source - they are removed (correctly) Using "condition.delete = false" should stop all deletions from happening. If you think this is not the case, please file a bug on http://tools.lsc-project.org/bugs ! Good luck, and let us know how it works out! Regards, Jonathan -- -------------------------------------------------------------- Jonathan Clarke - [email protected] -------------------------------------------------------------- Ldap Synchronization Connector (LSC) - http://lsc-project.org -------------------------------------------------------------- _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
