Difference between revisions of "Licensing"

From BESA® Wiki
Jump to: navigation, search
 
(10 intermediate revisions by 5 users not shown)
Line 8: Line 8:
  
  
−
===The BESA software does not start due to a licensing problem. What can I do?===
+
=== 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).
+
The BESA Software is licensed using the Thales hardware-based protection, which utilizes BESA license keys.
−
Only if a Sentinel HASP HL dongle with suitable licenses is available, local or on network, the BESA Software will run.
+
Only if a BESA license key 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
+
 
 +
If you encounter any troubles with starting the BESA software, please make sure that the Sentinel Runtime Environment is installed properly
  
 
* on the machine(s) where the BESA software should be started and
 
* on the machine(s) where the BESA software should be started and
 
* on the machine(s) where the dongle is connected to.
 
* on the machine(s) where the dongle is connected to.
  
−
You can download the latest version of the Sentinel Run-Time Environment [ftp://h1772544.stratoserver.net/public/HASP+Hardlock/HASPUserSetup.exe here].
+
You can download the latest version of the Sentinel Runtime Environment from the BESA website, please refer to the "Complete setup" section [https://www.besa.de/downloads/besa-license-key/ here].
 +
 
 +
 
 +
=== I get communication problems with Sentinel License Managers. What can I do? ===
 +
 
 +
If you encounter communication problems with Sentinel License Managers like:
 +
 
 +
* "Failed to load library"
 +
* "Unable to access Sentinel Run-time environment (H0033)"
 +
* "Communication error between local and remote Sentinel HASP License Managers (H0040)"
 +
* "Sentinel License Manager version too old (H0042)"
 +
 
 +
please read the instruction [https://my.hidrive.com/api/sharelink/download?id=d0nop5lK Communication Problems with Sentinel License Managers.pdf] which should help.
 +
 
 +
 
 +
 
 +
=== Can I update an expired BESA license? ===
 +
 
 +
If your BESA license is expired, please contact our [https://www.besa.de/contact/sales/ Sales Office] for more information.
 +
 
 +
If you encounter any difficulties, please read the instruction [https://my.hidrive.com/api/sharelink/download?id=4JnIJV23 How to update BESA licenses.pdf] which should help.
 +
 
 +
=== How can I configure who is allowed to use the BESA license? ===
 +
 
 +
If you want to configure the license access on your network or to use the licenses only locally, please use the instruction [https://my.hidrive.com/api/sharelink/download?id=unnIJlhi How to use BESA licenses on a network.pdf].
 +
 
  
−
The Run-Time Environment contains the latest drivers for the Sentinel HASP HL dongle.
+
=== 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.
−
===Can I update an expired BESA license?===
+
  
−
If your BESA license is expired, please check if a license update is available for your dongle [http://www.besa.de/downloads/license-update/ here] or contact our [https://www.besa.de/contact/sales/ Sales Office] for more information.
+
If the message "A duplicate license manager id exists on this server" appears:
−
If you encounter any difficulties, please read the instruction [ftp://h1772544.stratoserver.net/public/HASP+Hardlock/HASP%20How%20to%20update%20BESA%20licenses.pdf HASP How to update BESA licenses.pdf] which should help.
+
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.
  
−
----
 
−
===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 [ftp://h1772544.stratoserver.net/public/HASP+Hardlock/HASP%20How%20to%20update%20BESA%20licenses.pdf HASP How to update BESA licenses.pdf].
+
=== BESA software 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.
−
===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 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.
 
  
 
[[Category:Setup]]
 
[[Category:Setup]]
 +
[[Category:Troubleshooting]]

Latest revision as of 16:35, 12 October 2023

Module information
Modules Any module
Version 5.2 or higher

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 Thales hardware-based protection, which utilizes BESA license keys. Only if a BESA license key 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 that the Sentinel Runtime 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 Runtime Environment from the BESA website, please refer to the "Complete setup" section here.


I get communication problems with Sentinel License Managers. What can I do?

If you encounter communication problems with Sentinel License Managers like:

  • "Failed to load library"
  • "Unable to access Sentinel Run-time environment (H0033)"
  • "Communication error between local and remote Sentinel HASP License Managers (H0040)"
  • "Sentinel License Manager version too old (H0042)"

please read the instruction Communication Problems with Sentinel License Managers.pdf which should help.


Can I update an expired BESA license?

If your BESA license is expired, please contact our Sales Office for more information.

If you encounter any difficulties, please read the instruction How to update BESA licenses.pdf which should help.

How can I configure who is allowed to use the BESA license?

If you want to configure the license access on your network or to use the licenses only locally, please use the instruction How to use BESA licenses on a network.pdf.


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

Retrieved from "https://wiki.besa.de/index.php?title=Licensing&oldid=5362"