...
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 Server's immediate address. Verify that the protocol is installed properly. |
4 | No NetHASP Server was found. Check whether your software has a path and read permission to the address file. |
5 | Can't read the NetHASP Server address file. |
6 | Cannot close the NetHASP Server address file. |
7 | Communication error. Failed to send packet. Applies to IPX and NetBIOS. Verify that the protocol is installed properly. |
8 | No answer from the NetHASP Server.IPX - The network is busy or incorrect address files found. In the last case, delete all copies of the HASPADDR.DAT and NEWHADDR.DAT files. NetBIOS - the network is busy. |
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. Verify that the protocol is installed properly. |
12 | No active NetHASP Server was found. Applies to IPX and NetBIOS. |
15 | Serial Number Mis-match |
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). |
20 | Error handling the NetHASP configuration file (LASTSTATUS service returns the system error code in Par2). |
21 | NetHASP did not succeed in allocating memory. This error is unique to NetHASP interfaces under Microsoft Windows and DOS extenders. |
22 | NetHASP did not succeed in freeing memory. This error is unique to NetHASP interfaces under Microsoft Windows and DOS extenders. |
23 | Invalid NetHASP memory address. |
25 | Winsock.dll did not identify the TCP/IP protocol. Verify your TCP/IP installation. |
26 | Failed to unload winsock.dll |
28 | Winsock.dll startup error |
30 | Fail to close TCP/IP socket |
33 | SetProtocol service was called without performing a NetHASP LOGOUT or after performing a LOGIN. |
34 | Access to key prohibited because application is running Citrix Winframe or Windows Terminal Server |
129 | The correct NetHASP is not connected to the License Manager |
130 | The program number specified is not found in the NetHasp key memory |
131 | Error reading NetHASP memory |
133 | Current login request exceeds the number of stations that may run the application |
134 | Current login request exceeds the number of licenses authorized for the application |
135 | Logout request called without being logged in. |
136 | License manger is busy or not properly adapted to network |
137 | Out of space in NetHASP log table |
138 | Internal NetHASP error-excessive number of licenses for NetHASP |
139 | License manager computer failed or proper login not done |
140 | License manger does not serve the network of your station |
141 | Invalid service call or HASP API is communicating with old version of License Manager |
142 | No license manager found with name specified in NetHASP configuration file |
150 | No license manger with assigned name was found (SetServerbyName service) |
151 | Two or more License Managers with same name found (SetServerbyName service) |
152 | Encode operation failed because hardware does not support the service |
153 | Encode operation failed because hardware does not support the service |
155 | Found version of older NetHASP License Manager (prior to V6.1) |
...