Solution to corrupted HASP HL Keys in VMware on a Linux Host

An issue has been discovered on Linux platforms when the following conditions exist:

-> VMware is hosted on a Linux machine.
-> Sentinel HASP Run-time Environment is installed both under the host Linux operating system and under the guest VMware environment.
-> A HASP HL key is connected to a USB port on the Linux machine.

Under these conditions, VMware does not block the host USB port if the USB port on the guest is enabled. As a result, both the host (Linux) operating system and the guest (VMware) operating systems access the USB port simultaneously. This simultaneous access to the HASP HL key from both operating systems sometimes causes corruption of the key, since the key expects only a single entity to access it at any given time.

Note that when VMware is hosted on a Windows machine, this issue does not occur. A HASP HL key connected to a USB port on the machine is accessible by only one of the two operating systems (either the physical host or virtual guest).

Workaround:
Sentinel HASP Run-time Environment should exist in only one of the two operating systems (either the physical host or virtual guest). Uninstall the Sentinel HASP Run-time Environment from the operating system where you do not want to use the HASP licensing. For example: If Sentinel HASP licensing is to be used in the VM guest operating system, uninstall Sentinel HASP Run-time Environment from the host Linux machine.