Search
Close this search box.
< All Topics
Print

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.
 
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:
https://en.wikipedia.org/wiki/Reverse_DNS_lookup
 
For help setting an environment variable, see this article.
 
If increasing the timeout doesn’t help, then you should run an activation diagnostics report. Set the environment variable “RLM_ACT_DIAGNOSTICS” to a filename, then start your application and attempt an activation. Once activation has been attempted, the RLM code will write the file.
 
For example, in a command prompt:

  • set RLM_ACT_DIAGNOSTICS=[Path to file]\filename.txt (Windows)
  • export RLM_ACT_DIAGNOSTICS=[Path to file]/filename.txt (bash)
  • setenv RLM_ACT_DIAGNOSTICS [Path to file]/filename.txt (C Shell)

RLM and RLM
Activation Pro

What’s the difference?

Reprise License Manager (RLM)

Software License Manager

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

As a Software publisher, you integrate RLM into your product, and RLM keeps track at runtime of who is using the licenses of your software.

RLM can do this entirely within the client library (linked into your application), or, more commonly, your application makes a request of the RLM Lincese Server to check out a license.

The lincese server runs either on your customers network, or in the cloud if you are using our RLMCloud™ service.

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

RLM Activation Pro

Software Activation Manager

Activation Pro is
used once when your customer purchases your software in order to retrieve the license which is specific to that customer.

Software Activation’s purpose in life is to get the licenses for your product to your customers with a minimum of fuss.

Activation Pro also has a server component wich we call the activation server.

Your application contacts the activation server and supplies a short text activation key, and in exchange, the activation server returns the license which enables your product.

Generally, this is done once, right after your customer purchases your software, not every time your software is invoked.