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.
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:
lmutillmstat -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:
rlmutilrlmstat -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.
Failure to import log file
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 orphaned checkin.)
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.