Hexagon Geospatial
MENU

Licensing Knowledge Base

Easily license Hexagon Geospatial desktop products using the License Manager .
Showing results for 
Search instead for 
Do you mean 

Licensing Log Files

by psmith on ‎04-23-2019 10:57 AM (368 Views)

Licensing problems may occur on the system hosting the Licensing Service (Licensing Server) or on the system where the application is installed (Client System). The licensing diagnostic files available on the Licensing Server and the Client System are described below.

 

Diagnostic Files From The Licensing Server:

If your client application that uses a concurrent (CC) type license does not start due to a licensing error, or if you are experiencing problems with your licensing service then the following files from the Licensing Server can be useful in diagnosing the problem:

 

Licensing Service Log File

The IntergraphLicensingService.log is automatically created in the C:\Users\Public\Intergraph\Licenses folder. The IntergraphLicensingService.log file provides information on the status of the service, the ports and licenses used, and the features (products) hosted by the service.

 

Licensing Server License Files

License (.lic) files from the C:\Users\Public\Intergraph\Licenses\Server folder can provide details concerning the hosting method and user defined ports (if any).  Geospatial Licensing 2018 creates the Server folder when the service starts successfully; if the folder does not exist, the service may have failed to start properly.

 

Detecting Other License Services

In some cases, a Licensing Service may be in error or fail to start properly when there is an existing Flexera (FlexNet) based service on the system that is already using TCP PORT 27000.  To detect other named licensing services that might be running on the system, navigate to C:\Program Files (x86)\Hexagon\Geospatial Licensing 2018\program\ folder, then double-click on LMtools.exe.  If there are multiple services listed (other than Intergraph Licensing Service), the license file(s) used by the service may need to be edited to define a specific server port that does not conflict with the existing services.

 

LicErr.txt Logging

While normally used for logging licensing events on client systems, the LicErr.txt file can also provide useful information about products hosted on the licsense server such as the product name, version, and expiration dates.  The LicErr.txt file will only be populated when the License Service is starting or attempting to start.

  1. Create a blank text file named LicErr.txt.
  2. Place the LicErr.txt file in the C:\Temp folder.

Note: You may have to create the C:\Temp folder if it does not exist.

  1. Use Licensing Administrator and attempt to start the Licensing Service.  If the Licensing Service is already running, you will need to use Server > Stop Licensing Service followed by Server > Start Licensing Service.
  2. Once the license error occurs, move the LicErr.txt from the C:\Temp folder to prevent additional logging.

Diagnostic Licensing Files from The Client

If your client application uses a concurrent (CC) or a nodelocked (NL) type license does not start due to a licensing issue, then the following procedures can be helpful to diagnose issues.

 

Client Side LicErr.txt Logging

On the client system, the LicErr.txt file can help provide insight as to the sources of licenses and any errors that might occur when the license is requested.

  1. Create a blank text file named LicErr.txt.
  2. Place the LicErr.txt file in the C:\Temp folder.

Note: You may have to create the C:\Temp folder if it does not exist.

  1. Attempt to start the application one time.
  2. Once the license error occurs, move the LicErr.txt from the C:\Temp folder to prevent additional logging.
Contributors