If you have any problems installing or running the Usage Monitor, review the log file, described in License Statistics log file, to investigate the cause of the problem.

Troubleshooting for specific issues is covered in the following sections.

Inability to query license server

If the log includes the error, "Unable to query license server machine," you should check for communication errors between the license server and the Usage Monitor. To do this, navigate to the License Statistics directory from a command line and enter one of the following commands, depending on whether you are running the command for an LM-X, FLEXlm/FlexNet, IBM LUM, Sentinel LM/RMS, or RLM license server:

• For an LM-X license server, type the command:
  

  lmxendutil \-licstatxml \[-host

  host -port port]
  where host and port are the host and port appropriate for your license server. The host and port designations are optional. If the host information is omitted, the local host is used; if the port information is omitted, the default port is used.

• For a FLEXlm/FlexNet license server, type the command:
  lmutil

  lmstat \-a \-c \[port\]@

  host
  lmutil lmdiag -n -c

   \[port\]@

  host
  where port and host are the port and host appropriate for your license server. The port designation is optional; if it is omitted, the default port is used.

• For an RLM license server, type the command:
  rlmutil

  rlmstat \-a \-c \[port\]@

  hostwhere port and host are the port and host appropriate for your license server. The port designation is optional; if it is omitted, the default port is used.

• For a Sentinel LM/RMS license server, type the command:
  

  lsmon \[

  host]where host is the host appropriate for your license server. The host designation is optional; if it is omitted, the local host is used.

• For an IBM LUM license server, type the command:
  i4blt -s -lc -k -n host
  i4blt -s -lco -k -n host
  i4blt -ll -k -n host
  where host is the host appropriate for your license server.

If there are errors in the communication between the license server and the Usage Monitor, this command will return information about the errors. Otherwise, the command returns normal statistics information for the indicated license server.

Maximum user count exceeded

The terms of your License Statistics license agreement include limits on the maximum concurrent users that can be monitored. (See Determining usage for License Statistics licensing for more information on how License Statistics counts users.) If you exceed the allowed user count, License Statistics will continue running, but will stop monitoring. The log will indicate that the maximum number of users you can monitor has been exceeded.

If the user count is exceeded on a regular basis, you should either upgrade your license to allow you to monitor more users or reduce the number of applications you are monitoring.

Failure to import log file

When using License Statistics to import data, partial/rotated logs are not supported; if associated checkins/checkouts are not contained in the same log file, the data import may fail. In such cases, you will see an error message such as: "Cannot import log file. Checkin at line 177 references a checkout from an earlier log file. Merge the log files and try again." (Where line 177 is the line that contains the checkin that has no associated checkout contained in the same log file.)

You can try to merge the partial log files into one log file that contains complete checkin/checkout information, as described below.

For Windows, type the following from a command line:

type file1 file2... filen > output.txt

For Linux, type the following in a console:

cat file1 file2... filen > output.txt

where file1 file2... filen are the names of any number of files to be merged and output.txt is the name of the file that will result from the merge.

Inaccurate statistics for HASP license server

HASP server logs often do not contain all the information necessary to obtain accurate statistics. If you notice problems with the data imported from the HASP server logfile, you can see some improvement by configuring the HASP server to add the value OPEN_SESSIONS to the last column in the logfile. However, the usage statistics still will not be 100% accurate, because the HASP logs still lack some usage data even with this value set. 

License Statistics can handle HASP logs with or without the OPEN_SESSIONS value set. However, a single HASP server logfile cannot both include and exclude the OPEN_SESSIONS value, so you must import logfiles that include the OPEN_SESSIONS value separately from logfiles that do not include this value.