General Troubleshooting Hints

This list provides some general debugging information:

•

When you start the license server 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 version 4.1 or later (version 5 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 system is your license server running on?

•

What version of the operating system?

•

What system and operating system is the application running on?

•

What version of FlexNet Publisher does the FlexEnabled application use?

Use the lmver script, or, on UNIX, execute the following command on your license server manager, vendor daemon, and application:

strings binary_name | grep Copy

Alternatives are: for lmadmin, use the command lmadmin -version; for lmgrd and the vendor daemon use the -v argument, for example lmgrd -v.

•

What error or warning messages appear in the log file?

•

Did the server start correctly? Look for a message such as:

server xyz started for: feature1 feature2.

•

What is the output from running lmstat -a?

•

Are you running other FlexEnabled products?

•

Are you using a combined license file or separate license files?

•

Are you using three-server redundancy (i.e. there are multiple SERVER lines in your license file)?