Hi Konrad, There's an issue with the context DN of the LDAP destination. Can you check that the ldap URL base dn is not null ? Le 24 mai 2013 08:37, "Eichstädt, Konrad" < [email protected]> a écrit :
> Hi Sebastian, **** > > ** ** > > after I changing the log level to DEBUG I got the following message: **** > > ** ** > > c:\Install\lsc-2.0.1>bin\lsc2.bat -f etc -s all**** > > Mai 24 08:35:42 - DEBUG - Loading XML configuration from: > c:\Install\lsc-2.0.1\etc\lsc.xml**** > > Mai 24 08:35:43 - INFO - Reflections took 172 ms to scan 1 urls, > producing 60 keys and 226 values**** > > Mai 24 08:35:43 - DEBUG - Importing XML schema file: > schemas/lsc-core-2.0.xsd**** > > Mai 24 08:35:43 - INFO - Logging configuration successfully loaded from > c:\Install\lsc-2.0.1\etc\logback.xml**** > > Mai 24 08:35:43 - INFO - LSC configuration successfully loaded from > c:\Install\lsc-2.0.1\etc\**** > > Mai 24 08:35:43 - INFO - Connecting to LDAP server ldap:// > ruegen.sbb.spk-berlin.de:389 as [email protected]**** > > Mai 24 08:35:43 - ERROR - org.lsc.exception.LscConfigurationException: > java.lang.reflect.InvocationTargetException**** > > Mai 24 08:35:43 - DEBUG - org.lsc.exception.LscConfigurationException: > java.lang.reflect.InvocationTargetException**** > > org.lsc.exception.LscConfigurationException: > java.lang.reflect.InvocationTargetException**** > > at org.lsc.Task.<init>(Task.java:124) ~[lsc-core-2.0.1.jar:na]**** > > at org.lsc.SimpleSynchronize.init(SimpleSynchronize.java:103) > ~[lsc-core-2.0.1.jar:na]**** > > at org.lsc.SimpleSynchronize.launch(SimpleSynchronize.java:145) > ~[lsc-core-2.0.1.jar:na]**** > > at org.lsc.Launcher.run(Launcher.java:224) [lsc-core-2.0.1.jar:na] > **** > > at org.lsc.Launcher.launch(Launcher.java:159) > [lsc-core-2.0.1.jar:na]**** > > at org.lsc.Launcher.main(Launcher.java:142) [lsc-core-2.0.1.jar:na] > **** > > Caused by: java.lang.reflect.InvocationTargetException: null**** > > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method)**** > > ~[na:1.7.0_21]**** > > at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown > Source)**** > > ~[na:1.7.0_21]**** > > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou**** > > rce) ~[na:1.7.0_21]**** > > at java.lang.reflect.Constructor.newInstance(Unknown Source) > ~[na:1.7.0_**** > > 21]**** > > at org.lsc.Task.<init>(Task.java:104) ~[lsc-core-2.0.1.jar:na]**** > > ... 5 common frames omitted**** > > Caused by: java.lang.NullPointerException: null**** > > at org.lsc.jndi.JndiServices.getContextDn(JndiServices.java:1036) > ~[lsc-**** > > core-2.0.1.jar:na]**** > > at > org.lsc.jndi.AbstractSimpleJndiService.<init>(AbstractSimpleJndiServi**** > > ce.java:176) ~[lsc-core-2.0.1.jar:na]**** > > at > org.lsc.jndi.SimpleJndiDstService.<init>(SimpleJndiDstService.java:97**** > > ) ~[lsc-core-2.0.1.jar:na]**** > > ... 10 common frames omitted**** > > "Please look up the log file > C:\Users\EICHST~1\AppData\Local\Temp\2\lsc.log to s**** > > ee the error"**** > > ** ** > > Do have any idea what the root cause is? **** > > ** ** > > Many Thanks, **** > > ** ** > > Best regards **** > > ** ** > > Konrad Eichstädt**** > > Staatsbibliothek zu Berlin**** > > Preußischer Kulturbesitz**** > > Potsdamer Str. 33 > 10785 Berlin**** > > Informations- und Datenmanagement**** > > IDM II elektronische Ressourcen**** > > Tel: +49 030 266 432222**** > > ** ** > > *Von:* [email protected] [mailto: > [email protected]] *Im Auftrag von *Eichstädt, > Konrad > *Gesendet:* Freitag, 24. Mai 2013 08:02 > *An:* Sébastien Bahloul > *Cc:* lsc-users > *Betreff:* Re: [lsc-users] LSC Error connecting AD**** > > ** ** > > Hi Sebastian, **** > > **** > > Unfortunately not the only message which the log file contains are: **** > > **** > > "24.05.2013 [lsc] Starting LSC" **** > > "24.05.2013 [lsc] LSC finished running"**** > > **** > > This message isn’t very helpful. Is there any possibility to get more > debug traces or something with a special option?**** > > **** > > Best regards **** > > **** > > Konrad**** > > **** > > Konrad Eichstädt**** > > Staatsbibliothek zu Berlin**** > > Preußischer Kulturbesitz**** > > Potsdamer Str. 33 > 10785 Berlin**** > > Informations- und Datenmanagement**** > > IDM II elektronische Ressourcen**** > > Tel: +49 030 266 432222**** > > **** > > *Von:* Sébastien Bahloul [mailto:[email protected]] > *Gesendet:* Donnerstag, 23. Mai 2013 16:59 > *An:* Eichstädt, Konrad > *Cc:* Clément OUDOT; lsc-users > *Betreff:* Re: AW: [lsc-users] LSC Error connecting AD**** > > **** > > Hi Konrad,**** > > **** > > Is there anything interesting inside the > C:\Users\EICHST~1\AppData\Local\Temp\3\lsc.log file (full stacktrace, > complementary error) ?**** > > **** > > Regards,**** > > > **** > > Sebastien BAHLOUL > IAM / Security specialist > Ldap Synchronization Connector : http://lsc-project.org > Blog : http://sbahloul.wordpress.com/**** > > **** > > 2013/5/23 Eichstädt, Konrad <[email protected]>**** > > Hello All, > > Many Thanks for your support. I believe that I moved with your help one > step forward. I assume that the connection problem is solved but now I'am > getting the following error: > > c:\Install\lsc-2.0.1>bin\lsc2.bat -f etc -s all -n > Mai 23 16:26:54 - DEBUG - Loading XML configuration from: > c:\Install\lsc-2.0.1\etc\lsc.xml > Mai 23 16:26:54 - INFO - Reflections took 188 ms to scan 1 urls, > producing 60 keys and 226 values > Mai 23 16:26:54 - DEBUG - Importing XML schema file: > schemas/lsc-core-2.0.xsd > Mai 23 16:26:55 - INFO - Logging configuration successfully loaded from > c:\Inst > all\lsc-2.0.1\etc\logback.xml > Mai 23 16:26:55 - INFO - LSC configuration successfully loaded from > c:\Install\ > lsc-2.0.1\etc\Mai 23 16:26:55 - INFO - Connecting to LDAP server ldap:// > ruegen.sbb.spk-berlin.de:389 as [email protected] > Mai 23 16:26:55 - ERROR - org.lsc.exception.LscConfigurationException: > java.lang.reflect.InvocationTargetException > "Please look up the log file > C:\Users\EICHST~1\AppData\Local\Temp\3\lsc.log to see the error" > > Enclosed you find my lsc.xml file. Have you any idea what the problem now > is? > > Many Thanks again,**** > > > Best regards > > Konrad > > > > Konrad Eichstädt > Staatsbibliothek zu Berlin > Preußischer Kulturbesitz > Potsdamer Str. 33 > 10785 Berlin > Informations- und Datenmanagement > IDM II elektronische Ressourcen > Tel: +49 030 266 432222 > > -----Ursprüngliche Nachricht----- > Von: Clément OUDOT [mailto:[email protected]]**** > > Gesendet: Donnerstag, 23. Mai 2013 08:59 > An: Sébastien Bahloul > Cc: Eichstädt, Konrad; lsc-users**** > > Betreff: Re: AW: [lsc-users] LSC Error connecting AD**** > > 2013/5/22 Sébastien Bahloul <[email protected]>: > > Hi Konrad, > > > > I'm sorry but Wireshark was my last piece of advice. Some checks to > > defeat this issue : > > - could you try to switch to a dummy password ? > > - could you confirm the JDK/JRE version ? > > - could you confirm that Wireshark is showing a password based > > authentication for both LSC and LDAP browser connection (and not > > SSPI/Kerberos) on the same LDAP server host and port ? > > - could you check the connection LDAP extended controls that are used > > by both tools (LSC and LDAP brower) ? > > > > Could you maybe send us your wireshark capture? > > Clément.**** > > **** >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
