A drug development company, Lixoft, uses RLM Cloud for annual license renewals.
Today Reprise Software announced a new way for software publishers to license their products. It's called RLM Personal Edition (RLMpe).
On rare occasions, an activation request will get a read timeout status return (-105). There are several causes to the RLM_EH_NET_RERR (-105) error. They are described in the debugging section of the manual, repeated at the end here.
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.
The easiest way to test for this is to set the activation timeout to 60 seconds. Do this by setting the environment variable RLM_ACT_TIMEOUT to 60, and re-running your activation utility. If this fixes the problem, then you can either leave the timeout set to 60 or have your customer add a PTR record for their host as described in this article:
For help setting an environment variable, see this blog post.
If increasing the timeout doesn’t help, then disabling the proxy/firewall/anti-virus would be the next thing to try. It is beyond the scope here to attempt to address all possible proxy servers, firewalls, and anti-virus software.
Here is the debugging section from the manual:
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. Some RLM environment variables are RLM_ACT_TIMEOUT (adjusts the timeout to the activation server to the value supplied), RLM_QUEUE (enables queueing for a license), and RLM_ROAM (controls setting up, using, and returning roamed licenses). This is not an exhaustive list, but gives you an idea of what environment variables can do. In some situations, a Reprise Software support person may ask you to set a particular environment variable to some value and then run your application. This article is about how to set environment variables, not which ones are available in RLM.
A characteristic of environment variables is that they are set in a process, like a Windows command window or a Unix/Linux shell, and are inherited by processes that are created by that process. So if you create 2 command windows and you set an environment variable in window 1, it won’t be set in window 2. But if you run an application in window 1, the environment variable will be set in that application.
The easiest way to use an environment variable with RLM is to set it in a command window or shell, then invoke the application from that window or shell. For example, if you wanted to set RLM_DIAGNOSTICS to cause the application to write RLM diagnostic information to the file “diag.txt”
- Windows: set RLM_DIAGNOSTICS=diag.txt
- sh, bash : export RLM_DIAGNOSTICS=diag.txt
- csh: setenv RLM_DIAGNOSTICS diag.txt
Then invoke the application from the window where you set RLM_ROAM.
But it’s inconvenient or sometimes impossible to invoke the application from a command window on Windows. In that case you can set the environment variable via the Windows control panel:
- Bring up the control panel.
- Search for “environment” in the search box at the top right.
- Click on “Edit environment variables for your account.
- Enter the environment variable name and value.
- Click on OK in both windows.
RLM effortlessly allows software vendors and customers to change licensing models by simply changing the content of the license file itself. This allows software vendors to focus on usability and supporting the customer in configuring the floating license server itself.
Most developers involved in selecting and then implementing a software license management solution will freely admit that they are not experts in software licensing. Based on our discussions we have compiled the following list of the Top 10 Reasons why the Reprise License Manager (RLM) is preferred by today's busy software developers.
We compare licensing options for server-based software including floating licensing and using a licensing manager.
RLM stood out as a hassle-free and flexible solution for node-locked and floating licenses. When U-RENDER started evaluating different solutions for their own software product, RLM was already at the top of the list.
Whether it’s enterprise end-users wanting the best tools to maximize the usage of their valuable software assets, or software vendors wanting that next creative approach to licensing and selling their software, we’ve been there and done that.
You need an implementation strategy for license management that provides customers with all the licensing system components. These parts enable customers to control their software usage without burdening those customers who don’t. Here is how to build a win-win strategy for end-users and software publishers.