Clarity PPM - LDAP jobs fail with LDAP: error code 32 - The search base entry [..] does not exist

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

There is an error when running the Clarity jobs - LDAP - Synchronize Obsolete Users and the LDAP - Synchronize New and Changed Users job. 

Error in logs (exact directory names modified for privacy reasons):

com.niku.security.directory.DirectoryServiceException: javax.naming.NameNotFoundException: [LDAP: error code 32 - The search base entry 'ou=XX,ou=retired,o=internal,dc=domain,dc=com' does not exist]; remaining name 'ou=XX,ou=retired,o=internal'
 at com.niku.security.directory.LDAPAddModifySyncAgent.scheduledEventFired(LDAPAddModifySyncAgent.java:60)
 at com.niku.njs.Dispatcher$BGTask.run(Dispatcher.java:657)
 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 at java.base/java.lang.Thread.run(Thread.java:834)

Environment

Release : Any

Resolution

• Please engage your Active Directory admin to work on this issue. Our job does nothing to the LDAP server, it simply reads information from it based on the string in the CSA.
• No information is sent from Clarity to the Active Directory. This error is not a Clarity error but thrown by the LDAP server itself because the request set up in CSA did not retrieve the expected data.
• This may be caused by a root context that is wrong
• Also it would be caused by search request need to be corrected in CSA to avoid the organization unit
• If you have deleted a resource pack/group, but retired users still are there, this will be a problem.  
• Please remove all the retired resources that are in the group that's throwing an error.