Reprise Software
End User FAQs

Q: How do I use RLM across a firewall?

If you want to serve licenses across a firewall, generally the types of license servers, i.e. RLM and ISV, need known port numbers in order for your firewall to pass requests on these ports. The RLM server is always at a known port number - specified in the license file on the SERVER or HOST line. Typically, RLM starts up all the ISV servers with dynamic port numbers which are not known before startup time.

It is possible to have RLM assign fixed port numbers to the ISV servers. To do this, specify the port number for the ISV server on the ISV line. The port number is the fifth parameter in the isv line:

ISV isvname isv-binary options-file port-number

In order to specify the port number, you must also specify an options file for this ISV server.

Once you have specified the port number, instruct your firewall to allow connections to both the port number on the SERVER line (for RLM) and the port numbers on any ISV lines.

Note: Beginning in RLM v9.0, you can specify the ISV server port number with the optional "port=xxx" parameter on the ISV line, as such:

ISV isvname binary=isv-binary port=port-number
ISV isvname isv-binary port=port-number

Using this method, you do not have to specify an ISV options file.

Q: On Windows, RLM fails to start the ISV server with a select(), getsockname() or "communications (socket) problems" error. What's wrong?

Reprise has had reports on a very limited number of systems that RLM fails to start the ISV server, with errors similar to the following written to the debug log (note: the ISV name will be your ISV name, not necessarily "demo"):

03/16 04:12 (demo) select() failure: Unknown error
03/16 04:12 (demo) Out of file descriptors: Cannot clone communications handle: Unknown error
<last error repeats 10 times>
03/16 04:12 (demo) Too many errors on main socket, exiting

This error sometimes results in debug log output similar to the following:

01/06 10:11 (rlm) Starting ISV demo
01/06 10:11 (rlm) Error in getsockname() call 13
01/06 10:11 (rlm) ... demo on port 57809
01/06 10:11 (rlm) New thread created to watch ISV demo
01/06 10:11 (rlm) demo initialization error: 1, not restarting

Or the following:

01/05 12:50 (rlm) Starting ISV servers:
01/05 12:50 (rlm) ... demo on port 1088
01/05 12:50 (rlm) New thread created to watch ISV demo
01/05 12:50 (rlm) demo - communication (socket) problems

This problem is caused by a registry corruption (not induced by RLM) that affects some network operations. The fix is to open a command window and type the command:

$ netsh winsock reset

Should the above "netsh" command not solve the problem, Microsoft has published the following article on how to correct the registry when this occurs. Note that the error message indicating the problem is different in the article than the RLM error message indicating the problem, but the underlying cause is the same.


Q: When starting RLM, I get the message, "(rlm) Cannot bind Web Server port 5054, exiting." What is the problem and solution? (Note: This message may also indicate port 9000, which was used by older versions of RLM.)

That error message typically indicates another copy of RLM is running which is using port 5054 or 9000.

Check your system for other running copies of the RLM server and if they should not be running, stop them. Then, restart the RLM server.

Another possible problem is that another program is using the port. Use the "netstat" command to see if another program is using this port.

Q: RLM gives the following error message when attempting to install itself as a service on Windows from an account with administrator privileges: "Error: Access to Service Control Manager denied." What is the problem and solution?

Launch a command window using "Run as administrator", and install RLM from the new command window. "Run as administrator" is an option when you right-click on the command window icon on the desktop or in the start menu.

Q: When I install the RLM server as a Windows service, it fails to start. Windows gives me an error saying that the service failed to start in a timely fashion. What is the problem and solution?

The RLM server log file frequently contains information that identifies the startup problem. The RLM log file file location is specified by the "-dlog logfile" argument on the RLM command line when using the "-install_service" option. If you install the RLM service via the RLM web interface, the log file location is specified in the box labeled "Server Debug Log". In RLM v8 and later if you specify a relative path, that path will be relative to the location of rlm.exe. For example, if the debug log path is specified as "myrlmlog.log" and rlm.exe is located in "c:\rlm", the debug log will be "c:\rlm\myrlmlog.log". In versions prior to v8, the specified relative path is relative to \windows\system32. When running as a Windows service, rlm.exe and the ISV server run under the user name "SYSTEM". Make sure that the log file location that you specify can be written to by that user.


For Software Publishers

For License Admins