Knowledge:Network Key Problems

If your are not running a network key please refer to Local key error (15)

Description

• While trying to run my NetHasp protected application :
  • I receive a HASP Error message 15 : "No active HASP License Manager was found."
  • You are unable to add new modules to the key.
  • You receive a message saying that not hasp were found or similar.
  • If you received a message "Too many users are using the module" or similar , use the monitor application to see modules currently in use : Aladdin Monitor
• Cause:

1. New installation that was not configured correctly.
2. Network protocol mismatch or configuration problem.
3. Changes were implemented to a working system. These changes did not reflect on the stations and they are still working with the old NetHasp configuration.
4. Routers/Firewalls blocking the communication between the protected application and the LM.

Note that multiple Aladdin network keys cannot be used on a same computer, even if they are for different applications or modules. 
They must be attached to different computers with separate License Managers running.

Solution

(Try to run OptiTex License Manager as the test software, when it opens look at the key number on the top, if it's zero, then no hasp was found)

1. Install the latest driver from Aladdin web site :Latest NetHasp LM
2. Take the key in and out of the computer after installing the driver.
3. Make sure the application you are running is from a folder with nethasp.ini file.
4. Rename any existing NetHasp.ini configuration files and check whether the error returns. If it does not return, check that the correct parameters are written in the configuration file.
5. Check that there is at least one common protocol between the station running the protected application and the protocols loaded by the LM.
6. If the LM is on a different segment than the station, check the following:
   • Port 475 is open for communication in the routers and the firewalls in the network. Port 475 is the default communication port of the NetHasp.
   • Note that NetBios protocols cannot pass segments.
7. Busy network with a lot of noise can slow down communication and the search for the LM could reach a time-out. Use NetHasp.ini file to direct the application to the right computer, Download the file and replace with a text editor the IP address (marker with xx.xx.xx.xx) of the server, then place this file in C:\program Files\Optitex10\app folder (on some installation it may be different). If a busy network is the problem and the default configuration of the NetHasp.ini file does not work, try to increase the time-out length to overcome the time-out problems.
8. Try to Change nethastp.ini settings from broadcast enable to disable.

Failure To Add Modules On The Key

On some servers adding modules with codes to a key doesn't work. To solve this issue, install the key driver and LM on an other computer (temporarily), and add the missing modules there, then move the key back to the server.

Keywords

nethasp

---

The HASP License Manager returns the following error codes.

Error Codes

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 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.