User guide

FLEXnet Licensing End User Guide 119
Troubleshooting Guide C
This appendix documents areas of FLEXnet Licensing that have given customers difficulty in
the past.
General Troubleshooting Hints
The following are tips for debugging:
• When you start the license server (
lmgrd) be sure that you direct the output into a local log
file where you can examine it. The log file often contains useful information. Examine it
when you have a problem, and be prepared to answer questions about it when you talk to a
support person.
• If the license server appears to have started correctly (which you can determine from the
log file), try running
lmstat -a and lmdiag to see if that program has the same problem
as your application.
• If your application is v4.1 or later (v5 or later on Windows), you can use the
FLEXLM_DIAGNOSTICS environment variable. Set FLEXLM_DIAGNOSTICS to 1, 2, or 3.
A setting of 3 gives more information than 2, 2 gives more information than 1 (in particular,
the feature name that was denied). See “FLEXLM_DIAGNOSTICS” for more
information.
• When you talk to a support person, be prepared with answers to the following questions:
- What kind of machine is your license server running on?
- What version of the operating system?
- What machine and operating system is the application running on?
- What version of FLEXnet Licensing does the FLEXenabled application use?
Use the
lmver script, or, on UNIX, execute the following command on your lmgrd,
vendor daemon, and application:
strings binary_name | grep Copy
Alternatively, lmgrd -v gives the lmgrd version, and this works with the vendor
daemon also.
- What error or warning messages appear in the log file?