Error Codes

Error Code 0 – Protection Key Not Detected
Cause
Unable to detect a HASP Key.  

Resolution
Ensure that the latest HASP device drivers are installed on the PC which the HASP dongle is plugged into. 

Error Code 100 – Cannot open the HASP Device Driver

Cause
Unable to detect a HASP Key

Resolution
Ensure that the latest HASP device drivers are installed on the PC which the HASP dongle is plugged into.

Net Status 3 – Communication Error

Cause
Unable to establish a connection to HASP License Manager

Resolution
Ensure that there is an active NetHASP License Manager running on the machine with the NetHASP dongle plugged in.

In some instances, a NetHASP.ini file may be required in order to point Preactor at a specific machine running NetHASP License Manager.

Net Status 15 – No Active NetHASP License Manager was found
Cause

1.       New installation that was not configured correctly.

2.       Network protocol mismatch or configuration problem.

3.       Routers/Firewalls blocking the communication between Preactor and the License Manager

Resolution

1.       Rename any existing NetHASP.ini files. Check if error re-occurs. If the error does not return check the NetHASP.ini is configured correctly.

2.       Check that there is at least one common protocol between the machine running Preactor and the License Manager.

3.       Check that Port 475 is open for communication. Port 475 is the default communication port for NetHASP.

4.       Busy network with a lot of noise can slow down communication. Use a NetHASP.ini file.

Net Status 129 – The correct NetHASP is not connected to the NetHASP License Manager

Cause
Error 129 means that a call has reached a License Manager but did not find the correct NetHASP. This situation can be caused by the following :

1.       New installation that was not configured correctly.

2.       Hardware problem or conflict. Two or more HASP keys are connected to the same machine.

3.       No HASP is connected to the computer.

Resolution

1.       If you are using a NetHASP.ini file, check that the correct parameters are entered.

2.       If you are using more than one HASP, disconnect and retry.

3.       If possible replace the HASP to see if this is a HASP hardware issue.

4.       Check to make sure that a NetHASP dongle is connected and not a MemoHASP (local) dongle.

Net Status 130 – The requested license is not included in the list of valid licenses in the NetHASP memory.

Cause 

1.       You are trying to access a version of Preactor that you do not have the appropriate license for..ini file, check that the correct parameters are entered.

2.       Hardware license has not been programmed correctly with license number.

Resolution

                1.       Check that you are using the correct license by modifying the .prcdf file used to launch Preactor.
                2.       Contact Preactor Support Support@Preactor.com  

Net Status 133 – Maximum number of concurrent users being exceeded

Cause
This error may be displayed if more users than licenses are attempting to run a Preactor system, permissions of the user attempting to access the HASP key are insufficient or, in some instances the NetHASP key may be corrupt. It can also occur if the host machine is configured with DHCP, and the IP lease expires whilst using Preactor leaving the key permanently logged in.

Resolution
Please ensure that the user has access to the relevent ports. Download the Aladdin HASP Monitor for further checks. Use a static IP address for the host machine.

Licensing Error Messages

'Protection Key is Not Compatible with the Upgrade Information'.
Cause
This error can occur for the follow reasons:

• NetHASP Dongle not plugged in locally

Resolution
Please ensure that the NetHASP Dongle is plugged in locally to the machine running the .PrKey update file.

If NetHASP dongle is connected, ensure that the .prkey file is not corrupt. Contact support@preactor.com asking for a .zip containing the .PrKey file. Some firewalls/antivirus software appends text to the .PrKey file causing the corruption.

 This key update file is designed for a different version of PR_KEY.