Common Licensing Problems

Following are solutions to common problems that occur regarding the FLEXnet licensing setup for IC-CAP.

For details on using FLEXnet and lmtools, refer to the Macrovision website at:

http://www.macrovision.com/support/by_catagory/Software_Licensing.shtml

Where to Begin

If you are having trouble getting FLEXnet working, the best place to begin troubleshooting is the flex.log file. The flex.log file is typically located in $ICCAP_ROOT/licenses. Read the flex.log file and look for error or warning messages.

If no relevant errors or warnings are noted in the flex.log file, start IC-CAP in debug mode by setting the following environment variable in a UNIX window, then start IC-CAP:

C Shell (/bin/csh)

setenv HPEESOF_DEBUG_MODE all

Bourne/Korn Shell (/bin/sh, /bin/ksh)

HPEESOF_DEBUG_MODE=all
export HPEESOF_DEBUG_MODE

Look for errors or warnings in the shell where you started IC-CAP.

Common Errors and Solutions

Following are possible solutions to certain license-related error messages that occur.

Inconsistent Encryption Code

This error occurs when the information on the INCREMENT lines in the license.lic file is corrupt or incorrectly formatted. Check the license.lic file for the following:

1	Make sure that each line of the license.lic file is a single continuous line with each field separated by a single space.

2	If there are backslash characters ('\') line wrapping the lines, make sure that the backslash character is the absolute last character on its line. Even a space after the '\' will cause a problem.

3	Try removing the backslash characters and joining the INCREMENT lines, so that each INCREMENT line is a single continuous line with no line wrap.

4

If the license.lic file was transferred from DOS to UNIX, make sure to remove the control M's (^M) at the end of all the lines in the license.lic file. If spaces are added to the end of each line to eliminate the ^M's, the spaces must also be removed. The spaces turn out to be just as disruptive as the ^M's. The best way to remove the ^M's is using the vi editor and the following substitution command:

:1,$ s/.$//g

5	Make sure that none of the original SERVER line hostid information has been changed. Make sure that none of the SERVER lines have been eliminated.

Invalid Host or Unable to Determine Machine ID

This can be caused by one of the following:

1	Make sure that the information on the SERVER line(s) in license.lic is correct.

2

If the licenses are node-locked, and you attempt to run IC-CAP on a machine other than the machine the licenses are node-locked to, you will get a license error indicating invalid host. To check if this is the case, look at the $ICCAP_ROOT/licenses/license.lic file and check the INCREMENT lines. If each INCREMENT line ends in a machine hostid, then the licenses are node-locked to the machine whose id is shown. You can, however, export the display from the node-locked machine to another display.

3	If you are on an HP workstation, check the permissions of the /dev/lan0 file. This file must have read and write permissions for all:

chmod 777 /dev/lan0

The FLEXnet lmgrd and agileesof vendor daemons use this file and must be able to read and write to this device.

Invalid System Clock Time

FLEXnet detects when systems have had their dates set more than 24 hours back, and prevents users from using expired licenses by setting the clock back. It works by looking for any files in "/" or "/etc" that have a date more than 24 hours in the future.

Use the command ls -lat in "/" and "/etc" to find the offending file(s). The date of the offending file(s) can be corrected by using the touch command:

touch <filename>

If the file is a link, the link must be removed and then recreated. If the link itself is dated ok, check the date of the actual file or directory it points to. The pointed to file must also have a valid date.

A Feature is Not Enabled

FLEXnet codewords have both enable and expiration dates. If the codeword enable date is in the future with respect to the current machine date, then this error will occur.

First check the date on the computer. If it is not today's date, correct it. On UNIX systems, the date can be set using the date command:

date mmddhhmm[yy]

For example, to set the date to 23 Sept, 2002 at 13:30, the command would be:

date 0923133002

If this still does not correct the problem, or if the date is correct, then request new codewords with an enable date set to today's date.

Cannot Connect to License Server

If you see a flex.log file with the following errors:

(lmgrd) Started agileesofd

(agileesofd) Vendor daemon can't talk to lmgrd (cannot connect to

license server) port 1700

(lmgrd) Vendor daemon died with status 241

(lmgrd) Since this is an unknown status, lmgrd will

(lmgrd) attempt to re-start the vendor daemon.

(lmgrd) REStarted agileesofd (internet tcp_port xxxx)

Make sure that the lmgrd and agileesofd daemon are the correct version (version 8.2h or higher). The lmgrd daemon should have the same or higher version number as agileesofd. You can check version numbers as follows:

cd $ICCAP_ROOT/licenses
./bin/lmgrd -v
./vendors/agileesofd -v

Make sure that the workstation is connected to a network or that the network connector on the workstation is properly terminated. FLEXnet will not work if the network connection is down or if the network services are not starting properly. Check all physical network connections to make sure that they are okay and look for errors during machine boot up. On HP700 workstations, look at the /etc/rc.log file for errors.

Make sure that the agileesofd is being started successfully by lmgrd. If agileesofd cannot be started from the path specified on the VENDOR line in the license.lic file, this error will occur. Also make sure that the agileesofd file has execute permissions:

cd $ICCAP_ROOT/licenses/vendors
chmod 755 agileesofd

Address Already in Use

The tcp port number specified on the SERVER line in the license.lic file is in use by another process. Try the following: Kill any stranded lmgrd processes. Remove the /usr/tmp/.flexnet/lmgrd.xxxx file that contains the tcp port you want to use. You can remove the entire /usr/tmp/flexnet directory if you are the only one using lmgrd on this machine, then restart lmgrd. If you still have a problem, try using a different tcp port number on the SERVER line in license.lic and then restart lmgrd.

Here is an example of properly configured SERVER lines:

SERVER joshua 2072EFE45 1705

SERVER isaiah 20472A3D3 1705

SERVER jonah 2052C6416 1705