...
To resolve this problem, verify that the license server is responding properly as described above in "Inability to query license server."
Failure to find licenses for FlexNet license server
...
FlexNet vendor names are case-sensitive by default, so you may see the following error if the case is not correctly configured:
[2012/05/10 08:00:00] ERROR: Unable to find any licenses served by the license server!
Check that the vendor name entry in the xflicstat.cfg configuration file for that license server is specified in the correct case. You can verify the correctness of the configuration by querying the status of the server manually:
lmutil.exe lmstat -a -c hostname -S VendorName
Failure to gather data for FlexNet license server hosting multiple vendors
...
If monitoring realtime data on a FlexNet license server fails with the error "This server hosts licenses from multiple vendors," the FlexNet server is not configured correctly in License Statistics.
FlexNet license servers have hosted vendor daemons for each vendor. If all parameters provided to lmutil are correct, the output will include only the license usage for the specified vendor. If the output contains data for vendors other than the specified vendor, one or more lmutil arguments are incorrect. The most common incorrect argument is the port number. The same port cannot be provided for all vendors on one machine. The port used by the specific vendor daemon is configured in the license server's configuration or license. If the port is not set explicitly, the license server can select it automatically from free ports.
To configure the FlexNet server correctly for multiple vendor daemons, specify each as a separate license server in the FLEXNET_SERVER setting in the License Statistics configuration file. For example, if you want to monitor vendor daemons "vendor1" and "vendor2" on "server1" you must use a FLEXNET_SERVER setting for each of them, as follows:
FLEXNET_SERVER = vendor1@port@server1
FLEXNET_SERVER = vendor2@port@server1
Or, for HAL (redundant) servers:
FLEXNET_SERVER = vendor1@port@server1 vendor1@port@server2 vendor1@port@server3
FLEXNET_SERVER = vendor2@port@server1 vendor2@port@server2 vendor2@port@server3
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 run with OPEN_SESSIONS (see configuration below). However, this still does not ensure 100% accuracy, because the HASP logs may 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.
HASP server log configuration syntax
If the log configuration is not correct, you may see a message similar to the following in the License Statistics log, even though the HASP log contained denial data: "NOTICE: File.log has been imported successfully, but was empty (no denials found)." You should verify the configuration of the HASP server log if parsing fails. The HASP log configuration must be one of the following. Other formats are not currently supported.
To run with OPEN_SESSIONS:
| No Format |
|---|
{timestamp} {clientaddr}:{clientport} {clientid} {method} {url} {function}({functionparams}) open_sessions({sessioncount}) {newline} |
...
To run without OPEN_SESSIONS:
| No Format |
|---|
{timestamp} {clientaddr}:{clientport} {clientid} {method} {url} {function}({functionparams}) {newline} |
Incomplete lmdiag output for FlexNet license server
If there is a problem with the output produced by the lmutil lmdiag command, you will see the following message in the log:
"Output of the lmutil lmdiag command is incomplete, which can cause incorrect or incomplete data in License Statistics. Please ensure that your license server is able to correctly print out the lmdiag output."
This error indicates that some or all features included in lmstat output are not described in lmdiag, so License Statistics data may be inaccurate. If a specific feature in the lmstat output does not have any users described and lmdiag does not contain any information about this feature, License Statistics creates the feature as both a floating and node-locked type. In addition, a feature that is not described in lmdiag has no expiration date set.
This error may occur because the vendor's configuration doesn't allow printing out required data. This error may be unresolvable if you are unable to change the license server configuration.
Unidentifiable usernames in lmutil output
License Statistics identifies and displays usernames using data provided by the license server using a query tool (normally lmutil). If the license server does not provide valid usernames, License Statistics cannot use the data to display the username in the log or the web-based UI.
For example, if the lmutil output for CITRIX does not contain valid usernames for specific checkouts, it will use the syntax "string1 (string2)", where string1 is the value of the string stored in place of an actual username and string2 is an additional string to help distinguish users. This data is not recognizable by License Statistics.