Hexagon Geospatial

Licensing Knowledge Base

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

License File Not Found – common reasons and solutions (2013 to 2016 version products)

by ParthaR. on ‎03-06-2016 08:20 PM - edited on ‎12-20-2018 12:59 PM by Moderator (15,645 Views)


License File Not Found – common reasons and solutions (2013 to 2016 version products)



There are many reasons why a license file is not found when you initialize the product:

  1. If you have a nodelocked license and you are attempting to access the product using remote access, the license will fail. Nodelocked server products do allow for remote access, but they are the only nodelocked licenses that can be accessed remotely. Concurrent licenses do allow for remote access.

    Log on to the system locally and the license should be recognized or exchange the nodelock license for a concurrent license. Please note there is a price difference between a nodelock and concurrent license and you will need a quote from your sales rep for the exchange.
  2. If you are running a concurrent license, does your client machine have access to the machine acting as the license manager service?

    Ensure the client machine has access and can communicate with the license manager services machine. 
  3. For nodelock licenses, does the Host ID of the machine match the Host ID in the license file? You can open the license file in Notepad and find the phrase HOSTID= and then check that Host ID against the machine’s Host ID. If the Host ID does not match, you will need to rehost the license.

    You may do this online once every 6 months per license. Please go to licensing.hexagonsafetyinfrastructure.com/flexnet/operationsportal to re-host your license.
  4. Does your license file end in an extension other than “.lic”?

    Rename the license file so the extension is .lic
  5. Is your license file placed in the proper location for a nodelock license; if a concurrent license, does the client machine point to the correct license manager services machine?

    Nodelock – move the license file to the correct location. All current versions of the software have the licenses located in the \Program Files\Common Files\Intergraph\Ingr_Licenses folder. If you have an older version of the FLEX enforced licensed product, please refer to the README for the license file location. Concurrent – Ensure the client machine either has a registry entry to point to the license manager service machine or has a copy of the license file. 
  6. Check to ensure the system date is correct on the computer. The license expects the correct date. Has the system date ever been modified? If so, then you may have files that have dates greater than today’s date. 
  7. Does the user of the product have appropriate permissions on the license file folder?

    Check the permissions on the license file folder. The user must be able to read this license file.
  8.  If you are still receiving the License File Not Found message, check to see if the environment variable 'LM_LICENSE_FILE' exists and if so what value is assigned to it. Since many other products use FLEX enabled licensing, the variable may exist and be set to another license file path. In that case the Intergraph .lic file will be ignored unless the path to the product license is added.

    Solution: Intergraph’s implementation of FLEX enforced licensing utilizes an environment variable to determine the location of the license files. These variables can be set and controlled in two ways:
    • The Registry
    • System Environment Variables

    Normally the registry is used, and the following key determines the location of the license files:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\FLEXlm License Manager

    Under this key is the following registry variable:


    By default, this value is set to:

    C:\Program Files\Common Files\Intergraph\Ingr_Licenses

    Other paths can be appended to this variable using a semicolon as a separator. For example, if you have had a previous version of GeoMedia Professional loaded on drive D and you upgraded to the current version, both the existing path and the new default path would appear in the registry, as shown below:

    C:\Program Files\Common Files\Intergraph\Ingr_Licenses;
    D:\Program Files\GeoMedia Professional\Program

    Your existing license would still work, as would any subsequent licenses moved to the common folder.  The order of the path list in the registry determines the order used to search for valid licenses. This is most useful if you are mixing node locked and concurrent licenses on the same system. In this case, some applications will attempt to check out a license from the license server even if it is intended to be node locked. By placing the path of the node locked licenses ahead of the concurrent license path, you can ensure that the node locked license is read first.  

    For example, if you are using a node locked version of SMMS and a concurrent license for GeoMedia, you could set the following in the registry:

    D:\Program Files\SMMS\ ;
    C:\Program Files\Common Files\Intergraph\Ingr_Licenses

    You can also use the INGR_LICENSE_FILE as a system environment variable. In this case, both the environment and the registry are used, with the environment used first, and the registry appended to the path.

    A global license file variable called LM_LECENSE_FILE can also be used, but it will affect all FLEXlm based applications. Avoid using this variable if possible. If this variable is set, it takes precedence over the vendor-specific variable.  

    Shown below is an example of the variable setting with the path to GM Professional appended.

    LM_LICENSE_FILE = d:\LaserScan\Data\lic\license.dat;C:\Program Files\GeoMedia Professional\Program\GeoMedia_Professional.lic  

    You would need to add the correct product license file name for the product you are running when receiving the ‘License file not found’ error.  

    If the LM_LICENSE_FILE variable does not exist you will want to use 'regedit' to check for the existence of a 'HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager' registry entry and verify what value is assigned to it. It is possible that this entry exists if you were previously trying to implement concurrent licensing and the LMTOOLS.exe was used with the 'Add Vendor Path' option from the Utilities tab. If the registry entry exists and is pointing to something other than the correct license file path (e.g. C:\Program Files\GeoMedia Objects \Program\GeoMedia _Objects.lic) then the product will not find its license when initialized. If the registry entry exists and is pointing to an invalid path for the GeoMedia or G/Technology product, try deleting the entry to see if this resolves the problem.

    If the above suggestions fail to resolve the problem you can diagnose the problem further using the steps below:

    1) Run the 'lmtools.exe' that is included on the product CD in the 'licensing' folder.

    2) Once the dialog is displayed select the 'Service/License File' tab.

    3) If you have a nodelock license choose the 'Configuration using License File' radio button and browse for the 'GeoMedia_xxx.lic' file in the :\\Program Files\GeoMedia xxx\Program' folder where xxx denotes the specific product. If you have a concurrent license please point it to the location of your concurrent license file that may or may not be the product folder.

    4) Now select the 'Server Diags' tab and click on the 'Perform Diagnostics' button. This will generate a report in the dialog window that you can review for problems. 

    5) You should also select the 'Utilities' tab and use the 'Perform Check Sum' option to verify that the license file will pass the checksum test. The license file should pass this test unless it has been edited.

    6) From this same tab you can select the 'List All Vendor Paths' button to see what registry entries are set. For a node locked license the only entry expected would be C:\flexlm\license.dat under Other Vendors. If there are additional Vendors listed they may be the source of the problem (the earlier registry check should have found these entries however.)

    7) Lastly go to the 'System Settings' tab and verify that the information there checks out, especially the System time as the machine may think the license has expired or is not yet valid if the system time is wrong.