License keys

FlexNet^(*) licensing

Get your hostid

Run the following command on your computer:
lmutil lmhostid
The hostid of your computer is returned.

If an internet address is requested:
lmutil lmhostid -internet
The internet address of your computer is returned.

./lmutil: No such file or directory

You can also get for example "./lmutil: /lib64/ld-lsb-x86-64.so.3: bad ELF interpreter: No such file or directory" which is more explicit.

This error message indicates the LSB linker/loader library (ld-lsb) is not found.
It is due to the lack of Linux Standard Base (LSB) compliance on your system. Licensing tool requires LSB compliance version 3 or higher.

In case you do not get the exact name of the missing library, please run "ldd lmutil", get the value of the LSB linker/loader library (for example ld-lsb-x86-64.so.3), and run "ld-lsb-x86-64.so.3". You must get an error message.

There is a workaround to create only the missing LSB linker/loader library (requires root rights):
# ln -s /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3
(assuming /lib64/ld-linux-x86-64.so.2 exists on your platform)

If you want to install the full LSB core (Linux Standard Base core support package):

• RedHat 32bits: yum install redhat-lsb.i686
• RedHat 64bits: yum install redhat-lsb
• Debian: apt-get install lsb-core-package

Multiple hostids are returned

Those multiple hostids correspond to multiple network adapters.
You have to choose among those hostids the hostid of a permanent network adapter, i.e. that won't change. Choosing the hostid of a virtual interface would lead to an invalid license key.

On Windows platform, DOS command ipconfig /all help you for that purpose, showing a detailed description of each network interface.

Hostid for floating licenses

2 computers (can be the same) are involved in this configuration: the client (on which you run the product), and the server (on which you run the license server).

You must get the hostid of the computer hosting the license server and not that of the client workstation.

Test the validity of your license file

Run the following command on your computer:
lmutil lmdiag -c <path_license>/license.dat

The path to the license file, as well as the type of error and an error code if applied, is returned.

The installation wizard is not able to find the license file

Check whether a license.dat file exists in the indicated directory.

On Windows platform, check whether the name of the license file is really license.dat and not license.txt.dat.
In case file extensions for known file types are hidden, you can see that the name of the file is license.dat, but the file type is TXT file, which means the name of the file is in fact license.dat.txt. In order to rename the file, you have to temporarily uncheck this option Folder options > View tab > Hide extensions for known file types box) to rename your license file.
If you are familiar with the usage of MS-DOS command, you can also execute the following command in a Command Tool window: ren license.dat.txt license.dat in the directory which contains the license file.

License manager in floating configuration

The license.dat you have received must be installed on server and client platforms in the appropriate directory.

Additionally, license file on client platforms must be updated as follows:

• in the SERVER line, this_host shall be replaced with the actual name or IP address of the server computer
• TCP/IP port number may be added to SERVER line (for license manager) and/or VENDOR line (for vendor daemon)

Run the following command on your computer:
lmutil lmstat -c <path_license>/license.dat
The status of the license manager is returned.

If the lmgrd process is not running, launch it manually:
lmgrd -c <path_license>/license.dat -z

One of the most common cause of issue with the license manager is the firewall installed on the target platform that prohibits the license manager from communicating with outside.

• on Linux platform, you may need to specify TCP/IP port numbers used by the license manager (lmgrd) and by the Marben product daemon (ATOS) in the license file, and to ensure those ports are opened. Do not let the system choose the port numbers at run-time.
• on Windows platform, you may need to allow lmgrd.exe process from Flexera Software LLC editor and Marben Products daemon ATOS.exe from Marben Products editor to communicate on your network.

Licensing toolkit error codes

The more frequently error codes returned by the licensing toolkit are described below. Click on your error code for more details.

• -1: Cannot find license file

  There is no license.dat file where the product expects to find it.
  Refer to the product "Installation Guide" document for more details about licensing mechanism.

• -8: Invalid (inconsistent) license key

  The license file is corrupted.

  This could be accidental, or because you have edited and changed the license file.
  Only the comment sections of the license file can be edited (those lines starting with a # character). No other part of the license file could be changed.

  However, in floating configuration, license server hostname and port numbers must be updated to reach the license server.

• -9: Invalid host. The hostid of the system does not match the hostid specified in the license file

  The hostid of the computer does not match the hostid included in the license key.

  There are several possible reasons why the hostid might not match:

  • Typing error
  • The hostid of the system has changed
  • The license file is not installed on the computer for which it was intended

• -10: Feature has expired

  The license file is a temporary license, and it has expired.

• -15: Cannot connect to license server system

  The MARBEN License Manager has not been launched as a service.

• -95: Network connect to this_host failed

  This error code indicates the client is not able to connect to the license manager.
  Update the license file on the computer where you launch the product, and replace this_host (in the first line) with the actual system hostname or IP address of the computer where the MARBEN License Manager is installed.

• -103: Terminal server remote client not allowed

  You are running the product in a terminal server environment, which is not supported by your current license file.