The TASKING License Management System (TLM) works with TASKING products released during and after 2014. All TASKING toolsets are subject to the terms and conditions of the End-User License Agreement.



This page contains answers to common questions concerning TLM handled by our customer support staff, along with some tips and tricks that we have found useful and presented here as questions.

1. Node-locked license problem in VX-toolset for ARM v5.0 and Power VX-toolset v2.1
It turned out there is a bug in the installation procedure when installing a node-locked license.

The content of the file licopt.txt is generated wrongly for node-locked licenses. Instead of a reference to the TASKING license server like:


there should be a reference to the local license file:

TSK_LICENSE_FILE = licfile.txt

If you got a node-locked license, it may not work right away!!

Edit the file \etc\licopt.txt manually:

1. remove the line: TSK_LICENSE_SERVER = ...
2. add the line: TSK_LICENSE_FILE = licfile.txt

Please notice the key definition in this file should stay present:

TSK_LICENSE_KEY_Product-Code = xxx-yyy-xxx-yyy

2. Do you have any detailed information about TLM? Where can I download the GETCID utility or License Servers?
Please visit TLM's download section for a collection of documentation and tools.

3. Node-locked client based license checkout will fail when the computer ID of your system does not have a constant value
The computer ID is an alphanumeric value that uniquely identifies your computer. Therefore, the computer ID must have a constant value. If the value changes then the association between the node-locked license and your computer is lost, i.e. the license cannot be checked out.

The computer ID is calculated based on the MAC address(es) of the Ethernet adaptors in your computer. MAC addresses of the Ethernet adaptor(s) can change, or become visible or invisible. For example due to, replacement of an Ethernet adaptor card, addition or enabling/disabling of a Wi-Fi interface, tethering via Wi-Fi, inserting a laptop into a docking station, enabling/disabling flight mode, enabling/disabling a VPN client, etcetera. If such an event occurs the checkout of a node locked license can fail. Especially the first release (v1.1) of TLM is sensitive for changes in MAC addresses and enabled/disabled Ethernet interfaces.

So, make sure your system configuration at the moment you obtain(ed) a license is the same as when you use the license. You can verify this by executing the getcid.exe program and check whether the displayed computer ID is equivalent with the computer ID shown in your license file.

4. How do I know the network connection between the client and the license server is not blocked?
Sometimes the connection between the client and license server is blocked by a firewall or anti-virus software. To find out, a telnet session can be used. Please notice a ping is not sufficient, since the ping protocol does not use a port number.

From a DOS box run the following command:

telnet <host> <port>

For example:

telnet 8080

When a connection is established, you get a blank screen. If not, a connection error will show up:

Connecting To not open connection to the host, on port 8080: Connect failed

This may indicate the server and/or port number is blocked by a firewall or other security software, or the server itself is down.

5. License checkout fails due to outdated environment settings
If a license is granted when the tool is started from one environment (e.g. Eclipse) and the license is not granted if the tool is started from another environment (e.g. a DOS Box, a custom Start Menu, Taskbar or File Explorer), this may indicate the variable settings between these environments are different.

When a toolset is successfully installed, new environment settings will be applied. However these settings are not passed yet to applications that were already active before the toolset installation. To get this right you can simply restart the computer.