Frequently Asked Questions

This chapter serves as a supplement to the troubleshooting section, focusing on frequent customer problems.

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.

What Toolchain version is my license valid for?

In your license file you will find information regarding what toolchain your license is valid for.

LICENSE hightec-rt tricore-gcc 2024.01 permanent 1 share=uh
client_cache=300 max_roam=30 max_roam_count=1 start=10-mar-2023
platforms="x64_w x86_w" contract=SEN15xxx replace options=ver=4.9.x

In this example, you can see that your license gives you access to:

  • The input "tricore-gcc", indicates toolchain,

  • Proceeding date, indicates that the license is valid for builds until 2024.01,

  • The input "permanent" indicates that there are no expiry date for the license,

  • The input "platforms", indicates that the license is valid only for Windows machines,

  • The input "replace options", indicates that versions of the toolchain up until 4.9.x are valid. That is, it is possible to use v4.6.x, v4.8.x, v4.9.4.x etc., with this license.

For more information about license files, you can visit the page HighTec License Files with more examples.

Which parts of the license file can I modify?

If you have a license file that looks like this:

#License server information
HOST ThinkPad-x 28dxxxxxxxxx 5053
ISV hightec-rt port=6004

You can modify certain parts without the need for HighTec to validate this change. Under the HOST-line, you can modify the license file according to the following table:

Field Example Changeable

hostname

ThinkPad x

yes

port number

5053

yes

host id

28dxxx

no

ISV line

hightec-rt port=6004

not recommended

For additional information you can visit the relevant section of Reprise’s documentation.

How to check the value of RLM_LICENSE environment variable?

To access the license that you purchased, you need to set up the RLM_LICENSE (system) environment variable and point it to your license file or license server. If something is wrong with your license, a wrongly set variable could easily be the cause of the error. To check the actual value of the variable, in a terminal type:

On Windows & Command Promt:

echo %RLM_LICENSE%

On Windows & PowerShell:

$env:RLM_LICENSE

On Unix systems:

echo $RLM_LICENSE

How do I upgrade the RLM license server?

For upgrading, you need to replace the old license manager package with the new one. To set it up again, follow the same instructions that can be found under the Floating Licenses installation instructions.

Some of my identifiers have changed - what can I do?

There are some cases (like moving the license server), when the identifier of the host is changing, like: * MAC address * IP/DNS address * Host name

Host name and IP/DNS address are changeable like it is mentioned above, but the MAC address is not. In cases your MAC address has changed, your license file needs to be re-hosted. For this, please contact our sales team at sales@hightec-rt.com with the new license details. They will regenerate your license file what you can use.

I don’t have enough license - what are my options?

If you do not have enough licenses for what you need, please consider extending the license with more seats and contact the sales team at sales@hightec-rt.com.

Checkout during compile is failing

If you encounter a temporary "License not available" problem (1 run fails from multiple), you can use:

  • in case of gcc based toolchains the -flicense-retries=<n> compilation option to retry license acquisition, where 'n' defines the number of retries from 1..99. This means you can wait at max 100 seconds.

  • in case of llvm based toolchains the HTC_QUEUE_RETRIES environment variable to set the number of retries.

License Monitoring Tools

The RLM web-interface offers tools to monitor your licenses. It can be accessed by typing your https://<host_name>:<port_number> in a web browser.

You can also run the RLM monitoring tools via the command line. Open a terminal in the directory containing the rlmutil executable and make sure your RLM_LICENSE variable points to your license server, then call "rlmutil.exe" to get a list of possible options. For more details, see https://docs.reprisesoftware.com/docs/admin/license-admin-tools.html

Change password for RLM

After installing and setting up the RLM, you can already launch it, but it is possible that with the default settings you can only use the server with restrictions (like can not generate diagnostics, server will run only for 10 minutes before shutting down, etc.).

However the access control and the password setup for RLM differs between versions, so it is highly recommended to make the necessary adjustments for your version, based on the User Guide of Reprise in the beginning.

RLM web-interface does not show buttons

This usually occurs because of a firewall or anti-virus software. It’s difficult to pinpoint, but if you open the developer window in the browser and check the Console tab, you may be able to see the error that is causing the problem. You may try and see if any of these options works out.

-Open the page in a private or incognito browser, and make sure that all add-ons are disabled
-Disable content filtering from your antivirus software. Note that this could be due to a local running antivirus or a network antivirus. You may need to involve your IT department for assistance.
-Exclude the server IP address in the protocol filtering of your antivirus software.
-Check your antivirus or firewall settings to make sure that the machine running the license server is allowed through the filtering.

ISV File Problems With Linux

The ISV name of HighTec is "hightec-rt". The environment variable HIGHTEC-RT_LICENSE (Windows) and hightec-rt_license (Linux - case sensitive) have precedence over the environment variable RLM_LICENSE. Since the dash is not a valid identifier under Linux, if you have trouble, you can try the following.

Try to pass an environment variable with a hyphen to an application using the "env" command (if the Linux distro has the command):
env 'HIGHTEC-RT_LICENSE=port@host' application

Command make -j

This command does NOT limit the number of parallel builds. This can lead to problems, e.g., high load on file I/O, CPU, and license errors.

This problem can be fixed by changing the command to:
make -j %NUMBER_OF_PROCESSORS%
By this change, the parallel build is limited to the available number of cores on the corresponding build machine.
Note: The number of processors must be limited to the physical number of processors.