LDAP error code 32 'No Such Object' with JNDI DYN endpoints in Identity Manager
search cancel

LDAP error code 32 'No Such Object' with JNDI DYN endpoints in Identity Manager

book

Article ID: 244319

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Manager

Issue/Introduction

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.

Environment

Identity Manager 14.5

Cause

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.

Resolution

To ensure reliable connectivity and resolve "No Such Object" errors, configure the endpoint to use failover mode only:

  1. Remove Load-Balancing: Update the JNDI DYN Endpoint configuration to remove the Load-Balancer VIP.
  2. Point to Specific Hosts: Configure the endpoint to point directly to a single, authoritative LDAP server instance or a failover-only address.
  3. Implement Failover: Utilize one of the following methods to ensure high availability without active load-balancing:
    • DNS Aliasing: Use a DNS record that resolves to the primary host, which can be updated to point to a secondary host in the event of a failure.
    • Local Host Files: Update hosts files on the Java Connector Server (JCS) machine for static failover resolution.
    • External Router: Use an external hardware or software router configured for "failover only" mode (ensuring requests always hit the same node unless it is down).
  4. Verify: Restart the JCS service and verify that requests are consistently routed to the intended LDAP node.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.