Simcenter Flomaster Forcibly releasing a stuck network license feature back to the server

2024-06-25T20:41:04.000-0400
Flomaster

Summary

When a user is done using an application on a client machine, the license used by the software should automatically return to the license pool on the server as soon as the user closes the application. However, there are instances in which the license feature gets stuck on the client and fails to return to the server even when the user has closed the application. This article provides detailed instructions on how to forcibly release a license feature that is still stuck on a client machine back to the license pool on the server after the user has closed their application on the client and is no longer using the license. This solution is restricted to FlexLM and saltd vendor daemon..


Details

Definitions:

  • port_ number: This is the port reserved for the license manger to communicate (Ex. 29000, 5053).
  • license_feature: This is the license feature stuck on the client machine that needs to be released back to the license pool on the server (Ex. lms_il_ame_01, FloMASTERdyna_c)
  • license_file_path: This is the path to the license file containing the stuck license feature on the server.
  • server_hostname: This is the name assigned to the server hosting the license (Ex. server_100).

Steps:

  1. On the server, open the windows command prompt and switch to the Siemens License Server directory. It is the directory that contains the lmgrd executable file - “lmgrd.exe”:

cd C:\Program Files\Siemens\License Server

 

  1. Run the lmutil lmstat command to get details of the syntax that will then be used to run the lmremove command that releases the hung license. Depending on if the specific license feature that is stuck is known or unknown, there are few different ways to run the lmutil lmstat command.

 

  1. If the specific license feature that is stuck is unknown or uncertain, run the following commands to see a full list of all available FLEXlm or SALTD license feature contained in the license server.

          lmutil lmstat -a -c port_ number@server_hostname

          Example:
          lmutil lmstat -a -c 29000@server_100 


Or using the license file path

lmutil lmstat -a -c license_file_path

For the license file path, go the location of the license file on the license server, right click on the license file, copy as path and add it to the “lmutil lmstat -a -c …” command as shown below.

A screenshot of a computerDescription automatically generated


      Example:
      lmutil lmstat -a -c "C:\ProgramData\Siemens\License Server\ActiveLicenses\ugslmd.lic"

  1. If the specific license feature that is stuck is known, run the following commands for that license feature as shown below.

lmutil lmstat -f license_feature -c port_ number@server_hostname

      Example:

      lmutil lmstat -f FloMASTERdyna_c -c 29000@server_100

      Or using the license file path
      lmutil lmstat -f license_feature -c license_file_path

      Example:
      lmutil lmstat -f FloMASTERdyna_c -c "C:\ProgramData\Siemens\License Server\ActiveLicenses\ugslmd.lic"

  1. Output returned by the lmutil lmstat command

[Detecting lmgrd processes...]
License server status: port_ number@server_hostname

License file(s) on server_hostname: license_file_path(s):

 

server_hostname: license server UP (MASTER) v11.19.0
server_hostname: license server UP v11.19.0

 

Vendor daemon status (on server_hostname):

 

        vendor daemon_1: UP v11.19.0

Feature usage info:

 

        vendor daemon_2: UP v11.19.0

Feature usage info:

 

        vendor daemon_3: UP v11.19.0
Feature usage info:

 

Users of license_feature:  (Total of xx licenses issued; Total of x license in use)

 

   "license_feature" v2029.010, vendor: vendor_daemon_x, expiry: dd-month-year

floating license

 

 my_username client_hostname client_hostname_display (v_release) (server_hostname/port_number handle), start checkout_weekday checkout_month/checkout_day checkout_time

 

  1. Understanding the output of the lmutil lmstat command
    • my_username: This is the username of the client machine that checked out the license. This is usually the same name as the local user’s home directory folder. For instance, C:\Users\ my_username > (Ex. jane_doe: like in C:\Users\ jane_doe>).

    • client_hostname: This is the hostname assigned to the client that checked out the license (Ex. jdpc).

    • client_hostname_display: This is the display name of the hostname assigned to the client that checked out the license (Ex. jdpc0.0).

    • v_release: This is the version of the software release (Ex. v2023.10, v2024.04).

    • handle: This is a 3-digit number that is used to uniquely identify the license session (Ex. 202, 305).

    • dd: This is the day the license file containing the stuck license feature will expire (Ex. 09,13,28).

    • month: This is the month the license file containing the stuck license feature will expire (Ex. jan, nov).

    • year: This is the year the license file containing the stuck license feature will expire (Ex. 2026, 2029).

    • checkout_weekday: This is the day of the week the stuck license feature was checked out from the license server (Ex. Tue, Fri).

    • checkout_month This is the month the stuck license feature was checked out from the license server (Ex. 6,12).

    • checkout_day: This is the day the stuck license feature was checked out from the license server (Ex. 8, 20).

    • checkout_time: This is the time the stuck license feature was checked out from the license server (Ex. 10:40, 15:24).

    • vendor_daemon_x: These are the vendor daemon used to manage license on the server including the license containing the stuck license feature (Ex. saltd, ugslmd, mgcld).

  1. Example of the output returned by the lmutil lmstat command

[Detecting lmgrd processes...]
License server status: 29000@server_100

License file(s) on server_100: C:\ProgramData\Siemens\License

Server\ActiveLicenses\mgcld.lic:C:\ProgramData\Siemens\License Server\ActiveLicenses\ugslmd.lic:

server_100: license server UP (MASTER) v11.19.0
server_100: license server UP v11.19.0

 

Vendor daemon status (on server_100):

 

             saltd: UP v11.19.0

Feature usage info:

 

    ugslmd: UP v11.19.0

Feature usage info:

 

     mgcld: UP v11.19.0

Feature usage info:

 

Users of FloMASTERdyna_c: (Total of 10 licenses issued; Total of 1 license in use)

 

"FloMASTERdyna_c" v2029.010, vendor: mgcld, expiry: 28-nov-2029 

floating license

 

jane_doe jdpc jdpc0.0 (v2023.10) (server_100/29000 305), start Fri 6/20 15:24

 

  1. With the output from the lmutil lmstat command, run the lmremove command to release the license feature stuck on the client machine back to the license pool on the server. The lmremove command can be run one of 2 ways   

 

    1. lmutil lmremove -c port_ number@server_hostname -h  license_feature server_hostname port_ number handle

        Example:

        lmutil lmremove -c 29000@server_100 -h FloMASTERdyna_c server_100 29000 305

 

    1. lmutil lmremove -c port_ number@server_hostname license_feature my_username client_hostname client_hostname_display

 

        Example:

        lmutil lmremove -c 29000@ server_100 FloMASTERdyna_c jane_doe jdpc jdpc0.0

KB Article ID# KB000133331_EN_US

Contents

SummaryDetails

Associated Components

Simcenter Flomaster