Go home
Mobius products Mobius Bulletin Board/Forum Order our products
Go home Mobius news Mobius resellers Take a tour Frequently asked questions Industry links Contact information About the Mobius team


Welcome

This page has been provided to assist you when you experience problems with the dongle (HASP software license key) or with the network License Manager.

The HASP software comes from a company called Aladdin Knowledge Systems.  You may like to visit their Web site to look for latest drivers in case the solutions we have listed below do not solve your problem.

http://www.aladdin.com/support/hasp/enduser.asp

Latest drivers:

Download the latest dongle drivers: click here.
Download the latest License Manager software: Click here.

What sort of problem are you experiencing?

1.  Have you just upgraded to Vista, or purchased a PC with Vista installed?  Click here.
2.  Have you just upgraded to XP SP2 and the dongle does not seem to work?  Click here
3.  Do you have an old version (pre 2.3) of iLearnVibration and you have just moved it to an XP machine?  Click here
4.  Do you have a networked system, using the License Manager?  Click here
5.  Did the dongle drivers fail to load during the installation?  Click here
6.  General dongle problems? Click here

Please scroll down to find the solution that meets your needs.

XP SP2 Dongle problems

Have you just upgraded to Windows XP SP2 (Service Pack 2) (or are you installing the system on a new computer)?  When you attach the USB dongle, does the light inside the dongle go on and then turn off immediately?  In that case, please download the latest dongle drivers from the Aladdin Knowledge Systems dongle company.

Click here to download the installer

XP or Windows 2000 installation problem

If you have iLearnVibration Version 1.X, Version 2.0 or Version 2.1, there is a very good chance that the system will not install on a Windows XP or Windows 2000 computer - thanks to the fact that the dongle drivers from Aladdin Knowledge Systems were not compatible.

If you click on this link (to another Web page) and follow the directions, you will be able to complete the installation.  The system will then run successfully.

Dongle driver installation problem

Download the latest dongle drivers: click here.

If the dongle driver did not install correctly during the system installation (perhaps you saw a message that the installation of the dongle driver was unsuccessful), please download this file [287 kB] and run it.

If you need to update or re-install the dongle driver, please click this link [2.4 MB].  Simply unzip the file, run the program, and follow the on-screen instructions.

Version: 2.1.23.03.03
If you receive an error during installation "DLL library cannot be found" and then a message like "C:/windows/temp/HINSTD.DLL cannot be found", then you need to download this file [1.9 MB], unzip and run it, and then repeat the installation via the CD. 
 

Dongle operation problem

If it appears as if the dongle is not working correctly, here are two programs that may help:

DongleCheck [3 kB] is a simple program that will tell you if a dongle is connected to the computer.

Aladdin_Diagnostics.zip [4.6 MB] is a diagnostic program supplied by the dongle manufacturer.  It will check if a dongle is present, and more.  Download the file, unzip it, and run it.  The "DiagnostiX" program will be installed.  Select Start - Aladdin - DiagnostiX to run the program.

SecurityCheck.zip [1.38 MB] is a diagnostic program I created to test if the dongle is present and read the license information.

Dongle is not programmed

If your dongle is not programmed at all, or the programming needs to be changed (i.e. it is not set up to license the software you have purchased), please one of the following links to download the DongleClient program.

If you will run DongleClient on a computer with iLearnInteractive installed [166 kB]

If iLearnInteractive is not installed on the computer [1.6 MB]

Simply unzip the files and run them.  The document Dongle client.pdf (a part of the download) will explain the operation.

Network license manager problem

If the client iLearnVibration system seems to be unable to communicate with the License Manager, it could be because the client cannot "find" the LM on the network.  By default, the client iLearnVibration system sends a message out to the entire network looking for the LM.  If the LM hears the request, they will begin to communicate.  For a number of reasons, it may not hear that request.  You can create a NetHASP.ini file which tells the client where to find the LM.  On a TCP/IP network you can simply enter an IP address or the name of the computer running the LM software.

Click here to view and download sample nethasp.ini files for different operating systems and network configurations.  You will find other useful information at this site (Aladdin Knowledge Systems - the developer of the dongles and License Manager).

Click here [5.3 MB] to download the latest version of the License Manager software (this program is only installed on the computer with the red dongle).

Click here [4.6 MB] to download the DiagnostiX program (described above) - it will test to see if the dongle and License Manager are installed properly.  It will also help you to set up the nethasp.ini file (designed to improve the way the client computer (the one running iLearnInteractive) communicates with the server (running the License Manager program)).

Click here [800 kB] to download a new interface between the iLearn products and the License manager.  This may help to solve certain communication problems between the iLearn product and the License manager.

Click here [1.38 MB] to download a new diagnostic program "SecurityCheck" that will search for the License Manager and determine which applications have been licensed.

Click here to download the HASP manual [2.58 MB] which describes how to set up the nethasp.ini file.  This is helpful if iLearnInteractive cannot find the License Manager.

Click here to download a help file [20 kB] for the License Manager.  It lists command line parameters and an ini file that can be used to configure the License Manager program.  This will also help if iLearnInteractive cannot find the License Manager.

Here is some information directly from Aladdin:

Aladdin Support Technote

Solving common NetHasp problems
Problem:
I am getting an error from my NetHasp protected application and the application does not run. How can I solve the problem?

 
Cause:
An NetHasp error can occur while working in a network environment. This errors is usually due to the following:
 
    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.
    5. Busy network with a lot of noise, slowing down the communication to the extent that application reaches time-outs and returns an error.
    6. Incompatible version of the LM.
    7. Two or more LMs are Conflicting due to similar Identities.
    8. Hardware problem or conflict, two or more HASP keys are connected and a transparency problem raises.
    9. No Hasp is connected to the computer.
    10. The content of the HASP key is missing the requested Program Number.
    11. Too many users are connected to the HASP, or the user login request exceeds the number of authorized stations running simultaneously, specified in the HASP memory.

 
Solution:
Error 8- While trying to connect to the LM, the NetHasp protected application reached the default time-out. This problem can occur due to the reasons specified in the cause section in paragraphs 2 and 5.
Please refer to the following technote to solve the problem.

Error 15- This error will appear after the search for the LM was ended without success in locating a LM. This problem can occur due to the reasons specified in the cause section in paragraphs 1,2,3,4 and 5.
Please refer to the following technote to solve the problem.

Error 19- The LM returned this error because it received wrong inputs. This problem can occur due to the reasons specified in the cause section in paragraphs 1 and 3. This error means that there is a Syntax Error in the "NetHasp.ini" configuration file. Please download a preconfigured "NetHasp.ini" from Aladdins web site or review the syntax in the your NetHasp.ini file.

Error 129- The request form the LM has arrived to the LM but encountered problems. This problem can occur due to the reasons specified in the cause section in paragraphs 1,3,8 and 9. To solve this problem, please refer to the following technote.

Error 133- The current Login request exceeds the number of stations which may run the application simultaneously. You will have to wait until one of users accessing the LM with the protected application logs off.
If there are records of fictitious users logged in the LM, you will need to restart the LM to free the fictitious users. To view the users logged in the LM, use the Aladdin Monitor.

Error 150- No HASP License Manager with the assigned name was found. This error is returned by the "SetServerByName service." Make sure that the LM was installed with the correct Server name.
If you are not using the "SetServerByName service" in your source code, and you are using a "NetHasp.ini" file to call the LM by name, please verify that the correct Server name is specified in the configuration file.

Error 151- Two or more different HASP License Managers with the assigned name were found. This error is returned by the SetServerByName service.

If the "SetServerByName service" was incorporated within your application source code, there is no way to run two LMs with the same name on the same network with a 100% guarantee that the application will succeed in the login process.
Please use both keys (if they do not have the same passwords) on a single LM by daisy chaining the NetHasp's keys, or by combining them into one key by using the FAS with different program numbers (if they do have the same passwords).

If the "SetServerByName service" was not incorporated within your application source code and you are using a "NetHasp.ini" file to call the LM by name, please change one of the LM's names and configure the application to work with the appropriate LM name.

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

For Security issues, backwards compatibility was not continued if you incorporated new API functions (from HASP CD 8.1). The new API requires an LM version 8.01 and above. Please upgrade the installed LM.
A new LM can be downloaded here.

Tip: Create a simple Win32 / Win16 Enveloped application (depending on the type of your application) such as Windows Notepad with the Envelope that you used to protect your application and create another one with the latest Envelope to rule out the possibility that the problem is your application and not the network.

If the error you are encounering was not mentioned in this technote, please refer to the "NetHasp Status Codes" technote.
Aladdin Support Technote

NetHasp Error 15
Problem:
While trying to run my NetHasp protected application, I receive a HASP Error message 15 : "No active HASP License Manager was found."

 
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.

 
Solution:
    1. 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.
    2. Check that there is at least one common protocol between the station running the protected application and the protocols loaded by the LM.
    3. 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.
    4. 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. 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.
    5. It is recommended to wrap a Win32 / Win16 application with the HASP Envelope for network use and try to run it. You might find that the login process passes. In this situation, you should try to use newer versions of Envelope or API objects than the ones used in your protected application.
Aladdin Support Technote

HASP License Manager: Testing TCP/IP networks for proper communication
Problem:
Communication between the protected application and the License Manager fails.

 
Cause:
The underlying communication between the computers may be misconfigured or faulty.

The default communication port for HASP LM is 475. In some cases, this port may be blocked by firewalls/port filters or routers.

 
Solution:
The best way to locate and fix such problems is to consult the local network administrator is , but in some cases this is not an option.

To be able to use NetHASP protected software through firewalls, make sure that port 475 is not blocked.
Alternatively, it is possible to specify another port in configuration file of the client application and in the License Manager (using -portnum switch), but this is not the most recommended solution since other network traffic may overload the License Manager.

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.

If the communication works fine, check a test application mentioned such as Aladdin DiagnostiX with a nethasp.ini file configured to use the exact IP address of the LM. If this tests works well, but the protected application fails, the problem may be related to implementation issue. In this case, the software vendor should contact Aladdin's support or the support of the local HASP distributor.

 
Background:
See related HASP KB technotes: