|ARM Technical Support Knowledge Articles|
The aim of this guide is to make it easier for you to diagnose and solve node-locked licensing problems with the ARM tools.
We first need to identify what is going wrong. To do this open a command prompt window and execute the command armcc --vsn or armclang --vsn. Depending upon the version, the output of this command should look something like this:
||type of error|
||path to license file(s)|
The error message gives a lot of information, but initially we are interested in the
FlexNet Licensing error fields. Between them these two fields give the type of failure. Another useful field is the
License path, as this tells you where the tools are looking for a license file.
This command may complete successfully, depending upon what is the cause of your problem. In this case you need to record the error message next time you see it.
Once you have the error code and message, move on to part 2.
|Flex error -1: Cannot find license file|
|Flex error -5: No such feature exists|
|Flex error -8: Invalid (inconsistent) license key|
|Flex error -9: Invalid host. The hostid of this system does not match the hostid specified in the license file.|
|Flex error -10: Feature has expired|
|Flex error -21: Application version > License version|
| Flex error -89: This platform not authorized by license
|Flex error -103: Terminal Server remote client not allowed|
|C3397E - Q0555E: No RVI-ME device found on USB|
If the error code you are seeing does not match any of those listed above, or the you have not been able to resolve your issue, contact ARM License Support for further assistance. The e-mail address is firstname.lastname@example.org, and your email should include:
For users of RVDS 2.2 or later, please also run the License Wizard's diagnostic option and include the output with your e-mail.
For users of other tool suites, please download the client diagnostic script from the Licensing Problem Diagnostic Scripts page. Run it on your machine and include its output with your e-mail.
Flex error -1: Cannot find license file
This means that the tools are unable to find a license file. This is normally because you have not yet installed a license file, or the license file has been moved since installation. To rectify, follow the instructions in this FAQ:
Flex error -5: No such feature exists
This error means that a license file was found, but did not contain a license (valid or invalid) for the feature you are trying to use. Typically this will be caused by:
Flex error -8: Invalid (inconsistent) license key
This error message indicates that you have a corrupted license file. This could be accidental, or because you have tried to edit the license file. Only the comment sections of ARM tools licenses can be edited (those lines starting with a
# character). You can not not edit any other part of the file without it becoming invalid.
To fix, download a fresh copy of the license file from your account on the ARM web licensing portal and then follow the instructions in:
Flex error -9: Invalid host. The hostid of this system does not match the hostid specified in the license file.
This error message occurs when the host ID the license has been locked does not match that of the system.
ARM tools licenses are locked to a specific machine using a hostid. For node-locked licenses the hostid can be the disk serial number of the C drive, or the MAC address of an Ethernet adapter. The hostid in the license file must be visible on on your system at all times, otherwise the tools will not work.
There are several possible reasons why the hostid might not match:
To correct this, you will need to rehost the license to the correct hostid. How to do this is covered in the following FAQ:
Flex error -10: Feature has expired
The license file the tools are trying to use is a temporary license, and it has expired. If you have a permanent license file already you will need change the ARMLMD_LICENSE_FILE to point at the permanent license instead. You can do this manually, or by using the License Wizard. See the following FAQ for more information:
Flex error -21: Application version > License version
This means that a license of the right type has been found, but it has a lower version number than is required. For example, trying to run the RVCT 3.0 compiler with a RVCT 2.1 license.
If you have recently upgraded to a newer version of the tools, it is possible that it is still trying to use the old license file. The "License path" section of the error message shows the licenses file(s) the tools are trying to use. Navigate to this file, and check whether it is the correct file for the version of the tools you are using. If it is the incorrect file, run through the instructions in the following FAQ to install the newer license:
Flex error -89: This platform not authorized by license
Some ARM licenses restrict usage of the tools to specific platforms (e.g. Linux). This error message is seen when a platform not authorized by the license is used. For information please see:
Flex error -103: Terminal Server remote client not allowed
ARM tools licenses do not support the use of terminal servers (e.g. ssh) or remote desktopping software (e.g. Microsoft Windows Remote Desktop utility). For more information see the following FAQ:
C3397E - Q0555E: No RVI-ME device found on USB
This message should only be seen when using one of the RVDK packages (e.g. RVDK for Oki, RVDK for ST). The RVDKs require both a valid license file and also the supplied RVI-ME unit to be plugged in before they will operate. This error message shows that a license file was found, but that the RVI-ME is either not plugged in or is not installed correctly.
To fix, check that the RVI-ME is plugged in. If it is, you may need to re-install the driver.
Article last edited on: 2016-02-25 17:19:07
Did you find this article helpful? Yes No
How can we improve this article?