HP Remote Graphics Software Licensing Guide

A Supplemental licensing information
This appendix provides supplemental information on the RGS licensing, and is provided to help
troubleshoot any licensing problems.
Viewing the RGS Version Date
As described in Release Version Date on page 4, the Version Date embedded in the RGS Sender is
used by the RGS licensing mechanism. To view the RGS Sender Version Date, perform the following
steps:
1. The Version Date is logged in the RGS Sender log file (default log file is rg.log). To set up
Sender logging, see Section “Sender logging” in the HP Remote Graphics Software User Guide,
available at
http://www.hp.com/support/rgs_manuals. The logging level should be set to INFO-
level logging.
2. The Version Date is generated in the log file line containing the phrase “License Version Date”. For
RGS 5.3.0, the Version Date log file line is:
INFO - # License Version Date: 2009.0904
RGS Sender log
To help debug licensing problems, the RGS Sender logs licensing failures to the Sender log file,
rg.log. For information on this log file, please see the section “Sender logging” in the RGS User
Guide. If RGS Sender licensing (either local or floating) fails, an entry containing the string “FlexLM”
will be added to the Sender log file. The remainder of the entry will indicate the search path used by
the RGS Sender in trying to access the RGS license. For local licenses, the search path entry will be the
License Key file location searched by the RGS Sender (as described in
Installing the local License Key
file on page 14). For floating licenses, the search path entry will be the portnumber/hostname used by
the RGS Sender in an attempt to contact the license server (as described in
Accessing the RGS floating
license on page 26).
Note, however, in both cases, the rg.log entry does not identify the specific cause of a licensing
failure. For local licenses, failure to find the RGS License Key file is not differentiated from an RGS
License Key file that is found but contains an invalid license. Likewise, for floating licenses, failure to
contact the license server is not differentiated from a license server that is contacted but has an invalid
RGS license.
30 Appendix A Supplemental licensing information