1. Invalid License Key Inconsistent Authentication Code

Invalid License Key Inconsistent Authentication Code

The aim of this guide is to make it easier for you to diagnose and solve node-locked licensing problems with the ARM tools. Part 1: Identifying the error messageWe 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: C:armcc -vsnError: C9555E: License checkout for feature compiler5 with version 5.0201508 has been denied by Flex back-end.

Error code: -10Feature has expired.type of errorFeature: compiler5Expire date: 31-oct-2015License path: C:license.datpath to license file(s)FlexNet Licensing error:-10,32error codeFor further information, refer to the FlexNet Licensing documentation, available at 'www.flexerasoftware.com'.Product: DS-5 Professional 5.23.0 5230020Component: ARM Compiler 5.06 update 1 (build 61)Tool: armcc 4d35adThe error message gives a lot of information, but initially we are interested in the Error and 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.Part 2: Common node-locked license errorsPart 3: Further supportIf 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, and your email should include:.

A copy of your license file(s), as installed on the system. The complete text of any error messages. Which tools you are trying to run, for example ARM Compiler 5.06 update 1 installed as part of DS-5 5.23.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 page. Run it on your machine and include its output with your e-mail.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: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:.

Trying to use a feature which is an optional add-on for which you do not have a licenseFor example multi-core debug support in RVD was an optional add-on in RVDS 2.x. Trying to connect to more than one target simultaneously would lead this error message being reported. Corrupted license fileIt is possible that part of your license file has been deleted. In which case you should download a fresh copy of the license from your account on the ARM website ( ).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 and then follow the instructions in: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:. Typing error while registering your serial number.

The hostid of the system has changed (e.g. Due to replacing the Ethernet adapter). Trying to use the license file on a different machineTo correct this, you will need to rehost the license to the correct hostid. How to do this is covered in the following FAQ: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 ARMLMDLICENSEFILE 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: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:Some ARM licenses restrict usage of the tools to specific platforms (e.g. This error message is seen when a platform not authorized by the license is used. For information please see: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: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.