1. Home
  2. Support
Article - CS172161

LDAP error 34 Invalid DN Syntax when editing a group in the Administration Client in Integrity Lifecycle Manager

Modified: 06-Sep-2017   


Applies To

  • PTC RV&S (formerly Integrity Lifecycle Manager) 2009

Description

  • When editing a group in the Integrity Administration Client, the following error pops up immediately:
    • [LDAP: error code 34 - Invalid DN Syntax]
    • This causes the edit operation to fail
    • Users cannot be added / removed from the group
    • The following error appears in the server.log:
      • DEBUG mks.frame.security.server.EnumerationException: mks.frame.security.server.EnumerationException: people: [LDAP: error code 34 - Invalid DN Syntax]
        at mks.frame.security.server.domain.LDAPEnumerator.getInOU(LDAPEnumerator.java:1613)
        at mks.frame.security.server.domain.LDAPEnumerator.getUsersInOU(LDAPEnumerator.java:1538)
        at mks.frame.server.services.EnumerationConfig.getUsersInOU(EnumerationConfig.java:626)
        at mks.frame.rmi.LDAPUsers.<init>(LDAPUsers.java:58)
        at mks.frame.rmi.ServerLDAPManager.getUsersInOU(ServerLDAPManager.java:43)
        at sun.reflect.GeneratedMethodAccessor480.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at mks.util.MKSProxy.invokeDelegate(MKSProxy.java:285)
        at mks.util.MKSProxy.invokeInternal(MKSProxy.java:266)
        at mks.util.StatisticsProxy.invoke(StatisticsProxy.java:105)
        at $Proxy258.getUsersInOU(Unknown Source)
        at sun.reflect.GeneratedMethodAccessor479.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.sapia.ubik.rmi.server.invocation.InvokeCommand.execute(InvokeCommand.java:185)
        at mks.ubik.transport.beep.BeepServer$2.call(BeepServer.java:364)
        at mks.ubik.transport.beep.RmiInvocationAction.call(RmiInvocationAction.java:152)
        at mks.ubik.transport.beep.BeepServer.executeCommand(BeepServer.java:380)
        at mks.ubik.transport.beep.BeepServer$1.call(BeepServer.java:318)
        at mks.ubik.transport.beep.BeepServer$1.call(BeepServer.java:315)
        at mks.ubik.transport.beep.RmiInvocationAction.call(RmiInvocationAction.java:152)
        at mks.rmi.RmiAuthenticationHandler$1.run(RmiAuthenticationHandler.java:90)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:396)
        at mks.rmi.RmiAuthenticationHandler.doAs(RmiAuthenticationHandler.java:95)
        at mks.ubik.transport.beep.BeepTransportProvider.doAs(BeepTransportProvider.java:1130)
        at mks.ubik.transport.beep.BeepTransportProvider.doAs(BeepTransportProvider.java:1106)
        at mks.ubik.transport.beep.BeepServer.remoteExecuteCommand(BeepServer.java:333)
        at mks.ubik.transport.beep.BeepServer.handleCommandMessage(BeepServer.java:285)
        at mks.ubik.transport.beep.BeepServer.receiveMSG(BeepServer.java:176)
        at org.beepcore.beep.core.ChannelImpl.run(ChannelImpl.java:385)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
This is a printer-friendly version of Article 172161 and may be out of date. For the latest version click CS172161