Search
Close this search box.

Reprise Blog

Reprise Software Blog – Your Hub for Licensing Solutions Insights
Stay informed about our products including Reprise License Manager (RLM), RLM Cloud, and Activation Pro. 

 

Learn from our customer success stories, understand the intricacies of different licensing models, and keep up with our ongoing service upgrades.

Dealing with Activation Read Timeouts (error -105)

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.

 

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

Other Posts

New RLM Release (v16.0)

The latest major release of RLM is finally here! Version 16.0 brings an all new web interface with many enhancements over the previous interface, and fixes multiple vulnerabilities related to the web interface. New Features Include: All-new Redesigned UI/UX Most server functions now available directly

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. Some RLM environment variables are RLM_ACT_TIMEOUT (adjusts the timeout to the activation server to the value supplied), RLM_QUEUE (enables

futuristic background with a cyber key in front

How to License Server-Based Software

We compare licensing options for server-based software including floating licensing and using a licensing manager.
U-RENDER logo over their rendering of a red sportscar

U-RENDER Accelerates Time to Market using Reprise License Management

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.

A Kinder, Gentler Licensing Strategy

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.
Photo of fossil in a rock

StrataData Consolidates its Licensing Around RLM

Using RLM, StrataData migrated to a more flexible licensing model which seamlessly integrated their existing dongles for those that wanted to retain them, as well as provide all the benefits of floating, server-based licensing.

Building Your Software Pricing Model

Deciding how to price your software products is a challenge that does not a have “one-size-fits-all” solution. A software license manager, such as the Reprise License Manager (RLM), is an indispensable tool that can help you to design and enforce pricing models that are right
Futuristic background showing charts and arrows moving upwards.

Pricing Strategies for Sublicensed Software Development Toolkits

Software pricing and licensing experts agree that optimal pricing strategies are rooted in value pricing. Pricing is easy for standard packaged products, but sublicensed SDKs pose pricing challenges. Here are some ways to create your ideal model.

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.