Release Notes › Policy Server Release Notes › Known Issues › Known Issues in r12.0 SP2 › Testing SunOne Directory Server Connections on Windows

Testing SunOne Directory Server Connections on Windows

Symptom:

You may experience problems testing a SunOne directory server connection from the Policy Server Management Console if:

• The machine that is hosting the Policy Server is also hosting the SunOne LDAP store.
• You are starting the Policy Server Management Console from a location other than policy_server_home\bin.
  • policy server home

    Specifies the Policy Server installation path.

This problem occurs because multiple versions of the same LDAP SDK library, nsldap32v50.dll, exist on the machine:

• The Policy Server installer installs one version of the DLL to policy_server_home\bin. This version of the DLL does not cause problems when you attempt to test the connection.
• SunOne installs another version of the DLL to the system directory, for example C:\WinNT\system32. This version of the DLL may cause problems when you attempt to test the connection.

Note: This DLL conflict does not affect Policy Server processes or any of the SiteMinder command-line tools.

On Windows, when any process calls the operating system (OS) library loader, the loader looks to specific locations, in the following order, to load the DLL:

1. The directory from which the process was launched
2. The current directory
3. The system directory, for example C:\WinNT\system32
4. The Windows directory, for example C:\WinNT\system
5. The directories that are listed in the PATH environment variable

Therefore, if you start the Policy Server Management Console from a location other than policy_server_home\bin, the OS library loader loads the DLL from the system directory, for example C:\WinNT\system32, which may cause problems when you test the connection.

Solution:

Start the Policy Server Management Console from the policy_server_home\bin location.