SLM server

This section describes the issues that can occur on the SLM server.

Windows Service Manager returns Internal Windows Error upon license server startup.

An error occurred during License Server startup. Check the Application Log in the Windows Event Viewer for Errors from Source: BCLM and Category: SlmServer, to find out what went wrong.

SlmServer -start reports that the SLM server is started, but when I look in the Windows Service Manager it shows that the server is not started.

An error occurred during License Server startup. Check the application log in the Windows Event Viewer for errors from the source: BCLM and Category: SlmServer to find out what went wrong.

License server doesn't run anymore. Message in the logging "System time tampered, restore to the original system time to restart the license service."

The license server has detected that the system time of the server is set to an earlier date.

Solution:

Restore the original system date and restart the license server. If this fails to resolve the problem contact Infor support and provide this information: the license.xml file, host name, and bclm ID of the failing server.

On UNIX: SLM server startup does not report any error but the server is not running.

An error occurred during License Server startup. Check the log file of the server: log.SlmServer.

SLM server logs error TCP bind() to port failed.

The error message is: "TCP bind() to port #### failed, error ###. Failed to start TCP Listener."

The server tries to use a socket port number that is already in use by another application or SLM server.

  1. Check whether another application or server is using that socket port number.
  2. Start the SLM server on another port number if another application is running on that socket port number. Note that this requires an update to the license file and a new activation key in case this server is part of a licensed environment.
  3. Wait a few minutes. If no other application or server is running on that socket port number the OS can release the socket port. Then try again.
  4. The OS only permits a process with root privileges to listen on port numbers less than 1024.

SLM server on Windows: "CreateService failed - The specified service has been marked for deletion"

Close the Services window and try again.

SLM server logs error: "Slave license-server waiting for notification from master license-server!"

Possible cause:

  • A standalone SLM server is running in slave mode.
  • No master license server is running in an SLM server group.

Solution:

  • A standalone SLM server must always be started in master mode.
  • In an SLM server group configuration, a slave license server must be notified by a master license server at startup before the slave starts to process license requests. This ensures that the slave license server is up to date with the latest license data available at the master license server.

On UNIX SLM serverlogs error: "Errno 24 (Too many open files)" and "SockAccept failed"

Most UNIX variants, for example, HPUX11, have a soft limit of 60 and a hard limit of 1024 file descriptors. If you place a high load on the license server, the soft limit is insufficient.

To resolve this issue, you can try to tune the UNIX kernel, or run the command: ulimit -n 1024 to set the user limit to the maximum of 1024.

Not all licenses are available in an SLM server group with no high availability support.

One of the SLM servers in the group does not run for longer than 72 hours (grace period), which reduces the number of licenses.

Check whether all the servers in the SLM server group are running. If not, restart the servers.