Error when acquiring the DB2 Endpoint [LDAP: error code 32 - No such object found]

Products

• CA Identity Suite

Issue/Introduction

When acquiring the DB2 endpoint, the process is failing with the error message below:

2025-09-24 12:08:14,985 695037245 [ApacheDS Worker-thread-46] (com.ca.jcs.csproxy:com.ca.jcs.csproxy.CSProxyActivateConnectorProxy:146) ERROR - Error activating proxy connector during operation: doAdd
org.apache.directory.shared.ldap.exception.LdapNameNotFoundException: JCS@DB2SRVR: JNDI: Failed to activate connector on proxy connector server: [LDAP: error code 32 - No such object found]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)[:1.8.0_231]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)[:1.8.0_231]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)[:1.8.0_231]

Environment

Identity Manager v14.5.1 (Latest release)
Windows Server 2019 Standard Edition

Cause

 

The 64-bit DB2 UDB Administrative Client was installed instead of the 32-bit version.

 

 

Resolution

Installing the 32-bit version of the DB2 Administrative Client should resolve the issue.

During installation, it was observed that both the 32-bit and 64-bit versions of the DB2 client were installed. The PATH environment variable was pointing to the 64-bit DB2 library location, which is incompatible with the DB2 endpoint. To address this, you need to update the PATH variable to include the 32-bit library path (%SystemRoot%\SysWOW64) and remove the 64-bit reference (%SystemRoot%\System32) before acquiring the DB2 endpoint.

After successfully acquiring the DB2 endpoint and completing the installation, the PATH variable can be reverted to its original state by removing the 32-bit path and restoring the 64-bit reference.