Hi, I'm sorry, today I saw that the member dataset was in FORCE state. So I changed it to keep est voilà... Thank you both so much for your help! I hope one last question :-) In debug modus I see "DEBUG - Unsupported scripting engine: Oracle Nashorn"
Have I to worry about that? Best regards, Michael -----Ursprüngliche Nachricht----- Von: lsc-users <[email protected]> Im Auftrag von Clément OUDOT Gesendet: Donnerstag, 23. Mai 2019 20:42 An: [email protected] Betreff: Re: [lsc-users] Need help with the filters Le 23/05/2019 à 20:28, Pilling, Michael a écrit : > Yes, but still no better results.... The error you get is: LDAP: error code 68 - 00000562: UpdErr: DSID-031A11E2, problem 6005 (ENTRY_EXISTS), data 0 This error should only occurs when adding entry, but AD seems also to return this when adding a member to an entry. This can mean the member value already exists and can't be added a second time. That is the risk when using the MERGE policy. Soisik is right, you should do the merge inside the dataset and use the FORCE policy. Maybe what is missing in the js code is a test to avoid adding a value that already exists. -- Clément Oudot | Identity Solutions Manager [email protected] Worteks | https://www.worteks.com _______________________________________________________________ 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 _______________________________________________________________ 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
