SLM client

This section describes the issues that can occur with the SLM client.

Application does not start

The application cannot find, or bind to, the shared library.

Possible solutions to this issue include:

  • Check whether the shared library is installed on the system.
  • [WINDOWS] Check whether the Bclm.dll shared library can be found in the %PATH% environment.
  • [UNIX] Check whether the libBclm.[sl|so|a] can be found in the Shared Library Path of your system. For example; LD_LIBRARY_PATH or LIBPATH.

Adopting Application reports error regarding initialization of the SLM Application/Management API.

In this case, the error occurred during the client initialization. Check these situations:

  • SLM Client shared library file could not be opened or read.
  • SLM Client cannot open or read the server location file, servers.xml.
  • SLM Server is not running.

To resolve this issue:

  1. Start SlmClientTest from this directory: %SLMHOME%\bin\. The output provides you with possible warnings and errors found in your configuration and the steps to take to avoid these issues.
  2. [WINDOWS] Check the Application Event Log for errors from Source: Bclm for errors regarding the initialization of the Application or Management Client API.

    [WINDOWS] Check whether this available or set:

    • c:\Program File\Baan\Shared\shlib\BclmAppl.dll
    • %SLMHOME%\shlib\BclmAppl.dll
    • SLMHOME
  3. Check, if the client software is not installed in the default location, if the SLMHOME environment variable is set.
  4. Check if the servers.xml file is available and in the correct location.
  5. Check whether the syntax of the servers.xml file is correct.
  6. Check whether the SLM server is running.

Application reports error regarding connecting to license server.

The SLM client cannot contact the License Server. This can be the case:

  • No license servers are running.
  • The client configuration is bad.

Solution:

  1. Start SlmClientTest from your %SLMHOME%\bin\ directory. The output provides you with possible warnings and errors found in your configuration, and steps that you can take to avoid these problems.
  2. [WINDOWS] Search the Application Event Log for errors from Source: Bclm. Check for errors regarding the connection setup to the license server.
  3. Check whether the License Servers are up and running.
  4. Check whether the correct License Server hosts and port numbers are available in the servers.xml file.
  5. Check, if the License Server runs on a remote machine. Use ping or telnet from the local host, whether the remote machine is reachable on the port where the server must be running. For example, a firewall can block the remote machine.

Application reports error regarding no license available for product.

The SLM client cannot receive a valid license. This can be caused by one of these reasons:

  • License server is in maintenance mode. In this case, the license server denies each license request.
  • Product is not licensed at the license servers.
  • License servers are out of licenses for this product.
  • Licenses are expired for the product. Check the validation period.
  • Desktop, user, or server is unknown for this product at the license servers.

The solution is:

  • Check the logs of the application and the logs of the license server. On Windows that is the EventViewer. On UNIX <SLMInstalldir>/log/log.SlmServer. If multiple servers are defined, ensure to check the log files of all these servers.
  • If the product is unknown/unlicensed at the license server, obtain a valid license for the product.
  • If the license server is in maintenance mode, a license file with a valid activation key is missing. Or the SlmId of the license server does not match any of the IDs in the license file. The log file indicates the reason why the license server is in maintenance mode.

Connection errors on high-volume Windows application server

Windows is running out of sockets.

  1. Decrease the release of sockets delay time. For information on how to decrease the delay with the use of the TcpTimedWaitDelay parameter, see MSDN article 149532.
  2. Increase the number of available sockets. See MSDN article 151418 to increase the number of sockets using the MaxFreeTcbs and MaxHashTableSize parameters.