Windows operating system
This troubleshooting information applies only to the versions of Microsoft Windows operating systems that are supported by IBM® Security Directory Suite, Version 8.0.
- System environment variables for non-English installation wizard
You must set the LANG and LC_ALL system environment variables for the installation wizard in non-English languages. - UTF-8 supplementary characters do not display correctly
Some UTF-8 supplementary characters might not be displayed correctly. You can install one of the East Asian language kits to resolve this problem. - Communications error: Exceeding 64 connections/OCH
On Windows systems, if clients are generating many connections to the server and the connections are being refused, the server might log error messages. Follow the steps to resolve these errors. - Error starting server at operating system startup
In IBM Security Directory Suite, the server (the ibmslapd process) is started manually through the Services window or by the ibmslapd command. If you try to start the server automatically by updating the Startup Type in the Services window to Automatic, errors might occur when you restart the computer. - Backup and restore from a remote drive fails
On a Windows operating system, when you back up, restore, or load by using DB2® utilities, the operation might fail. An error message that the path is not valid is displayed when you specify a directory that is mapped as remote drive. Understand the Windows access restrictions and use the troubleshooting information to resolve this problem. - DB2 diagnostic path error in idsdbmaint tool
On MicrosoftWindows operating systems, if DB2 is installed with the installation wizard, then the idsdbmaint tool might display an error that the DB2 diagnostic path cannot be determined. Run the specified DB2 commands to work around this problem. - Directory Server clients on Windows PowerShell
Windows PowerShell is not a supported shell for IBM Security Directory Suite. Therefore, when the Directory Server clients are run on PowerShell, they might not function as expected. - Log management tool fails to start
On Windows operating systems, the log management tool might fail to start from Web Administration Tool. This problem is related to user privileges.
Parent topic: Platform-specific issues