Troubleshooting: Error with Licenser or Licenses

Here, you will find a guide on how to troubleshoot some of the most common license-related problems. If you can’t find what you are looking for, a list of error codes can be found on Reprise’s website, under RLM Status Values as additional help.

If you still have problems, you can contact our support via our support page or at support@hightec-rt.com. In this case, don’t forget to add your Service Entitlement Number (SEN) in the subject of your email.

Error in Licenser

  • Environment variable RLM_LICENSE is not set or contains invalid values.

    Check and add/correct RLM_LICENSE.

  • Licenser can’t be reached because PATH does not contain the licensemanager folder.

    Add licensemanager folder to the PATH environment variable. This folder is by default C:\HighTec\licensemanager.

Licenser Emits: Error With Products Query: No error, Licence Check: No valid license!

There is a mismatch between tool version and product in license file, e.g., FETC is installed but license file is for a commercial version or vice versa.

Make sure that your license file matches your product version. The version that is licensed can be found in the license file; it looks like this: LICENSE hightec-rt tricore-free-gcc. In this case, the "LICENSE" line specifies that this is a license file for tricore-free-gcc, the free entry toolchain.

Port 5053 in Use, Waiting…​

This usually means that the port number specified in your license file is already in use, probably by another RLM licensed product.

You can change your port number in the license file without the need for HighTec to validate this change. For more information, please visit the relevant section of our FAQ.

Cannot Find Hostname In Network Database (comm: -18)

This usually means that the hostname in your license file does not match the hostname in the RLM_LICENSE variable or the hostname of your machine.

The hostname in your license file can be changed without the need for HighTec to validate the change.

License Not Found

  • HighTec recommends using RLM_LICENSE to configure the location of the license. However, in some cases, the vendor specific value is set (e.g., in Makefiles) and this results in a compilation error. From the log, it is not evident that the vendor specific value has been set.

  • RLM supports two environment variables to configure the location of the license: "HIGHTEC-RT_LICENSE", and "RLM_LICENSE".

    Check what environment variable is set and that the path to it is correct. To be able to check out a Floating License seat, the environment variable needs to be directed to the specific hostname and port number of the license server.
    Note: On windows the environment variable "RLM_LICENSE" may be set in system variables instead of user variables. Make sure this setting is correct.

license check: Can’t read license data (-102)No such file or directory (errno: 2)

This error usually means that:

  • no license file (or server) has been specified via RLM_LICENSE,

  • there are no *.lic files in the referenced directory or

  • none of the specified license files are readable.

    As stated in "License Not Found", please check if the RLM_LICENSE (system) environment variable is set correctly to the directory of the license file (in case of node-locked license) or to <host_name>@<port_number> of the running license server (in case of floating license).

Communication error with license server (-17) (rlm stat (-111))

The operating system maintains a queue of connections to a network service, when the service cannot respond fast enough to incoming connection requests. If the queue is full, clients connecting can get this error.

-Use RLM v12.3BL3 on the server
-On the server set/export the environment variable RLM_TCP_LISTEN_BACKLOG and set it to 20
-Restart the RLM server with this configuration.
Note: It’s an environment variable (not an options file directive) that needs to be set on the server side, before invoking RLM.

Can’t use Toolchain V4.6.3.0 but can use Newer Versions

V4.6.3.0 was built with RLM v9.x, which does not understand the "akey" keyword.

Contact support@hightec-rt.com to solve this issue.

License Failure With Many Parallel Builds (> 16)

The operating system maintains a queue of connections to a network service, when the service can’t respond fast enough to incoming connection requests. If the queue is full, clients connecting can get this error.

Set the environment variable RLM_TCP_LISTEN_BACKLOG to 20, and restart the RLM server with this configuration.

Exception in chsize from rlm1233.dll.

This exception comes "out of the blue".

-In C:\ProgramData\Reprise there are two files:
rlminfo.5053
hightec-rtkmeftricore-gcc
-Delete them, and it should work again.