Cloned Software License Removal

Owned by Kirill Nikolaev (Unlicensed)
Last updated: Jun 15, 2023 by Alexandre SOUF
3 min read

Problem

In certain situations a Software License may become "Cloned" (disabled), this can occur when changing hardware configuration of physical or virtual CHARON host. For more see HASP Software Licensing restrictions.

Example:

In this situation there is no way to remove the license by the standard methods.

Solution

 The following procedure must be applied to remove the cloned license:
    1. Go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (SACC).

    2. In the "Sentinel HASP Admin Control Center" (SACC), locate the target "Sentinel SL AdminMode" license.

    3. Press the "Certificates" button at the right side of the SL description:

    1. Note the name of the correspondent certificate (1) and path to the certificates base directory (2) in the "Certificates" section:

  1. Remove the certificate files (*.v2c files) from the certificates base directory:
    1. For Windows hosts, the files are located in the folder "C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel LDK\installed\68704".
      (lightbulb) In the example above, the file to remove is  "C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel LDK\installed\68704\340823357928523443_base.v2c" - If some updates were applied to this base license the additional files also need to be removed. 
    2. For Linux hosts, these files are located in the "/var/hasplm/installed/68704/" folder.

  2. Reboot CHARON host or restart the Sentinel LDK service:
    1. On Windows, restart the "Sentinel LDK License Manager" service (hasplms) either using the services.msc program or via a command line (as administrator) then enter the "sc stop hasplms" command followed by "sc start hasplms" or using PowerShell "Restart-Service hasplms" command.
      (warning) this can be done only if no emulator is running due to service dependencies. If another emulator is running and cannot be stopped, killing the hasplms.exe process and starting the service can be used as a workaround.
    2. On Red Hat Enterprise Linux (7 or 8 or 9), CentOS (7 or 8) and Rocky Linux (8 or 9), restart the aksusbd service: # systemctl restart aksusbd
    3. On Red Hat Enterprise Linux 6.x, restart the aksusbd service: # service aksusbd restart

  3. Start "Sentinel HASP Admin Control Center" (ACC) again to ensure that the SL has been removed.


<Go to Top>


© Stromasys, 1999-2024  - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.