Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Table of Contents |
|---|
“HASP key not found (H0007)” error
| Cause | Solution |
|---|---|
License key is not connected. | Connect the license key. |
Connected license key's batch code is different from required one (a license key |
of another software vendor is used). | Connect the license key |
provided by VIT. | |
When network license key is required, the license key being connected does not enable the protected software. | Check if the license key that is being connected is a network key (usually red) and, if not, connect the network protection key. See also: |
Sentinel LDK Run-time environment (hasplms.exe process) is not |
installed on the computer where protected software is to run. | See the instructions: Sentinel LDK Run-time environment installation (Windows) Sentinel LDK Run-time environment installation (Linux) |
Network traffic is blocked at Port 475 on the computer where the license key is installed and/or protected software is running (due to Windows Firewall or, for example, antivirus software). | Disable all the software that may block access to your license key or add a blocked object into a list of exceptions (whether it is Port 475, Sentinel LDK Run-time service or other software blocked). |
“Feature not found (H0031)” error
| Cause | Solution |
|---|---|
The license key does not have any information about Program Number/Feature ID requested by protected application. | Update the license key: |
On your computer, two license keys with the same batch codes are installed. The key that was detected and |
currently enables the protected application does not have |
the feature(s) needed by that application. |
For hardware license keys: connect available keys one-by-one to see which of them enables protected functionality of your application. Also, read more on this conflict (the Important 2 block). |
“Unable to access HASP SRM RunTime Environment (H0033)” error
| Cause | Solution |
|---|---|
C:\WINDOWS\system32\hasplms.exe is blocked by the Firewall or antivirus software. | Add the Sentinel LDK Run-time environment to the blocking exceptions list. |
| Port 1947 is blocked by the Firewall. | Add the port to the blocking exceptions list. |
Sentinel LDK Run-time environment (hasplms.exe) | Relaunch the environment's process. |
“Terminal services detected, cannot run without a dongle (H0027)” error
| Cause | Solution |
|---|---|
Occurs when terminal services are detected. For example, Microsoft Terminal Server (including Remote Desktop services), Citrix Winframe/Metaframe etc. | Your license key should not be connected to a computer that has active terminal software installed. VIT controls this option by allowing or prohibiting its products operation on terminal servers |
. If such option is needed, request for the license key update: |
“Your license has expired (H0041)” error
| Cause | Solution |
|---|---|
| The license has expired. | Update the license key: |
| System time on the computer was changed manually. |
"UpdateTooOld"
Trying to install a V2C file with an update counter that is out of sequence with update counter in the Sentinel protection key. Values of update counter in file are lower than those in Sentinel protection key.55
"UpdateTooNew"
Trying to install a V2C file with an update counter that is out of sequence with the update counter in the Sentinel protection key. First value in file is more-than-1 greater than value in Sentinel protection key.
| Cause | Solution |
|---|---|
When licensing information contained in a v2c-file is to update (rewrite) the information contained in the corresponding license key, that new information must be applied strictly in a sequence of corresponding c2v-files generation. | Check if you are applying several license updates in a right order and whether all of them are present and none skipped. If everything seems to be applied correctly, but the error still occurs, contact your manager: there might be something overlooked while v2c-files generation on VIT's side. Possible solution may be to format your license key and write a new license information into it from scratch. |