javax.naming.InvalidNameException: [LDAP: error code 34 – invalid DN]

Affected Version: 4501
Component: OpenLDAP 2.4
Issue Description:
After upgrading Ephesoft 4500 to 4501 and then trying to connect to LDAP that ephesoft provides we see an error “Error 34 : Invalid DN”

 

Exception:

javax.naming.InvalidNameException: [LDAP: error code 34 – invalid DN]
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3095)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2886)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2800)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83)

Workaround:

Replace the OpenLDAP 2.4 folder from 4500 backup and replace the same with 4501 OpenLDAP 2.4 folder in Ephesoft -> Dependencies and restart the OpenLDAP service