SLM Installation

The Installation Wizard shows an error message and stops the installation. The log file is empty.

Set the environment variable BSI_DEBUG to 0xFFFFFFFF and rerun the installation. Note that for a remote installation, the password is also logged. In that case, delete the log file afterwards!

The Installation Wizard writes logging to BCLMClient.log in your personal temp directory, for example:

C:\Documents and Settings\<your name >\Local Settings\Temp

The Installation Wizard cannot start the SLM server: Failed to bind UDP port 6005.

The SLMHOME/log/log.BclmServer or the Windows Event Viewer displays the message "Failed to bind UDP port 6005."

In that case, an SLM server is already running on that system, or another application is bound to that UDP port. By default, an SLM server uses UDP port 6005 to listen to broadcast messages. The Installation Wizard always starts a BclmServer with -uport 6005.

If an SLM server is running, you must stop that server, and restart the Installation Wizard.

If another application is bound to UDP port 6005 you can try to reconfigure that application to use another port. Or start SLM server to use another UDP port.

Not all running SLM servers are listed in the SLM server Configuration dialog box

The Installation Wizard uses UDP port 6005 to send a broadcast message over the network. That broadcast is carried out on the machine on which the Installation Wizard runs, and not on the machine on which the SLM server is installed.

Usually, all SLM servers that are running reply with a message to the wizard.

SLM servers do not respond, if:

  • During startup of the SLM server a non-default UDP port is passed when using the - uport option.
  • The SLM server is in a different segment and broadcast messages cannot pass segments, which is usually how the network is configured.
  • The network contains routers or switches that block the broadcast message.

For information on how to manually add SLM servers to your configuration, see Specifying servers.

The installer reports an error when reinstalling server or client package.

One of the shared libraries that are reinstalled is in use and cannot be overwritten. Stop all client and server programs that can be locking the shared library and retry. Check the log file because the file that can show processes that lock SLM files that prevents the upgrade process.

Locked file(s) detected installation cannot proceed.

Locked file(s) detected: Possible files:

  • SLMHOME/bin/BclmServer.exe
  • SLMHOME/bin/BclmMsg.dll
  • SLMHOME/shlib/com_baan_bclm_Bclmlmpl.dll

This error occurs when attempting to install SLM on a location where SLM is already installed. The SLM server is still running or a Java client is still active.

To resolve the problem, first retry the Install button. In most cases the installer stopped the involved program already. If unsuccessful, finish the installer and stop the SLM server or the SLM adopted application. Restart the SLM installer.

Some SLM shared library or DLL is still locked by an adopting application during upgrading Client or Server

Before you start to upgrade, you must stop all running adopting applications. In this way, you free the file locks.