You can address licensing issues, such as the loss of licenses, by specifying that error messages from the License Server are written to a log file. You would use this capability when reporting licensing issues to your Customer Support Representative, who will assist you with setting the license logging level. Your Customer Support Representative will read the messages in this log file to assist with troubleshooting license issues.
To turn on error logging and specify the amount of information saved to a log file, you would set a License Server environment variable called MI_LOGLEVEL to a value of 1 to 3. Setting a value of zero (0) disables error logging. By default, the License Server logging level is set to one (1), which logs error messages for some specific situations and if there is a deletion of invalid licenses.
Logging Level | Action |
---|---|
0 |
Disables logging. |
1 |
Logs short error messages and error codes, and logs if there is a deletion of invalid licenses. This is the default setting. |
2 |
Logs detailed error messages and error codes, logs if there is a deletion of invalid licenses, and logs additional diagnostic messages. |
3 |
Logs everything that level 2 logs with additional information. This level is only useful for client applications like MapInfo Pro that use borrowable or distributable licenses. |
The License Server writes log entries to a file called PBLicense.log in the Windows %temp% folder on the machine where the License Server is running. MapInfo Pro creates the same log file to the same location. The %temp% folder is set by default to:
C:\Users\<username>\AppData\Local\Temp
When reporting a licensing issue to your Precisely Technical Support representative, you will send this log file along with the details of your issue.
If the log file reaches the maximum size limit (of approximately 1MB), then it is renamed to PBLicenseLog.bak, and the new log entries are written in the new PBLicense.log file.
To set the logging level:
If the License Server is running, then stop it and restart it to apply the new system variable and start logging messages. If MapInfo Pro is running, then you must also restart it.