User Directory Synchronisation Failed Due To Lexical Error
Symptoms
- Synchronisation fail when connecting to parent tree
- But, synchronisation successful when connecting to one child tree
The following appears in the atlassian-jira.log:
ERROR ServiceRunner [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10200 ].
com.atlassian.crowd.exception.OperationFailedException: java.util.concurrent.ExecutionException: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: problem generating object using object factory [Root exception is org.springframework.ldap.BadLdapGrammarException: Failed to parse DN; nested exception is org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column 18. Encountered: "\\" (92), after : ""]; remaining name 'OU=example,DC=atlassian,DC=com'
at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseAllUsers(UsnChangedCacheRefresher.java:266)
...
Caused by: org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column 18. Encountered: "\\" (92), after : ""
...Cause
There is child tree that has special character in it's name. Refer to Characters in User or Group DN's that will cause problems when using Crowd for detail.
Resolution
Either of the following will resolve the issue:
- Remove special character from the child trees under the parent tree that failed during synchronization
- Configure JIRA to connect to specific child trees only
Please see our Troubleshooting LDAP User Management documentation for further assistance with diagnosing LDAP problems.
Last modified on Nov 2, 2018
Powered by Confluence and Scroll Viewport.