Product support

Network Licence Manager status codes explained

Article:

Title:

Situation:

Solution:

The following explanation comes from Aladdin's knowledgebase (14/1/2003):

• Status codes 1-34
• Status codes 129-155

Status codes 1-34

1. The IPX, NetBIOS, or TCP/IP protocols have not been installed properly - act accordingly.
2. Communication error - unable to get the socket number (applies to IPX and TCP/IP). Verify that the protocol is installed properly.
3. Communication error. NetBIOS - unable to establish the session. IPX - unable to get the immediate address of the 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.
4. No HASP License Manager was found. Check whether your application has a path to the address file and read permission.
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. The network is busy. IPX - the network is busy or incorrect address files were found. In the latter case, delete all copies of the "haspaddr.dat" and "newhaddr.dat" files.
9. [not used?]
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 properly installed.
12. [not used?]
13. [not used?]
14. [not used?]
15. No active HASP License Manager was found.
16. [not used?]
17. [not used?]
18. Cannot perform a HASP4 Net login because of an unsuccessful SetServerByName call.
19. Syntax error in the configuration file. The LastStatus service returns the line number in which the error occurred in Par2. If LastStatus returns 0 in Par2, there is an environment variable with an illegal setting.
20. Error handling the HASP4 Net configuration file. A file operation such as "open file" or "read file" failed. One possible reason could be that the system is out of file handles. The LastStatus service returns the OS system error code in Par2.
21. HASP4 Net did not succeed in allocating memory. This error is unique to HASP4 Net interfaces under DOS extenders and Windows. Try to free DOS memory.
22. HASP4 Net did not succeed in freeing DOS memory. This error is unique to HASP4 Net interfaces under DOS extenders and Windows.
23. Invalid HASP4 Net memory address.
24. [not used?]
25. Failed to load winsock.dll (applies only to TCP/IP and IPX).
26. Failed to unload winsock.dll (applies only to TCP/IP and IPX).
27. [not used?]
28. Winsock.dll startup error (applies only to TCP/IP and IPX).
29. [not used?]
30. Failed to close socket (applies only to TCP/IP).
31. [not used?]
32. [not used?]
33. SetProtocol service requested without performing logout.
34. Access to key prohibited because the application is running on Citrix Winframe or Windows Terminal Server (service pack 4+ required to detect if this is running on the console screen).

Status codes 129-155

129. The correct HASP4 Net is not connected to the HASP License Manager.
130. The program number specified is not in the program list of the HASP4 Net memory.
131. Error reading from HASP4 Net memory.
132. Error writing to HASP4 Net memory.
133. The current Login request exceeds the number of stations which may run the application at the same time.
134. The current login request exceeds the number of authorized activations for the application.
135. You called the hasp( ) routine with the Logout service without first calling the Login service.
136. The HASP License Manager is busy - this may occur if your HASP4 Net system is not well adapted to the network.
137. There is no space in the HASP4 Net log table.
138. Internal HASP4 Net error - the number of licensed stations is larger than the maximum number allowed by the HASP4 Net model.
139. The computer with the HASP4 Net crashed and was reactivated, or you called the hasp( ) routine with a service (not including 40, 85, or 96) without first calling the login service.
140. The HASP License Manager does not serve the network of your station.
141. Invalid service, or new version of the HASP API is communicating with an older version of the HASP License Manager.
142. The HASP License Manager matching the name specified in the HASP4 Net configuration file was not found.
143. [not used?]
144. [not used?]
145. [not used?]
146. [not used?]
147. [not used?]
148. [not used?]
149. [not used?]
150. No HASP License Manager with the assigned name was found. This error is returned by the SetServerByName service.
151. Two or more different HASP License Managers with the assigned name were found. This error is returned by the SetServerByName service.
152. The encode operation failed because the hardware does not support the service.
153. The decode operation failed because the hardware does not support the service.
154. [not used?]
155. An old version of the License Manager has been found. The API used requires a newer version of the License Manager to be installed.

Product:

Operating systems(s):

Date created:

Last modified:

Online article: