Список кодов ошибок Hasp и их значения
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 immediate address of HASP License Manager. 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 HASP License Manager was found. Check whether your software has a path and read permission to the address file.
5 Cannot read the HASP License Manager address file.
6 Cannot close the HASP License Manager address file.
7 Communication error. Failed to send packet.Verify that the protocol is installed properly.
8 No answer from the HASP 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 a function without first calling the Login function.
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 HASP License Manager was found.
18 Cannot perform HASP network login because the SetServerByName call was not successful.
19 Syntax error in the 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 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 HASP network key did not succeed in allocating memory. This error is unique to HASP network key interfaces for Microsoft Windows applications and DOS extenders.Try to free DOS memory.
22 HASP network key did not succeed in freeing memory. This error is unique to HASP network key interfaces for Microsoft Windows applications and DOS extenders.
23 Invalid HASP network key 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 start-up 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.
34 Access to key prohibited because the application is running on Citrix Winframe or Windows Terminal Server.
129 The correct HASP network key is not connected to the HASP License Manager.
130 The Program Number (ProgNum) specified is not in the Program List of the HASP key’s memory.
131 Error reading from HASP key memory.
132 Error writing to HASP key memory.
133 The current Login request exceeds the number of stations that may run the software concurrently.
134 The current Login request exceeds the number of authorized activations for the software.
135 You called the Logout function without first calling the Login function. This can happen when the License Manager was reloaded or you have been logged out from the License Manager.
136 The HASP License Manager is busy.
137 There is no space in the HASP network key user list.
138 The Number of Authorized Stations is larger than the maximum number designated by the HASP model.
139 You called a function without first calling the Login function.
140 The HASP 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 HASP License Manager.
142 Cannot find the HASP License Manager matching the name specified in the HASP configuration file.
150 No HASP License Manager with the assigned name was found.
151 Two or more different HASP License Managers with the assigned name were found.
152 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.
157 Buffer size too small for requested function.
158 HASP License Manager running on machine with old HASP driver installed.
159 HASP License Manager running on machine with no HASP driver installed.