Problems with loading or setting the licence

General verification of hardware licence key driver functionality

After installing the PROMOTIC system on the target computer and after inserting the USB licence key into the port the key lights up (this applies to normal standard keys). In the Web browser at address http://localhost:1947 when selecting the item Sentinel keys a graphical representation of the connected key will be displayed and the "Blink on" button can be used to flash the key light.

QUESTIONS

1. I have a HW Key containing the runtime licence, but the application cannot load this licence.

2. The application will run on a virtual computer. What are the options?

3. What should I do when porting an older working application to a computer running the new Windows?

4. I think everything is set up correctly, but the runtime licence still cannot be loaded. How to proceed?

1. The application cannot load the licence from HW Key

The cause can be:

a) The installed PROMOTIC version does not have the appropriate HW Key driver for the current version of the Windows OS. For the solution see Compatibility table Windows OS and PROMOTIC version

b) The application is launched remotely in RDP mode (remote desktop). For the solution see PROMOTIC system and Windows remote desktop (RDP)

c) Error in the application's INI file in the "Licence" section

d) The application (in the PROMOTIC 9 version) is launched in the development environment but the HW Key contains the runtime licence.
The correct settings for launching the application are set by the PmManager program by the configurators in the "Tools and settings > Basic settings" item.

2. Application on a virtual computer

There are several options depending on the availability of the USB port for the virtual computer and also on the administration of such computer (RDP protocol or other).

a) Options if the HW Key is connected into the USB port of the host device and made available for the USB on a virtual computer.

a1) The key may contain a runtime licence, but there may be a problem launching the application, because the application (due to RDP access or other reasons) may not have access rights to the USB port.
It always has these rights if it is running as a service in Windows. But in this case, the application is without a graphic interface.

a2) The licence is provided by the licence server. See PROMOTIC network licence, Network licence key, PmLicServer licence server.

b) The USB port is not available for the virtual computer.

b1) Licence is provided by a licence server running on another computer in the local network. See the links PROMOTIC network licence, Network licence key, PmLicServer licence server.

b2) Licence bound to the operating system (Windows) of the computer. See Software licence key (.swk) bound to specific components of the Windows OS.

3. Older working application transferred to a new computer.

It is necessary to detect the PROMOTIC version in which the application is running. Then according to the compressibility table find out whether the version can run on the installed version of the Windows OS.

a) If this assumption is met, then the appropriate PROMOTIC version will be installed on the target machine. and the appropriate driver from https://www.promotic.eu/en/promotic/download/download.htm. The application and any additional components required to run the application are copied (database, communication drivers, ...).

b) If the application in the given version will not be able to run on the given Windows OS, then the application will have to be converted to a higher version of PROMOTIC supported in Windows OS. This can only be done with a PROMOTIC development licence by the application owner or with his consent. In this case it may be necessary to renew the licence (PmUpgrade10 - Extension of upgrade and expansion period of the licence key for 10 more years).

c) If the application is being transferred to a virtual computer, then it must meet the requirement 3a, but it may also be possible to change the licensing method according to 2.

4. The runtime licence still cannot be loaded

Possible causes:

- The application is being launched by the remote desktop with the RDP protocol.

- The application is set to launch as PmRtFree - free runtime, limited application size or PmRtDemo - demo runtime, unlimited application size

- The application (in version PROMOTIC 9) tries to run to the development environment instead of runtime

- HW Key driver is not working

- Error in the application's INI file in the "Licence" section

- The temporary licence was issued with a time limit that has expired

Recommended procedure:

The licence is contained in the HW Key:

1) Determine the functionality of the HW Key driver.

2) Check HW Key settings - see PROMOTIC system and Windows remote desktop (RDP)

3) Launch the Demo application (or other small size application) and see in the INFO system on the "PmaRoot > Licences" tab if the licence is loaded. If yes (the four digit licence number is listed in the "Licence number" entry), then it is necessary to look for an error in settings of the application itself.

The licence is provided by the licence server:

1) Check the functionality of the licence server at the addresses (in PROMOTIC 9 version) http://ipserveru:5656/info.html and http://ipserveru:5656/log.html. The installation and commissioning procedure is described in the documentation for the corresponding PROMOTIC version. See PmLicServer licence server.

2) Check the settings in the application's INI file, see PmLicServer licence server.

The licence is bound to Windows OS:

1) Check the settings in the application's INI file Software licence key (.swk) bound to specific components of the Windows OS.

2) The licence was working but failed after some time.

This can be caused by a time limitation set in the licence or by an update, upgrade or migration of a virtual computer running the Windows OS, that have caused changes of the Windows OS.

A new valid licence must be generated SwLicWithWIN (this service may incur a fee).

Promotic