Difference between revisions of "Licensing"
| Line 37: | Line 37: | ||
If you want to configure the license access on your network, please use the instruction [ftp://h1772544.stratoserver.net/public/HASP+Hardlock/HASP%20How%20to%20use%20BESA%20licenses%20on%20a%20network.pdf HASP How to use BESA licenses on a network.pdf]. | If you want to configure the license access on your network, please use the instruction [ftp://h1772544.stratoserver.net/public/HASP+Hardlock/HASP%20How%20to%20use%20BESA%20licenses%20on%20a%20network.pdf HASP How to use BESA licenses on a network.pdf]. | ||
| + | |||
| + | Note that the abovementioned instruction is applicable also to the VPN connection. In case the license server is not found you may need to provide the server address explicitly in the [http://localhost:1947/_int_/config_to.html Sentinel ACC] tab: (Configuration / Access to Remote License Managers). The server IP address or server Name should be typed in the Remote License Search Parameters field. | ||
Revision as of 15:15, 14 April 2020
| Module information | |
| Modules | Any module |
| Version | 5.2 or higher |
Contents
- 1 Frequently asked questions concerning licensing:
- 1.1 The BESA software does not start due to a licensing problem. What can I do?
- 1.2 I get an error message "Failed to load library" during the installation of the HASP drivers. What can I do?
- 1.3 Can I update an expired BESA license?
- 1.4 How can I configure who is allowed to use the BESA network license?
- 1.5 The BESA network licenses are not usable on the client machine. What can be the reasons for this?
- 1.6 BESA does not start because too many licenses are in use. How can I free a license?
Frequently asked questions concerning licensing:
The BESA software does not start due to a licensing problem. What can I do?
The BESA Software is licensed using the Sentinel HASP (formerly Aladdin HASP SRM) hardware-based protection, which utilizes HASP HL keys (USB dongles). Only if a Sentinel HASP HL dongle with suitable licenses is available, local or on network, the BESA Software will run.
If you encounter any troubles with starting the BESA software, please make sure first that the Sentinel Run-Time Environment is installed properly
- on the machine(s) where the BESA software should be started and
- on the machine(s) where the dongle is connected to.
You can download the latest version of the Sentinel Run-Time Environment here. The Run-Time Environment contains the latest drivers for the Sentinel HASP HL dongle.
I get an error message "Failed to load library" during the installation of the HASP drivers. What can I do?
Please see the page Error message: Failed to load library for help with this problem.
Can I update an expired BESA license?
If your BESA license is expired, please check if a license update is available for your dongle here or contact our Sales Office for more information.
If you encounter any difficulties, please read the instruction HASP How to update BESA licenses.pdf which should help.
How can I configure who is allowed to use the BESA network license?
If you want to configure the license access on your network, please use the instruction HASP How to use BESA licenses on a network.pdf.
Note that the abovementioned instruction is applicable also to the VPN connection. In case the license server is not found you may need to provide the server address explicitly in the Sentinel ACC tab: (Configuration / Access to Remote License Managers). The server IP address or server Name should be typed in the Remote License Search Parameters field.
The BESA network licenses are not usable on the client machine. What can be the reasons for this?
Start a Web Browser and type http://localhost:1947/_int_/log.html.
If the message "A duplicate license manager id exists on this server" appears: Kindly copy " http://localhost:1947/action.html?create_new_lmid " on cloned License Manager ID machine browser and press enter. It will change the ID of License Manager.
BESA does not start because too many licenses are in use. How can I free a license?
Start a Web Browser and type http://localhost:1947/_int_/sessions.html. This shows all connected sessions. They can be disconnected if required using the button on the right of the display.
