To check the dongle (HASP key)

1. Bring up Sentinel Admin Control Center by entering the following path in browser address bar-
http://localhost:1947
2. Click on Diagnostics in Options list on left of screen
3. Click on Generate Report button at bottom center of screen
4. Scroll down list and look for entry under "Local Sentinel Keys" or "Remote Sentinel Keys"
5. Email the Key ID number listed to techsupport@intusoft.com

To test if there are any interferences in the network communication between the client and the License Manager, use the following commands from the command-line:

1. Simple communication test:
ping <ip address>

- Expected result: The message should include the text (0% loss)
- Any number other than zero means that TCP/IP communication is not working properly.

2. Verifying that License Manager port (475) is open:
Load the LM on the remote machine and start a Telnet session on the client, using the IP address of the computer with the LM:
telnet <ip address> 475

- Expected result: The terminal screen will be cleared; pressing any key will return the message "Connection to host lost."
- Result if the LM could not be reached: "Could not open a connection to host on port 475 : Connect failed". This means that port 475 is blocked.

---------------------------
Configure “Data Execution Prevention” to Allow the Service to Run

If Data Execution Prevention (DEP) is turned on for all programs and services, you must enter the HASP License Manager service executable as an exception.
This is the default setting for Windows 7 (and newer) and Windows Server 2008 (and newer).


Do the following:
1. From the Start menu, select Control Panel > System and Security > System.
2. In the System Properties dialog box, click the Advanced tab.
3. In the Performance pane, click Settings.
4. In the Performance Options dialog box, click the Data Execution Prevention tab
5. If option Turn on DEP for all programs and services except those I select is selected, do the following:
a. Click Add.
b. browse to and select the HASP License Manager service (by default, C:\spice8lm\Service\nhsrvice.exe)
 

The following error codes are returned by the NetHASP system. Error codes below 129 are communication errors. Error codes from 129 and up are returned by the NetHASP License Manager.
Error Code
 Description
0
Operation successful.
1
 The IPX, NetBIOS or TCP/IP protocols have not been installed properly. Act accordingly.
2
 Communication error. Unable to get socket number. Applies to IPX and TCP/IP. Verify that the protocol is installed properly.
3
 Communication error. - NetBIOS: Unable to establish session. Verify that the protocol is installed properly. - IPX: Unable to get NetHASP License Manager's immediate address. Verify that the protocol is installed properly. - TCP/IP: Unable to connect to the server. Verify that the server address is correct in the INI file.
4
No NetHASP License Manager was found. Check whether your software has a path and read permission to the address file.
5
 Cannot read the NetHASP License Manager address file.
6
Cannot close the NetHASP License Manager address file.
7
 Communication error. Failed to send packet. Verify that the protocol is installed properly.
8
No answer from the NetHASP License Manager. IPX - The network is busy or incorrect address files found. In the latter case, delete all copies of the HASPADDR.DAT and NEWHADDR.DAT files. NetBIOS - the network is busy. TCP/IP - If the TCP method is used then the network is busy. If the UDP method is used then the network is busy or there is an incorrect address in the INI file.
10
You called the hasp() routine with one of the services, without first calling the LOGIN service.
11
 Communication error. Adapter error. Applies only to NetBIOS. This error can also happen when the NETBIOS protocol is not installed. Verify that the protocol is installed properly.
15
No active NetHASP License Manager was found.
18
Cannot Login because the SET_SERVER_BY_NAME call was not successful.
19
 Syntax error in the NetHASP configuration file (LASTSTATUS service returns the line number in which the error occurred in Par2). If LastStatus returns 0 in par2, either there is an environment variable with an illegal setting, or no IP address was found (when working with TCP/IP or UDP to host).
20
 Error handling the NetHASP configuration file. A file operation like "open file" or "read file" failed. A possible reason can be that the system has run out of file handles. The LastStatus service returns the OS system error code in Par2.
21
 NetHASP did not succeed in allocating memory. This error is unique to NetHASP interfaces for Microsoft Windows applications and DOS extenders. Try to free DOS memory.
22
 NetHASP did not succeed in freeing memory. This error is unique to NetHASP interfaces for Microsoft Windows applications and DOS extenders.
23
 Invalid NetHASP memory address.
25
 Failed to load the DLL (winsock.dll or w32sock.dll). Applies only to TCP/IP or IPX.
26
 Failed to unload the DLL (winsock.dll or w32sock.dll). Applies only to TCP/IP or IPX.
28
 Winsock.dll startup error. Applies only to TCP/IP.
30
Failed to close the socket. Applies to TCP/IP only.
33
 Protocol already set. Returned only when you attempt to set the protocol without having logged out completely from the API.
129
 The correct NetHASP key is not connected to the NetHASP License Manager.
130
 The Program Number (Prg Num) specified is not in the Program List of the NetHASP memory.
131
 Error reading from NetHASP memory.
132
 Error writing to NetHASP memory.
133
 The current LOGIN request exceeds the number of stations which may run the software concurrently.
134
The current LOGIN request exceeds the number of authorized activations for the software.
135
You called the hasp() routine with the LOGOUT service without first calling the LOGIN service. This can happen when the License Manager was reloaded or you have been logged out from the License Manager.
136
 The NetHASP License Manager is busy. This may occur if your NetHASP system is not well adapted to the network.
137
 There is no space in the NetHASP user list.
138
 Internal NetHASP error. The Number of Authorized Stations is larger than the maximum number designated by the NetHASP model.
139
The NetHASP License Manager crashed and was reactivated, or you called the hasp() routine with one of the services without first calling the LOGIN service.
140
 The NetHASP Licence Manager does not serve your station's network.
141
 Invalid service, or new version of the HASP API is communicating with an older version of the NetHASP License Manager.
142
 Cannot find the NetHASP License Manager matching the name specified in the NetHASP configuration file.
150
 No NetHASP License Manager with the assigned name was found (this error is returned by SET_SERVER_BY_NAME).
151
 Two or more different NetHASP License Managers with the assigned name were found (this error is returned by SET_SERVER_BY_NAME).
152
The encode operation failed because the service was not supported by the hardware.
153
 The decode operation failed because the service was not supported by the hardware.
155
 An old version of the License Manager has been found. The API used required a newer version of the License Manager to be installed.