Communication Troubleshooting
Sometimes in troubleshooting problems with client applications connecting to license servers, it’s useful to have a tool outside RLM which can tell you whether messages can get through to the server. If a firewall or anti-virus package or proxy is blocking communications, a separate tool will have the same problems connecting to the server as […]
License Server Administration for Multiple Software Providers
Note: In this article we will refer to software publisher as an ISV (Independent Software Vendor). Standard Setup (recommended) A single RLM License Server is able to manage floating licenses issued by multiple ISVs. You will want to run the highest version of RLM provided to you by your ISV, or you can download the […]
Client Diagnostics
When troubleshooting you can generate an RLM client diagnostic report. Generating this report requires setting the “RLM_DIAGNOSTICS” environment variable. You can read more about setting environment variables here. When the RLM Client library is run (developers: specifically the rlm_init() API call), RLM will generate the diagnostic report to the file location specified in the environment […]
Activation Read Timeouts (Error -105)
On rare occasions, an activation request will get a read timeout status return (-105). If you can activate from some systems, then the first cause (server down) is unlikely. More likely is that there is either a proxy/firewall/anti-virus package blocking the response or the system fails a reverse DNS lookup and is timing out. […]
How to Set Environment Variables
Environment variables are flags that you set outside an application that the application reacts to. Applications and libraries, like RLM, read environment variables that they define. You can find a list of the RLM environment variables in our documentation. A characteristic of environment variables is that they are set in a process, like a […]
RLM Server Ports
Default Ports For a basic RLM server install with licenses from one Software Vendor (ISV), the server will use the following ports: 5053 – Default RLM server port 5054 – Default web administration port (embedded web server) A port between 1024 and 65353 – The ISV server port, dynamically assigned at startup. Setting custom […]
RLM Server Web Interface Passwords v15.1 – v15.2
Overview Beginning with RLM v15.1 it is mandatory to configure a password file to use the RLM Web Interface. RLM will generate a default password file if there isn’t already a password file present at startup. Previous versions RLM versions 10.0 to 15.0 allowed users to create a password file (rlm.pw), but this was […]
Floating License Timeouts
Overview RLM server administrators can configure a license timeout if a client computer has not returned the license, and if RLM is no longer able to check the license status on the client computer. This means that a Timeout will not return a license that is in use (say a user keeps an application checked […]
Using SSL Certificates (HTTPS) with RLM
Overview Starting with RLM version 15.1, License Administrators are now able to run the RLM web server with SSL certificates. When setup to use SSL certificates RLM’s web server will run with the HTTPS protocol. RLM does not come with pre-configured SSL certificates. You will either need to procure your own certificates from a Certificate […]
