Why can't STK client find a network license from the license server?


QuestionWhy can't STK client find a network license from the license server?

You attempt to start STK and it says no license found but you think you should be getting a network license.    
To troubleshoot this issue from the client side, perform the following checks and report your findings to the IT person in charge of the AGI/STK Network License Server software.

  1. Verify that you are pointing to a network license server. Normally, this is done via a client-side license file. The default location for this file is C:\ProgramData\AGI\LicenseData, and the file name generally contains the keyword ‘client’. Open this file using your favorite text editor, and make note of the server line. This line contains the following information:

    SERVER {HostName or IPAddress} {MAC address or “ANY”} {optional TCP/IP value}

    User-added image
    If you do not have a client file, you may be using an environment variable – STKD_LICENSE_FILE. This is not common. If you are using this, the value may be a file path, or a value represented as {optional TCP/IP value}@{HostName or IPAddress}, or both.

    User-added image
    Check with your local admin that you are pointing to the correct server using the correct port if specified.

  2. Open a Windows command prompt and type ping <IP Address>.  For example …

    >ping {HostName or IPAddress}

    User-added image

    You should see Reply from {IP Address}: …. If you don’t get a reply then you are most likely not on the same network as the license server, or there is an issue with the HostName mapping.

  3. Open a Windows command prompt run lmutil as follows …

    “C:\Program Files (x86)\AGI\LicenseManager\bin\lmutil.exe” lmstat -c "{optional TCP/IP value}@{HostName or IPAddress}"

    User-added image

    In the output locate the following text “STKD: UP v##.##”, if you can’t find this, then the service is not running - send the entire output to your license server administrator.
  4. If you have Windows PowerShell installed, you can run this command to test for an open port on the server ...

    “tnc <host name or IP address> -port <TCP/IP port>"

    User-added image

    FYI - tns is short for Test-NetworkConnection. Look for 'TcpTestSucceeded' value (True is good)

  5. If the server is up and running and you can access the network license when you have local access to the server, but not on VPN,  then it is likely that you’re having firewall issue. Most often this is resolved by adding a user specified TCP/IP ports to the server side license file on both the SERVER and DAEMON lines, and include the SERVER port on the client side. The proper syntax for doing this is discussed in this FAQ: How do I edit my license file?


Resource File 1 
Resource File 2