Charon-AXP/VAX/PDP V4.9 B19402 fails to detect license at start

Problem


(warning) Affected versions(tick) Solved with patches
Windows

Charon-AXP V4.9 Build 194-02
Charon-VAX V4.9 Build 194-02
Charon-PDP V4.9 Build 194-02

Build 194-07 published July 2nd, 2019
Linux

Charon-AXP V4.9 Build 194-02
Charon-VAX V4.9 Build 194-02
Charon-AXP V4.9 Build 194-04
Charon-VAX V4.9 Build 194-04

Build 194-07 published July 2nd, 2019

Linux

If you defined the Charon virtual machine as a service, the license could not be seen on Linux server boot, specially when using USB boxes that provide USB ports over the network.

Using these devices, the license dongle would need some time to be detected once the Linux server is booted.

(warning) Due to a bug in the vanilla version (Build 194-02), the license_key_lookup_retry parameter is not taken into account.


Example:

set session license_key_lookup_retry = "10,30"

Description: if license key is not found during initial scan, do 10 more attempts waiting 30 seconds between them.

Windows

The license could not be seen on Windows server boot, specially when using USB boxes that provide USB ports over the network.

Using these devices, the license dongle would need some time to be detected once the Windows server is booted.

This can cause Charon virtual machine, which is a Windows service, defined for automatic startup to fail with license missing on Charon server boot.

(warning) Due to a bug in the vanilla version (Build 194-02), the license_key_lookup_retry parameter is not taken into account.

Solution

The following solutions have to be applied if the patch has not been installed.

Linux

Add a startup delay in the service definition or script starting the virtual machine or use the Linux Toolkit that already contains a check to verify a license is found before running the Charon executable file.

Patch details are available here: Charon-AXP V4.9 Build 194-08 for Linux 64 bit - Patch Notes

Windows

It is highly recommended to install the latest patch available and use the license_key_lookup_retry feature as described in the example above.

Patch details are available here: Charon-AXP V4.9 Build 194-08 for Windows 64 bit - Patch Notes

With the vanilla version (Build 194-02), there is also a missing dependency to the Sentinel LDK License Manager service (hasplms) that can produce license detection errors at Charon virtual machine startup (if it starts before the hasplms service).

(lightbulb) This can be solved by opening a cmd.exe window as an Administrator and running the following command (do not omit space after the equal sign):

C:\...>sc config <service> depend= hasplms/tcpip

Add a delay in the automatic startup for the Charon virtual machine service. This cannot be done using the Virtual Machines Manager so use either the Windows Service manager (services.msc) GUI or run the following command:

C:\...>sc config <service> start= delayed-auto

(question) Note this will not guarantee at 100% the license will be present. The license_key_lookup_retry feature is then recommended (if the patch is installed).

To verify the settings are correctly set, use the "sc qc <service>" command.

Example:

C:\Windows\system32>sc config AS4100 depend= hasplms/tcpip
[SC] ChangeServiceConfig SUCCESS

C:\Windows\system32>sc config AS4100 start= delayed-auto
[SC] ChangeServiceConfig SUCCESS

C:\Windows\system32>sc qc AS4100
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: AS4100
        TYPE               : 10 WIN32_OWN_PROCESS
        START_TYPE         : 2 AUTO_START (DELAYED)
        ERROR_CONTROL      : 1 NORMAL
        BINARY_PATH_NAME   : "C:\Program Files\CHARON\Build_19402\x64\as4100.exe"
        LOAD_ORDER_GROUP   : TargetPlatformEmulator
        TAG                : 0
        DISPLAY_NAME       : AS4100
        DEPENDENCIES       : tcpip
                           : hasplms
        SERVICE_START_NAME : LocalSystem

(red star) These operations will have to be performed on each service update if the patch has not been installed.

Related articles



© 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.