javax.naming.InvalidNameException

[LDAP: error code 34 - Invalid DN Syntax]

Solutions on the web74

  • via Google Groups by ssrJazz, 6 months ago
    [LDAP: error code 34 - Invalid DN Syntax]
  • via Google Groups by Dan McLaughlin, 1 year ago
    [LDAP: error code 34 - Invalid DN Syntax]
  • [LDAP: error code 34 - Invalid DN]
  • Stack trace

    • javax.naming.InvalidNameException: [LDAP: error code 34 - Invalid DN Syntax] at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2973)[na:1.6.0_22] at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2780)[na:1.6.0_22] at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2694)[na:1.6.0_22] at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:306)[na:1.6.0_22] at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)[na:1.6.0_22] at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)[na:1.6.0_22] at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)[na:1.6.0_22] at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)[na:1.6.0_22] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)[na:1.6.0_22] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305)[na:1.6.0_22] at javax.naming.InitialContext.init(InitialContext.java:240)[na:1.6.0_22] at javax.naming.InitialContext.<init>(InitialContext.java:214)[na:1.6.0_22] at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:99)[na:1.6.0_22] at org.openmeetings.app.ldap.LdapAuthBase.authenticateUser(LdapAuthBase.java:103)[openmeetings.jar:na] at org.openmeetings.app.ldap.LdapLoginManagement.doLdapLogin(LdapLoginManagement.java:376)[openmeetings.jar:na] at org.openmeetings.app.remote.MainService.loginUser(MainService.java:346)[openmeetings.jar:na] at sun.reflect.GeneratedMethodAccessor372.invoke(UnknownSource)[na:na] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[na:1.6.0_22] at java.lang.reflect.Method.invoke(Method.java:616)[na:1.6.0_22] at org.red5.server.service.ServiceInvoker.invoke(ServiceInvoker.java:199)[red5.jar:na] at org.red5.server.service.ServiceInvoker.invoke(ServiceInvoker.java:116)[red5.jar:na] at org.red5.server.net.rtmp.RTMPHandler.invokeCall(RTMPHandler.java:160)[red5.jar:na] at org.red5.server.net.rtmp.RTMPHandler.onInvoke(RTMPHandler.java:406)[red5.jar:na] at org.red5.server.net.rtmp.BaseRTMPHandler.messageReceived(BaseRTMPHandler.java:134)[red5.jar:na] at org.red5.server.net.rtmp.RTMPMinaIoHandler.messageReceived(RTMPMinaIoHandler.java:207)[red5.jar:na] at org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:716)[mina-core-2.0.4.jar:na] at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)[mina-core-2.0.4.jar:na] at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)[mina-core-2.0.4.jar:na] at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)[mina-core-2.0.4.jar:na]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You are the first who have seen this exception. Write a tip to help other users and build your expert profile.