RLM Issues Affecting License Administrators and Users

Software License Management Issues Resolved

We are constantly striving to improve RLM to make sure license administrators and users do not face any issues. Here is a complete list and details regarding all the issues that have been resolved from version 8.0 to present.
To hide the full description, click on the issue title or the '-' sign on the left.


expand list (Good for searching full description in browser).
collapse list

P453 - rlm crash when editing license/options files
RLM will sometimes crash in the web server while editing license or options files. This has been reported when there is an INCLUDEALL internet line in the rlm.opt file, but could happen anytime. The reports are all on Linux systems.

This is fixed in RLM v12.1BL3.
Fix affects: rlm

P452 - UPGRADE processing failure
UPGRADE processing makes only one pass thru the license files, so if there are multiple UPGRADE lines and they are out of order, they will not all be processed, resulting in some licenses not being upgraded.

To work around this problem, place all UPGRADE lines for a particular product into one license file, ordered from the lower versions to the higher versions.

This is fixed in RLM v12.1BL3.
Fix affects: isv server, client

P444 - rlm web server memory leak
rlm leaks 2 x MAXPATHLEN (~2050) bytes of memory every time a web server login is processed

This is fixed in v12.1
Fix affects: rlm

P441 - multi-character usernames can't be removed from named user licenses
If a user with a multi-character set name is added to a named-user license, they cannot be removed in the rlm web interface.

This is fixed in v12.1
Fix affects: server

P440 - ISV server crash with no HOST line
If RLM is started with a license file containing an ISV line and an uncounted license but no HOST line, the ISV server crashes on startup.

This is fixed in v12.1

A workaround is to put a HOST line in the license file.
Fix affects: server

P439 - server crashes on windows 10 with rlm_init_disconn()
The x64_w4 ISV server crashes on Windows 10 if the client calls rlm_init_disconn(). The crash happens the next time the client sends a message to the server. This only affects x64_w4 on Win 10.

This is fixed in v12.0BL2-p3
Fix affects: server

P438 - server crashes on windows 10
The x86_w4 and x64_w4 rlm crashes on Windows 10 on startup.

This is fixed in v12.0BL2-p3
Fix affects: server

P437 - actpro_url doesn't work in settings file
Settings files don't allow setting the activation pro URL unless there is a server_roam license present. (This bug does not affect ISV server binaries, only settings files)

This is fixed in v12.1
Fix affects: isv server settings file
As a workaround, set the SERVER_ROAM license in rlm_isv_config.c. You can use this license:
#define SERVER_ROAM_LICENSE "‹LICENSE demo rlm_roam 1.0 permanent uncounted hostid=any sig=\"60P04521WWPSXMX74NQ6QY9B0EDJJFY3P4M2YX822GX5YJ95F8QX6H4R940DWMHVS5HFTQEG44\"\›"
rlm_isv_cfg_set_server_roam(handle, SERVER_ROAM_LICENSE);

P436 - pre v12.0 clients fail with v12.0 server
A pre-v12 client cannot check out a license from a v12 server.

This is fixed in v12.0BL2-p2, which is on the website now.
Fix affects: server
As a workaround, setting the environment variable RLM_LICENSE_PASSWORD to any non-empty value will allow checkouts to proceed normally.

P435 - HP/UX 64-bit server issues
v12.0 HP 64-bit license servers refuse to run after being shut down; they report lockfile problems. The preferred workaround is to use a 32-bit server. If that is not practical, then delete the lockfile in /var/tmp/.rlmlockISVNAME before re-starting the server.

This is a permanent restriction.
Fix affects: 64-bit hp server.

P422 - web interface timeout issues
If a user's login to the rlm web interface times out, the web interface displays "logins disabled" rather than the login screen.

Refreshing the browser will display the login screen.

This is fixed in RLM v12.0.
Fix affects: rlm.

P421 - rlm password file errors
If you have an rlm password file with "user1" and "user11" (ie, the 1st username is a substring of the second), then change password for user1, user11's password gets changed also.

This is fixed in the next release - RLM v11.3BL2 or v12.0.
Fix affects: rlm.

P411 - Can't eject USB device while RLM running
Can't eject a USB device while an RLM-licensed app or license server is running.

This is fixed in RLM v11.3BL1.
Fix affects: client, server.

P410 - rlm web interface inconsistency.
The rlm web interface reports transactions against the wrong license pool. With a v1.0 and a v2.0 license, if the v2.0 license is checked out, the v1.0 license's transaction count is incremented. The checkout is shown in the correct place, this is only an error where the transaction is shown in the web interface.

The column previously labeled "transactions" is now labeled "checkouts".

This is fixed in RLM v11.3BL1.
Fix affects: server.

P404 - rlm binds port 5053 incorrectly
If a license file specifying an rlm port other than 5053 is present, and a second license file containing only an uncounted license is also present, rlm will bind 5053 in addition to the port specified on the HOST line. Port 5053 should not be bound in this case.

This is fixed in RLM v11.2BL3.
Fix affects: rlm.

P393 - licenses roamed from a broadcast server can't be checked in
If a license is roamed from a server which is found by broadcast (rather than license file or RLM_LICENSE), the license cannot be checked back in early - it must time out.

This is fixed in RLM v11.2BL1.
Fix affects: client

You can work around this problem using the following method:
1. determine the port # of the ISV server used to roam the license (from the debug log at the time of roam)
2. Set up the ISV server to use this port (specify the port # on the ISV line)
3. Set RLM_LICENSE to this-port#@server-host
4. Set RLM_ROAM to -1 and check out the license.

P389 - rlm_enable_server_vm licenses appear in status (they shouldn't) on non-VM servers.
This is fixed in RLM v11.2BL1. Fix affects: server
P388 - The Qualsys Guard security vulnerability scanner crashes rlm on Windows
This is fixed in RLM v11.1BL2. Fix affects: rlm
P383 - rlm web interface loses filter values
In the rlm web interface, if you filter the license status field by product, user, and/or host, these filter values are lost on a refresh.

This is fixed in v11.1BL1.
Fix affects: rlm.

P381 - login problems with multiple rlm sessions
If multiple instances of rlm are running on one system, logging in to the web interface of one automatically logs in to all with the same privileges.

This is fixed in RLM v11.1BL1
Fix affects: rlm

P372 - RLM web interface password file security issue
If an RLM password file is present, and a user isn't logged in to the RLM web interface, they are able to execute web interface commands if they know the correct internal URL for the command.

This is fixed in RLM v11.1BL1
Fix affects: rlm

P371 - windows servers lose information about roamed licenses.
If a windows server is shut down, it loses information about any roamed licenses.

This is fixed in RLM v11.1BL1
Fix affects: server

P353 - 2 ISV servers with the same port # cause rlm to crash
If 2 ISV servers are specified to use the same port in the license file, RLM crashes.

This is fixed in RLM v11.0BL1.

Fix affects: rlm

P350 - A valid disk serial number is sometimes ignored
A valid disk serial number can be thrown out if it has a null model number. This is fixed in RLM v11.0BL1. Fix affects: client, server.
P348 - Duplicated licenses cause internal double-free
Duplicate uncounted licenses in separate license files are discarded by the fix to P316, but an internal error causes a double free of internally-allocated data when the handle is closed.

The workaround is to remove these duplicate license files.

This is fixed in RLM v11.0BL1.
Fix affects: client.

P347 - "virtual floppy" disk models trigger false VM detect
A system with a disk model "virtual floppy" triggers the virtual machine detection. Also "Dell VIRTUAL DISK SCSI Disk Device" causes the same problem. This is fixed in RLM v11.0BL1. Fix affects: client, server.
P345 - login errors (32-bit Linux)
The RLM admin web browser will give a "not logged in" error when a user is in fact logged in, and tries to change the password. This error has been observed on 32-bit Linux platforms only. A workaround is to change the password on another system, and copy the password file to the Linux server system. This is fixed in v11.0BL1. Fix affects: rlm
P344 - multiple dongles sometimes missing (Windows)
The hostid list generated by _rlm_hostid_list() will be missing dongles if the number of dongles attached to the system is greater than the number of IP addresses on the system. This is fixed in RLM v11.0BL1. Fix affects: client
P342 - quoted strings in counted licenses - checksum errors
A counted license containing a quoted string (eg platform=) spanning lines, signed on Windows and consumed on Unix will cause an error in the checksum checking code, due to Windows carriage control. The license authenticates correctly and is served, but an error is logged to the debug log. A workaround is to run dos2unix on the license file, or remove the _ck= attribute from the license. This is fixed in RLM v11.0. Fix affects client, server.
P341 - rlm looks in the wrong directory for password file
The RLM documentation states that the server looks for the password file, rlm.pw, in the directory where the rlm binary exists, but actually it looks in the current working directory. This is fixed in RLM v10.1BL2 - rlm now (correctly) looks in the directory with the rlm binary. Fix affects: rlm
P340 - rlm crash after warning
If rlm logs "Warning: rlm_path is <NULL>", the null path may cause rlm to segment fault. We believe this only happens with "-c license_file" is specified on the command line. As a workaround, run rlm from the license directory and don't specify "-c". This is fixed in RLM v10.1BL2. Fix affects: rlm
P339 - rlm_products() doesn't handle NL, Uncounted licenses
Upgrade lines aren't processed before rlm_products() is called, (unless rlm_checkout() is called first), so upgraded nodelocked, uncounted licenses in local license files are not handled correctly. This is fixed in RLM v10.1BL1. Fix affects: client.
P338 - ISV server hang
The ISV server can hang if the following are all true:

(1) client is linked with RLM pre-v9.3

(2) client calls rlm_auto_hb() with automatic reconnection

(3) the checked-out license involved is a token-based license,

(4) the token definition is in the license file AFTER the enabling license, or is processed later in a different license file, and

(5) the reconnection handler attempts to re-acquire the license.

This is fixed in RLM v10.1BL1.

Fix affects: server.

P337 - rlm web interface memory leaks
The rlm web interface will leak memory when requesting ISV server pool status or a list of users. This is fixed in RLM v10.1. Fix affects: rlm.
P335 - server errors with disconnected clients
If a disconnected client doesn't check with the server during it's promise interval, the server may send bad messages to other clients. This is fixed in RLM v10.1. Fix affects: server.
P334 - On windows, "ISV <isv> <isv>" will not find server
On windows, the ISV line: "ISV <isv> <isv>"
will not find <isv>.exe.
This is fixed in RLM v10.1.
Fix affects: server.
P333 - On Windows, a space in DEBUGLOG path causes crash
On Windows, a space in the DEBUGLOG path in the options file will cause an ISV server crash when a checkout is done. This is fixed in RLM v10.1. Fix affects: server.
P329 - extra roaming licenses checked out on server
If there are 2 pools for a license and a license is roamed from one of the pools, when the server is restarted it takes a license from both pools and can't recreate the roam handle in the 2nd pool. This happens if the 2 pools have the same product name, version, share flags, max_share, and hostid, but other license fields are different. This is fixed in RLM v10.1, however the fix invalidates older server roam files, so all roamed licenses should be returned before the upgrade. NOTE that if the licenses aren't returned, the only downside is that the roamed licenses will still be valid until they expire, and the server will allow them to be checked out from the general pool of licenses as well. Fix affects: server.
P327 - extra checkouts with auto heartbeats when disconnect
Using automatic heartbeats, if a node is disconnected from the network while a license is checked out, when it reconnects it will check out multiple licenses.

This is fixed in RLM v10.1

Fix affects: client.

**********************************************************************

NOTE: The fix for P327 involves a change in the way rlm_get_attr_health() processes licenses with errors on their server connections. Previously, once an error was detected, the status was never updated from that error. Starting in v10.1, rlm_get_attr_health() will check the connection to the server each time it is called, even if the connection is in an error state. This means that the condition can be cleared and the license re-validated if the connection is repaired (for example, in the case of a temporary network disconnect. Please see the RLM Reference Manual for more details.

**********************************************************************

P324 - Linux system in GMT+0 is not recognized in correct TZ
A Linux system in GMT+0 is not recognized as being in the correct timezone even if bit 0 is set in the timezone mask. This is fixed in RLM v10.0BL3. Fix affects: client and server.
P323 - too many license filenames crashes RLM
If the total length of all the file names in a license file directory exceeds 10000 characters, the rlm client code will crash. This is fixed in RLM v10.0BL3. Fix affects: client.
P322 - TIMEOUTALL option not always effective
If a TIMEOUTALL option is specified and a license with a min_timeout specification follows another license with a higher (or no) min_timeout, the earlier min_timeout (or default) will be used instead of the min_timeout in the license. This is fixed in RLM v10.0BL3. Fix affects: server.
P321 - appending to debug log causes service install failure
When installing a Windows service, specifying append to the RLM debug log file (+<file>) results in a "can't write debug log" message and the service installation fails. This is fixed in RLM v10.0BL3. Fix affects: rlm.
P320 - broadcast only works for first operation.
If broadcasting for a server, only the first operation works. Subsequent operations will fail to find the server. If a 2nd checkout is attempted, it will fail with RLM_EL_NOPRODUCT (-1). This is fixed in RLM v10.0BL3. Fix affects: client.
P314 - roam checkout requests sometimes incorrectly denied
If there are 2 licenses which can roam, and the first license cannot satisfy the roam request (ie, all licenses are currently roamed, or the request is for more than the maximum # of roam days), then the roam will fail. This is fixed in RLM v10.0BL2. Fix affects: Server.
P310 - "random" server crashes
P310 - If there are:

2 licenses of the same name, version, and hostids which otherwise don't pool (see below), and

one or more licenses from the first pool are checked out, and

then a reread is done on the server

... then the server loses track of the licenses from the first pool.

When the client checks the licenses back in, the server will access freed memory when logging the checkin message. The symptom on Windows is sometimes that the ISV server exits with an "exit 255".

This is fixed in RLM v10.0BL2.

Fix affects: server.

2 licenses will not pool if any of the following attributes do not match:

password

options

disable

share

max_share

timezones

platforms

count type (SINGLE, UNCOUNTED, COUNTED, TOKEN)

user_based

host_based

any metering parameter

P309 - ISV debug log w/append doesn't appear in diags
If the ISV options file specifies a debug log in append mode (+filename) the ISV debug log will not be included in diagnostic output. This is fixed in RLM v10.0BL2. Fix affects: server.
P308 - Roaming a license with '/' in the product name fails
Roaming a license with a '/' in the product name fails with a roam data write error (-124). This is fixed in RLM v10.0BL2. Fix affects: client.
P306 - Server instability with token-based licenses
If a token-based license remains checked out when a reread is done on the server, the "requested license" field becomes invalid. This field points to deallocated memory, so subsequent requests for a userlist can cause random server problems (such as server crashes). Note that either the "rlmstat -a" command, or the license usage in the RLM web interface will request a userlist. This bug only happens when token-based licenses remain checked-out during a reread. This is fixed in RLM v10.0BL2. Fix requires: server.
P304 - status command sometimes fails to show last pool
In certain circumstances, rlmstat or the RLM web interface status command will not display the last license pool for an ISV server. This is fixed in RLM v10.1BL1. Fix affects: server.
P303 - license transfer doesn't work for some ISV settings
License Transfer will not work if the ISV server is a settings file built with a different RLM version from the version of the rlm server binary. This is fixed in RLM v10.1BL1 Fix affects: rlm
P302 - Linux client can leak file descriptors
On linux, if an RLM-licensed client is able to connect to rlm but not to the ISV server, the application will leak file descriptors, one for every rlm_checkout() request that is made (even if rlm_checkin() is called). This will also run the rlm process out of file descriptors if it continues long enough before the client process exits. This is fixed in RLM v10.1BL1. Fix affects: client.
P301 - The -x rlmdown option doesn't restrict web interface
The -x rlmdown option to rlm does not prevent the web interface from shutting down a single ISV server, if the ISV server is selected individually. This is fixed in RLM v10.1BL1. Fix affects: rlm
P300 - Rehostable licenses become invalid on switch to DST
Rehostable licenses on Windows are invalid in Daylight Savings Time if created in Standard time, and invalid in Standard Time if created in Daylight Savings Time. This is fixed in v10.0BL1. Fix affects: client.
P299 - ISV settings file is sometimes not found
If:

the license file has an ISV line with an ISV path with no file extension, AND
the ISV name is <= 4 characters, AND
a settings file is in place with the .set extension

then RLM will not find the settings file.

The workaround is to add the ".set" to the ISV name in the license file, or rename the settings file to not have the .set extension.

This is fixed in RLM v10.0BL1.
Fix affects: rlm.

P298 - '@' character in license filename path doesn't work
if the path to the license file contains the '@' character, RLM will ignore that license file. This is a permanent restriction. The RLM documentation will be updated to reflect this case.
P297 - server returns wrong expiration date in rlm_products
If the license server combines 2 licenses, one unexpiring and one with an expiration date, then it will return an expiration date of "permanent" when rlm_products() or rlm_license_exp() is called. The server should return the earlier, ie, expiring license date in this case. This is fixed in v10.0BL1. Fix affects: server.
P294 - Long lines of random characters crash the LF parser
Long lines of random characters in the license file causes RLM to crash in the parser. This is fixed in v9.4BL4. Fix affects: client, server.
P293 - short disk serial numbers confuse RLM's VM detection.
If a disk has a serial number of less than 8 characters and a null model number string, RLM will incorrectly report that it is running on a virtual machine. This is fixed in v9.4BL4. Fix affects: client, server.
P290 - hostname wildcard matching in v9.4 does not work
The hostname wildcard matching feature which was scheduled to be in v9.4 did not make it into the release. This code will be in v9.4BL4 and beyond.
P286 - RLM fails to detect a VMware VM if disk SN too short
RLM will fail to detect a VMware Virtual Machine if the disk serial number in the VM is less than 8 characters. This is fixed in RLM v9.4BL2. Fix affects: client, server
P282 - rehostable hostid creation fails
Creating a rehostable hostid fails on windows if the reprise directory (\ProgramData\Reprise) does not exist. This is fixed in v9.4BL2. Fix affects: client.
P281 - hostids created for rehostable licenses are bad
hostids created for rehostable licenses are bad on linux and mac (and possibly other platforms, but not Windows). This is fixed in v9.4BL2. Fix affects: client.
P279 - re-activating a rehostable hostid causes problems.
On Windows, re-activating a product with a rehostable hostid causes the existing hostid to be overwritten and the activation count decremented on the server. If there was no remaining activation count, the old license is now invalid. This is fixed in v9.4BL1. Fix affects: client.
P278 - failed (rehost) activation can leave hostid on system
A failed (rehost) activation can leave hostid on system. If an activation for a product with a rehostable hostid fails, the hostid is created and remains on the system. Subsequent activations which should succeed fail with an RLM_EH_REHOST_EXISTS error. Note that this only happens if the failure specifies an activation key which is for this product, but is no longer valid for some reason (ie, all activations are exhausted or the activation key has expired). This is fixed in v9.4BL1. Fix affects: client.
P277 - server lockfile time never gets updated
The server lockfile time never gets updated. This causes tmpwatch on linux to delete it. This is fixed in v9.4BL1. Fix affects: server.
P276 - clients take too long to detect server disconnect
On certain systems, with a 30 second heartbeat interval, rlm_get_atttr_health() returns 0 for many minutes after the server machine is taken off the network. Eventually it returns -20 (RLM_EL_SERVER_DOWN). This has been observed on Linux and Solaris clients. Windows clients do not exhibit this behavior. The fixed client library now correctly returns a -21 error (RLM_EL_NO_HEARTBEAT) 2 passes after the server is disconnected. This is fixed in v9.4BL1. Fix affects: client.
P275 - options spec for multiple ISV instances doesn't work
options spec for multiple ISV instances doesn't work The "options=" option on the ISV line does not work for multiple ISV instances. Only the options= file for the first ISV line will be used. This is fixed in RLM v9.4BL1. Fix affects: server.
P274 - activation fails when Avast virus scanner present
Windows systems using Avast virus scanners cause RLM activation to fail with a "BAD HTTP TRANSACTION" (-134) error. This may be caused by other virus scanners as well. A workaround is to disable the Avast "Web Shield" temporarily. This is fixed in v9.4BL1. Fix affects: client.
P273 - username not processed correctly in rlm_set_environ()
Username is not processed correctly when set in rlm_set_environ(). This happens when one RLM_HANDLE is used and the username is changed from the original name that existed when connected to the server (e.g, in the first rlm_checkout() request), then the username is changed back to the original name. For example, if the original username is "joe" when the application connects to the server, then it is changed to "ted" for the next checkout, then changed back to "joe", the change back to "joe" will not work correctly and the server will process a bad username for the checkout. This same error will happen with hostnames and isv-defined data as well. This is fixed in v9.4BL1. Fix affects: server.
P272 - rlm_act_request() with long hostid list corrupts last
Calling rlm_act_request with a hostid list longer than can be transmitted (RLM_MAX_HOSTID_STRING, or 76 bytes) results in a license file with a hostid list where the last entry is truncated. This most likely results in an invalid hostid.

The new maximum length is RLM_MAX_HOSTID_LIST_STRING (206 bytes), including the "list: " prefix.

This is fixed in v9.4BL1.
Fix affects: client, license generator.

P271 - connect to a down linux server gives wrong error
When an RLM client attempts to connect to a linux license server which is down, the error returned is "write error to network" instead of "connection refused. We are currently evaluating whether this is a problem which we can resolve. If so, a fix is planned for v9.4BL1.
P270 - Roamed, held, minimum_checkout licenses will timeout
ROAMED licenses, held licenses and licenses with minimum checkout times are all timed out by the server (they should not be timed out). When a roamed license is timed out, then expires, it can't be roamed again until the server is restarted. The client receives an RLM_EL_EXPIRED (-3) error and the ISV server logs "DENIED (FILTERED - MAX_ROAM)" This is fixed in v9.4BL1. Fix affects: server
P268 - last LICENSE line not recognized
If a license file contains non-RLM license lines after the last LICENSE, the last LICENSE is not recognized. The workaround is to insert the comment character ('#') at the beginning of the non-RLM lines at the end of the file. This will be fixed in v9.4BL1. Fix affects: client and server
P267 - Windows lock errors with admin users
On Windows, if an admin user checks out a single license and checks it in, then a non-admin user can't check it out. This is due to privs on the lock file. The workaround is to delete the lock file. This will be fixed in v9.4BL1. Fix affects: client and server.
P265 - rlm incorrectly attempts to open C: as a license file
On Windows, if the application is installed in the root of the filesystem (eg c:\), and the app passes argv[0] in the 2nd arg of rlm_init(), and if there are no license files present, RLM thinks that the directory is a license file. rlm_init() returns a -102 error as it should, but it incorrectly attempts to open the directory. Also in this case the license server erroneously reports "c:" as a license file. This is fixed in v9.4BL1. Fix affects: client and server.
P264 - rlm crashes using the web interface to view dbg log
rlm.exe crashes when using the web interface to look at the ISV debug log. We have not been able to reproduce this bug. If you have seen this and can reproduce it, we would like to know the circumstances that create the bug. What was reported is this: [quote:3di2e8en]ISV server has an ISV-defined hostid which takes a relatively long time to compute, and there are 10 instances of it. The crash doesn't happen when the ISV server gets only 1 instance of the hostid.[/quote:3di2e8en] July 30 - We still cannot reproduce this bug, but a second report came in from another customer and we were able to locate the problem in the code. This bug happens only very rarely, and we do not know the situation which causes it. This is fixed in v9.4BL3. Fix requires: rlm
P263 - licenses fail to get checked in w/multiple handles
Licenses do not get checked in when an application exits under the following circumstances:
  • The application uses 3 RLM handles,
  • 1 or more licenses checked out on each handle,
  • let at least a minute pass,
  • exit the application.


If the preceding are all true, the licenses on 1 or 2 of the handles sometimes won't be checked in.

We believe this issue is a TCP/IP networking bug, so we have added heartbeat messages from the server which cause the non-checked-in licenses to be checked in after approximately 20 minutes when this situation occurs. The heartbeats are effective for RLM v9.3 or later clients.

You can avoid this issue entirely by either checking in all licenses before exiting, or by using a single RLM handle for all checkouts.

This issue appears primarily on Windows clients, but has been observed at a much lower failure rate on other platforms.

This is fixed in RLM v9.4BL2.
Fix affects: server, and requires a 9.3 or later client.

P262 - ISV server startup problems on Windows
If the ISV server path on the ISV line specifies a .exe, and a .set is present instead, rlm will not find the .set, and the ISV server will not start. The workaround is to specify the .set file in the license file. This is fixed in v9.4BL1. Fix affects: server.
P260 - rlmreread notes bad checksum with ISV-defiined hostid
rlmreread logs a bad checksum error is there is a license with an ISV-defiined hostid in the license file. This bug is fixed in RLM v9.4. Fix affects: rlmutil In the meantime, the workaround is to remove the _ck= option from the individual license with the ISV-defined hostid.
P259 - rlmtests in Windows end-user bundle doesn't work 9.3
rlmtests in the Windows enduser bundle doesn't work. The license file generated has an ISV line with a path including a .exe at the end, and the bundle includes a .set file but not an .exe. This problem first appeared in the v9.3 end-user kit. This is fixed in the current version of the 9.3 end-user kit.
P258 - UPGRADES can be applied incorrectly.
If an UPGRADE license shares any nodelocked hostid in a hostid list with the license to be upgraded, the upgrade will be performed. The bug is that all hostids should match for the upgrade to be successful. This is fixed in v9.3BL2. Fix affects: client, server.
P252 - ISV line paths are lower-cased
P252 - ISV line paths to ISV servers and options files are lower-cased, causing the files not to be found if uppercase characters are on the paths. This is fixed in v9.3BL2. Fix affects: server.
P251 - Windows: disks with model #s > 32 chars cause crash
P251 - On Windows, disks with model numbers > 32 characters will cause a crash (C0000409 error code). This is fixed in v9.3BL2. Fix affects: client, server, rlmhostid.
P249 - reconnect sometimes consumes too few licenses
P249 - rlm_auto_hb() reconnect sometimes consumes too few licenses. On reconnect (with rlm_auto_hb()), clients will sometimes get a good status even though they have not checked out a new license. This issue only happens with automatic reconnect in rlm_auto_hb(). The sequence which causes this problem is: [list:2ssragdn]- client 1 connects, receives server handle 41 - client 2 connects, receives server handle 81 - server down - client 1 tries reconnect - unsuccessful - server up - client 2 tries reconnect using handle 81 - servers refuses - client 2 tries reconnect without a handle - receives new handle 41 - client 1 tries reconnect using handle 41 (which is the same as client 2's new handle); this succeeds but without using a license[/list:u:2ssragdn] This is fixed in RLM v9.3BL2. Fix affects: client.
P247 - Windows Disk Serial # code generates debug assertions
P247 - the windows disk serial number code will cause a debug assertion when running against the MS debug C library. This doesn't happen on all disks, but it has been reported to happen on some Seagate drives.

This bug affects the client, server, and utilities.

This is fixed in v9.2BL4.

P245 - Activation Pro warnings and quoting errors
P245 - In Activation Pro several forms issue warnings (create/edit product, edit activation key). Also, when editing activation keys, if the extra license parameters are quoted in double-quotes, the parameters don't appear in the edit form. These issues are fixed in v9.2BL2-patch1. A patch file is available on the Reprise website.
P244 - roamed license report expiration for clock windback
P244 - When checking out a roamed license, if clock windback is detected the error is reported as RLM_EL_EXPIRED instead of RLM_EL_WINDBACK. This is fixed in RLM v9.3. Fix affects: client.
P243 - blank line in options file causes crash on reread
P243 - A reread command will crash an isv server if there is an options file with a blank line after a REPORTLOG line. Also, a blank line after any options file line will cause that line to be processed twice. This is fixed in v9.2. Fix requires: server.
P242 - rlmsign crashes with extra double-quotes
P242 - rlmsign crashes if an extra double quote appears at the end of a parameter string, e.g.: [list:bqrjr8r8]customer="My Cust"" [/list:u:bqrjr8r8] The workaround is to remove the extra double quote. This is fixed in v9.2. Fix requires: rlmsign
P241 - rlm_skip_isv_down() skips LF with no ISV line
P241 - If rlm_skip_isv_down() is set, RLM will ignore (skip) license files without an ISV line. A workaround is to put an ISV line into all license files. This is fixed in v9.2. Fix requires: client.
P239 - ISV server matches substrings of usernames in GROUPs
P239 - The ISV server matches substrings of usernames in GROUPs in the ISV options file if the actual username is at the end of the specified string in the GROUP specification.

For example, username "xbobm" in a GROUP matches a checkout from username "bobm", but username "bobmx" would not match.

The same is true for HOST_GROUPS.

This is fixed in RLM v9.2BL1.
Fix requires: server.

P237 - Activation from the rlm web interface fails
P237 - Activation from the rlm web interface fails because it is attempting to encrypt the request, but it doesn't have the correct keys. A workaround is to set the RLM_ACT_NO_ENCRYPT environment variable before running rlm. This bug was introduced in RLM v9.0, when activation requests were first encrypted. This is fixed in RLM v9.1BL4 and v9.2BL1. Fix requires: rlm
P236 - rlmrefresh writes garbage to license files.
P236 - rlmrefresh writes garbage to license files.

This is fixed in RLM v9.2BL1.
Fix requires: new rlmrefresh utility, unique to each ISV.

P235 - web interface status causes rlm to crash
P235 - In the web interface, clicking Status->Server Status->Usage... causes rlm to crash if no licenses are checked out from the pool selected. This has been reported only on x86_w1. This is fixed in RLM v9.2BL1. Fix requires: rlm
P233 - TAP-Win32 Adapter not recognized as undesirable
OpenVPN ethernet adapter name ("TAP-Win32 Adapter") is not recognized as undesirable, and may appear near the beginning of the list of hostids. This will be fixed in v9.1BL4. Fix affects: client, rlmhostid
P230 - reportlog started with rlmswitchr ends
P230 - If a server is started without a reportlog, then rlmswitchr is used to create a reportlog, this reportlog will be closed when a reread command is sent to the server (or at the midnight reread). Then, no reporting will be done. To correct this condition, rlmswitchr will no longer work if the server is not currently writing a report log. If a server has been started without a reportlog and you wish to create one while the server is running, edit the options file to specify one then do a reread on the server. This is fixed in RLM v9.1BL3. Fix requires: server.
P227 - rlm_log()/rlm_dlog() can crash application.
P227 - If rlm_log() or rlm_dlog() is called after a checkout, then that license is checked back in, a subsequent call to rlm_log() or rlm_dlog() can cause the application to crash.

This has only been reported on linux, but the bug could appear on any platform.

This is fixed in RLM v9.1BL3.
Fix requires: client.

P226 - ISV Server crashes on Linux when editing options file
P226 - The ISV Server crashes on Linux when trying to edit an existing options file via the RLM web interface. The workaround is to edit the options file outside the RLM web interface. This is fixed in RLM v9.1BL2. Fix requires: server
P225 - Server can miscount license usage
P225 - The server miscounts licenses if: (a) 2 checkouts request multiple licenses, (b) the 2 checkout requests are eligible for sharing, and (c) the 2nd checkout request can use reservations, but the first cannot. This is fixed in v9.0BL4 and v91.BL2. Fix requires: server. (Note: this problem has not been reported in the field. It was detected with new regression tests at Reprise).
P224 - disable=TerminalServer also disables Remote Desktop
P224 - disable=TerminalServer also disables Remote Desktop sessions. It should not do this, as some ISV want to allow RD without allowing TS. Added a new disable attribute "disable=TerminalServerAllowRD", which if present disables use for the license on a Terminal Server session but not on a Remote Desktop session. This is fixed in v9.1BL2. Fix requires: client.
P223 - invalid "replace" licenses crash server
Licenses with no replace date but with the "replace" attribute can be created with rlmsign. Also, if a license file has 2 licenses of the same name with the REPLACE attribute, and one of them is invalid (ie, it has neither a start date or an issued date), the license server will crash. The server will now disregard invalid replace licenses. (Note: these licenses previously were served). rlmsign will also give an error message and refuse to sign an invalid replace license. This is fixed in RLM v9.0BL4. Fix requires: server, rlmsign, activation generator (+ any custom license generation utility)
P222 - nodelocked, uncounted licenses not served correctly
If a nodelocked-uncounted license is placed in a separate license file without a correct SERVER and ISV line, the license server will not process it correctly. This affects the rlm_enable_server_vm license as well as any other nodelocked, uncounted licenses. The workaround is to place all nodelocked-uncounted licenses in a license file with a SERVER and ISV line. This is fixed in RLM v9.0BL4. Fix requires: server.
P221 - "-dat" switch does not work on reread
P221 - If rlm is started with the -dat switch, the license files with ".dat" extensions are not found when the server rereads the license files at midnight or in response to an rlmreread command. The workaround is to use license files named with a ".lic" extension and not to use the -dat argument to rlm. This is corrected in RLM v9.0BL3. Fix requires: server.
P220 - no hostid in rlc "create license" causes crash
P220 - If a hostid is not specified in the license creation function in rlc or rlmgen, the last step of license creation will cause a segment fault. The workaround is to always specify a hostid. This is corrected in RLM v9.0BL3. Fix requires: rlc/rlmgen.
P217 - Shared license which is roamed uses too many licenses
P217 - If shared license is roamed multiple times (resulting in a single license use), when the server restarts, the licenses are no longer shared and consume more licenses than they should.

This problem will only occur if the sharing specification does NOT include the host ("h") specification, or if the local roam file is deleted between license checkouts.

So, for example, if you share based on user and roam 2 licenses to different hosts, this problem will appear.

This is corrected in RLM v9.0BL2.
Fix requires: server.

P215 - rlm reports incorrect license files after reread
P215 - After a reread, the rlm web interface shows an incorrect list of license files if the license file names have changed. This is corrected in RLM v9.0BL2. Fix requires: rlm
P214 - quoted strings on ISV line fail on windows
ISV lines in the old (pre-v9) format with embedded spaces will not work properly on Windows. To work around this, use the new keyword=value parameters on the ISV line. For example, the line: ISV isvname "c:\a\b c" will work, but ISV isvname "c:\a\b c" "c:\a\opt file" will not work. Instead of the second line, use a line of the form: ISV isvname binary="c:\a\b c" options="c:\a\opt file" you can also add the port=port# parameter to the line as well. See the new documentation on the ISV line format. This bug was introduced in v9.0BL1 (beta), and is fixed in v9.0BL2 Fix requires: server and rlmsign (any license generator).
P213 - detached demo failure for ISVs with 'y' in name
P213 - The fix for P185 did not correct detached demo file names when the ISV name contains a 'y' character (the resulting detached demo file names contain the '|' character, which is illegal on some windows systems). This has been corrected in RLM v9.0BL1. Fix requires: client
P208 - rlm_log()/rlm_dlog() cause nodelock checkouts to fail
P208 - If rlm_log() or rlm_dlog() is called before the first rlm_checkout() request is made, the client does not transmit its list of hostids to the server, and any nodelocked checkout which uses a license on the license server will fail.

This is fixed in rlm v9.0BL1.
Fix requires: client.

P207 - nodelocked licenses do not share correctly
P207 - If 2 or more sharable nodelocked licenses are present in the same license file, sharing will only work on the machine whose license is the last license listed in the license file. This bug was introduced in v8.0 with the optimized sharing capability. This is fixed in rlm v9.0BL1. Fix requires: server.
P206 - systems without networking can cause infinite loop
P206 - The rlmhostid command (and application code that attempts to retrieve the hostid) can go into an infinite loop on certain systems which return the loopback address (127.0.0.1) in their network lookup code. This has only been reported on the WINE windows emulator on linux systems; not on any native systems. This is fixed in rlm v9.0BL1. Fix requires: client.
P204 - problems with CaSe of usernames in named user list
P204 - All of RLM treats usernames as case-insensitive (in fact, usernames are converted to all lowercase in the license server), however the named-user list processing in the server treated usernames as case-sensitive. This means that if a user is added to the named user list with incorrect case ("Joe" rather than "joe"), a checkout request from "joe" will fail. Also, if the user "Joe" is removed from the list, the user "joe" will still not be allowed to checkout the product until the # of minutes has passed until user "Joe" can be re-added to the list. This is fixed in rlm v9.0BL1. Fix requires: server.
P203 - rlm_get_attr_health() fails on detached demo license
P203 - After checking out a detached demo license, the rlm_license_stat() call will work correctly, however the rlm_get_attr_health() call will return -1 instead of 0. This is fixed in rlm v9.0BL1. Fix requires: client.
P202 - RLM web interface subject to cross-site scripting
P202 - The RLM web interface is subject to cross-site scripting attacks. This is fixed in rlm v9.0BL1. Fix requires: rlm.
P201 - ISV rotate option without report log causes crash
P201 - If an ISV option to rotate a report log is present in the ISV options file, but there is no report log specified, then the ISV server will crash when the time to rotate the report log arrives. The workaround is to always specify a report log if you are specifying a rotate option. This is fixed in rlm v9.0BL1. Fix requires: server.
P199 - mixing INCLUDE and INCLUDEALL leads to denials
P199 - If both INCLUDE and INCLUDEALL end-user options are specified, any user/host who is not on both lists will not be allowed to use the product (or in the case of rlm, the capability, such as status, reread, etc). This is true for both RLM and ISV options. This is fixed in rlm v8.0BL6. Fix requires: server. The workaround is to not use both INCLUDE and INCLUDEALL in the same options file, or, if this is required, any user on an INCLUDE line will need to be listed on an INCLUDEALL line as well.
P197 - rlm reports the same server down many times
P197 - If rlm processes license files which have bad path information for an ISV server, the rlm web interface will report that this server is down once for every license file which has a bad path, until it encounters a license file with a good path. This is fixed in rlm v8.0BL4. Fix requires: rlm
P196 - rlmutil fails on Windows with "/" instead of "\"
P196 - On Windows if rlmutil is invoked with a forward slash instead of a backslash separating the last two path components, rlmutil will fail. This is fixed in rlm v8.0BL4. Fix requires: rlmutil
P194 - Windows installer problems
P194 - In the Windows installers for rlm and rlm embedded, if a bad path was specified for the key pair files no error message was given and the installer went on without copying the key pair. The installers now print an error message in this situation. This is fixed in rlm v8.0BL4. Fix requires: N/A
P193 - RLM server diagnostics causes an infinite loop
P193 - RLM server diagnostics can cause an infinite loop writing to the logfile. We have only seen this problem on Windows systems. If the rlm server is started with a -dlog specification (this happens when running rlm as a service on Windows), then the diagnostics command is run from the web interface specifying an invalid output file, the log file will be written in an infinite loop. The workaround is to always specify a valid output file name. This is fixed in rlm v8.0BL4. Fix requires: rlm.
P192 - roam with ISV-defined hostids sometimes causes crash
P192 - If the total length of all hostids in an application exceeds approximately 200 bytes when the application attempts to check out a roaming license, the application may crash. This will usually only happen if the application has more than about 100 bytes of ISV-defined hostids. This is fixed in rlm v8.0BL4. Fix requires: client.
P191 - rlmanon produces an empty output file.
P191 - The rlmanon utility produces an empty output file. This is fixed in rlm v8.0BL4. Fix requires: rlmanon.
P190 - IP addresses reported by RLM are incorrect.
P190 - IP addresses reported by RLM are incorrect on several platforms. (they are reported in reverse order). This means that previous licenses created for these hostids will no longer work and new licenses created for these hostids will not work in the future. The affected platforms are all PPC and Sparc-based platforms: [list:1ose79k1] sun_s1 sun64_s1 ibm_a1 ibm64_a1 ppc_l1 ppc64_l1 ppc_m1[/list:u:1ose79k1] This problem was introduced in RLM v8.0 and is corrected in RLM v8.0BL4. Fix requires: client and server (and utilities).
P189 - Report Log does not get last AUTH record
P189 - If an ISV options file specifies a report log when the server is started, then the report log specification is removed from the options file and the server processes a reread request, the original report log will not have its final AUTH record appended. This is corrected in RLM v8.0BL4. Fix requires: server.
P188 - RLM_PROJECT environment not processed correctly
P188 - the RLM_PROJECT environment is passed to the server using it's original case (upper/lower), however, the server options which use project compare the client's project to a lowercase version of the project string. Therefore, any RLM_PROJECT setting with uppercase letters will not be processed correctly by the server for its options. Beginning in RLM v8.0BL4, the case of the project variable will be preserved, but the comparison will be done in a case-insensitive manner. This is corrected in RLM v8.0BL4. Fix requires: server.
P186 - failover licenses can cause server crash
P186 - A thread synchronization error can cause a server to crash when failover servers are enabled. This has never been reported in the field; it was found in internal testing at Reprise. This has been corrected in RLM v8.0BL3. Fix requires: server
P185 - detached demo creation sometimes fails on Windows
P185 - Detached demo files sometimes contain the '|' character, which is illegal on some windows systems. This is a rare case which only occurs if there is a 'y' in the ISV name or a '{' in the product name. This has been corrected in RLM v8.0BL3. Fix requires: client
P184 - Roamed compound token-based license failure.
P184 - Roamed compound token-based license failure. If a compound token-based license (one with multiple primary licenses) is roamed, and the license server is not restarted before the roamed license is returned, then only the first primary license is returned. Note that all the primary licenses are returned correctly if the license server is re-started between the time the roamed license is checked out and the time it is returned. In other words, this bug only appears if the server remains up between the time of checkout and return of the roamed license. This bug was introduced with the fix for P158 in RLM v7.0BL4. This has been corrected in RLM v8.0BL3. Fix requires: server
P183 - Options for the rlm web interface sometimes fail
P183 - Options for the rlm web interface (include, exclude, etc) based on hostname sometimes do not work on Windows. This happens when the hostname is mapped by DNS (ie, not in a local hosts file) - in this case, Windows returns the hostname in all uppercase. This has been corrected in RLM v8.0BL2. Fix requires: rlm
P182 - problems with restrictions on shutdown/reread
P182 - rlm restrictions on shutdown and reread apply correctly to the rlm server itself, however, a user who is not allowed to perform these operations can shut down or reread an ISV server. This is fixed in v8.0BL2. Fix requires: rlm
P181 - End-user rlm options based on IP addresses fail
P181 - End-user rlm options based on IP addresses sometimes do not work. This will be the case whenever a system has multiple IP addresses, and an option based on an IP address which is not the IP address used to communicate with the license server is used. This is fixed in v8.0BL2. Fix requires: rlm and rlm utilities.
P179 - license file parser crashes
P179 - When parsing a LICENSE line containing "<keyword>=<value>", and the <value> portion is required but missing, RLM will crash. For example, "hostid=" (value required) will cause the crash, whereas "replace=" (value not required) will not. The workaround (prior to v8.0BL2) is to supply the missing value. This is fixed in v8.0BL2. Fix requires: client and server.
P178 - RLM does not always retrieve every IP address
P178 - RLM does not always retrieve every IP address for a computer. On some systems the calls RLM uses to retrieve IP addresses fail to return all the system's IP addresses. (P151 fixed some systems where the hostname is configured on the loopback address (127.0.0.1), but the fix did not work on all Unix systems.) RLM will now scan all the interfaces and report the IP address of each interface, but not the loopback interface. This is fixed in v8.0BL2. Fix requires: client and server.
P177 - licenses nodelocked to sn= or string= can't be served
P177 - Licenses which are nodelocked to string= or sn= hostid types (in other words, which are not locked to anything) cannot be checked out if they are being served by a license server. These licenses work fine if they are in a local license file. This is fixed in RLM v8.0BL1. Fix requires: server.
P175 - Failures with usernames containing RLM illegal chars
P175 - Licenses with usernames which contain the RLM illegal characters (&, >, <, and ") are not processed correctly. RLM previously converted all usernames to lowercase and spaces in usernames to "_". Now these 4 special characters will be converted to A, G, L, and Q, respectively. This is fixed in RLM v8.0BL1. Fix requires: client, server.
P174 - license strings with embedded " #" sometimes fail
P174 - License files which contain a string with an embedded " #" will, in some cases, not be processed correctly. This is due to the fact that the license parser sometimes splits this string into a line which starts with the "#" character, which is then treated as a comment when the license is read back in. This is fixed in RLM v8.0BL1. Fix requires: client, server.
P173 - reservations for INTERNET ineffective
P173 - Reservations for IP addresses (INTERNET) do not work correctly. These reservations can be used by any user just as if no reservation is present. This is fixed in RLM v8.0BL1. Fix requires: server.
P172 - Compound token-based licenses do not share correctly.
P172 - Compound token-based licenses which contain both an unshared license as well as a shared license do not operate correctly. Specifically, license sharing does not work on the shared license. This is fixed in RLM v8.0BL1. Fix requires: server.
P171 - rlm crash while writing license file from activation
P171 - rlm will crash while writing the license file from an activation (using the web interface). The conditions under which this happens are unknown, and it has been reported on Windows only. This is fixed in RLM v8.0BL1. Fix requires: rlm.
P169 - rlm overwrites debug log even with "+"
P169 - If rlm is started with the "-dlog +debug_log" option, the file "debug_log" is overwritten rather than appended. This is fixed in RLM v8.0BL1. Fix requires: rlm.

Support home

Resources for software publishers and license administrators

Email tech support

Send us your questions or requests for technical assistance.

Reprise on Twitter

Follow Reprise on Twitter for news of bug fixes, product releases, and more.

Reprise Blog

Stay current on all topics related to license management

Webinars

Sign up for a live demo of RLM or Activation Pro

Supported platforms

  • Linux x86 (64-bit, 32-bit)
  • Windows XP, Vista, 7, 8, 10 (64-bit, 32-bit)
  • Windows Server 2003, 2008, 2012 (64-bit, 32-bit)
  • Windows 2000 (32-bit)
  • Mac OS X x86 (64-bit, 32-bit)
  • Mac OS X PPC (32-bit)
  • Solaris x86 (64-bit, 32-bit)
  • Solaris Sparc (64-bit, 32-bit)
  • IBM AIX RS/6000 (64-bit, 32-bit)
  • HP-UX PA-Risc (64-bit, 32-bit)
  • NetBSD x86 (32-bit)
  • Java (Mac, Unix, Windows)
  • ARM9
  • Intel Xeon Pi