This article addresses intermittent "LDAP: error code 32 - No Such Object" errors encountered when viewing or modifying objects on a JNDI DYN endpoint. This issue is typically caused by improper load-balancing configurations that prevent consistent access to the backend LDAP directory.
Identity Manager 14.5
The error occurs when the JNDI DYN Endpoint URL points to a load-balanced Virtual IP (VIP) rather than a specific directory server instance. Because LDAP servers may experience replication delays, routing requests across multiple backend servers faster than replication can occur results in intermittent failures where an object exists on one node but not yet on another.
To ensure reliable connectivity and resolve "No Such Object" errors, configure the endpoint to use failover mode only:
hosts files on the Java Connector Server (JCS) machine for static failover resolution.To speak with a customer representative or a Support Engineer see . Scroll to the bottom of the page and click on your respective region.