End-User Frequently-Asked-Questions

Installation and Configuration

Q1. How do I use RLM across a firewall?  Click Here For Answer

Q2. on Windows, RLM fails to start the ISV server with a select() error.  What's wrong? Click Here For Answer

Q3. When starting rlm, I get the message "(rlm) Cannot bind Web Server port 9000, exiting".  What is the problem and solution?  Click Here For Answer

Q4. rlm gives the following error message when attempting to install itself as a service on Vista from an account with administrator privileges: "Error: Access to Service Control Manager denied".  What is the problem and solution?  Click Here For Answer

 

Answers

Q1. How do I use RLM across a firewall?

If you want to serve licenses across a firewall, generally you will need the license servers to have known port numbers in order to allow your firewall to pass requests on these ports.  The rlm server itself is always at a known port number (contained 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.

However, it is possible to have RLM assign fixed port numbers to any of the ISV servers.  In order to do this,  you need to specify the port number for the ISV server on the ISV line.  The port number is the fourth parameter in the isv line:

      ISV isvname 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.

 

Q2. on Windows, RLM fails to start the ISV server with a select() 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 can be caused by corruption of some values in the Windows registry. Reprise has no reason to believe that RLM is responsible for this registry corruption. 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.

    http://support.microsoft.com/default.aspx?scid=kb;en-us;817571

Also, we have heard from our customers (but have not been able to verify) that running this command clears the problem:

netsh winsock reset
 

Q3. When starting rlm, I get the message "(rlm) Cannot bind Web Server port 9000, exiting". What is the problem and solution?

That error message generally indicates that there's another copy of RLM running, which is using port 9000 for it's web server port.

Check your system for other running copies of the rlm server, and if they should not be running, stop them, then re-start the rlm server.

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

Q4. rlm gives the following error message when attempting to install itself as a service on Vista 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.

 

To find out how the Reprise License Manager can improve your company's licensing strategy, please contact us via email at info@reprisesoftware.com