LICENSE: Network License FAQ [18289]

This article applies to:

E-Prime 3.0

E-Prime 2.0

Detail
Currently E-Studio will not recognize the network hardware key if it is attached to the same computer. You must choose a computer on the network on which you will not want to use E-Studio - this is where you will attach your key. Note: this computer may be referred to as the server machine in subsequent paragraphs. The computer where you will be using E-Studio is called the client machine.

What must be installed on the server machine?
The drivers for the key must be installed on the server machine. If you would like to use any E-Prime application other than E-Studio, you may install E-Prime on the server computer; the E-Prime installation includes the hardware key drivers. If you do not plan to use E-Prime on the server machine at all, you can run HaspUserSetup.exe (see below) to install only the drivers. After installing the drivers, insert the hardware key into the computer.

After connecting the key, wait a minute or two before opening E-Studio on another network machine. The network usually requires a short adjustment period to recognize the key.

What must be installed on the client machine?
The full version of E-Prime 3.0 or 2.0 must be installed on the client machine in order to access E-Studio. Insert your E-Prime installation media and run through the installation wizard.

Troubleshooting

A "violation of license agreement" error message appears when I open E-Studio.
First, check the HASP License Manager Admin Control Center (ACC) at http://localhost:1947. The network key should appear on the HASP Keys page as a red key. The version number should be at least 3.21. If either of these requirements is not met, please read the rest of this document for suggestions.

The hardware key version number is listed as something other than 3.21 or later.
Run HaspFirmwareUpdate, which is available in the Support folder of your E-Prime installation media. This will update the firmware on the key to the latest version.

I cannot access the ACC on the Server and/or Client machine.

Install the latest HASP/LDK driver from the Gemalto Sentinel Customer Community on all applicable machines. This will install the copy protection drivers manually. After running through the default installation, restart your computer.

My network key does not appear on the ACC at http://localhost:1947 on the Client machine.
Make sure there is no antivirus software running on the machine. If there is, please be sure to disable it before using E-Studio. Next, install the latest HASP/LDK driver from the Gemalto Sentinel Customer Community. This will install the copy protection drivers manually. After running through the default installation, restart your computer.

 
My network key still does not appear on the ACC (http://localhost:1947) on the client machine, but does appear on the server machine.
First, open the ACC on the server machine and click on Configuration to the left. Navigate to the Access from Remote Clients tab. Make sure the "Allow Access from Remote Clients" box is checked and that there are no restrictions in the "Access Restrictions" field. Next, go to the Configuration page of the ACC on the client machine. Navigate to the Access to Remote License Managers tab. Make sure the first two boxes are checked ("Allow Access to Remote Licenses" and "Broadcast Search for Remote Licenses"). If the key still will not populate follow the step below to specify the server.

My client machines are connected through a proxy or are on different VLANs or subnets and cannot see the key.
Open the ACC on the client machine and go to the Configuration page. Navigate to the Access to Remote License Managers tab. Check the "Aggressive Search for Remote Licenses" box. If the key is still not recognized (after waiting a few minutes), enter the IP address or machine name of the server machine into the "Specify Search Parameters" field. This is the most aggressive way to establish communication with the network key.

My network key appears on the ACC on the client machine and the server machine, but I still get a "violation of license agreement" error.
Please run LicenseAdminDiag.exe (https://dev.pstnet.com/api/core/filetransfer?transferToken=jTZu3C0fvE01TjJM0FEwqQMfwbnOrOA2AtJIy-FoFQ0A8Lq9T9ZXQnL0skOCCRYGJa5zT6X22r3xRk3qhQqdjilRjhgulxGnyN7Zjzip2Pk7sl6j8dHqwxW4KV3-p7q-UR84H3srpXMOoDxA9KHl91p1OcWqhPgy0) and attach the generated files to a web support request (INFO: How to submit a support request and check the request's status [28276]).

I want to access the HASP License Manager Admin Control Center remotely.
You can access the ACC remotely by typing in the machine name rather than localhost. The name "localhost" is a reserved name for the computer where you are entering it; for example, if your machine name is PST000, entering "http://localhost:1947" on that machine will send you to the same place as if you had entered "http://PST000:1947". You can use this method to access the ACC of one computer while you are sitting at another computer. Keep in mind that the "Allow Remote Access to ACC" box must be checked on the Basic Settings tab of the Configuration page of the remote machine's ACC. Therefore, you will most likely have to visit the remote machine at least once in order to change that initial setting.

I want to use the same ACC settings for every computer on my network.
The hasplm.ini file stores all the information listed on the ACC. This file is stored in C:\Program Files\Common Files\Aladdin Shared\HASP\ and can be copied into the same folder on any number of machines. Copying the file to the other machines is your own responsibility. Note that any changes made through the ACC on the client machines will overwrite this file. To prevent end users from altering your settings, you can set a password for the ACC; password information will also be transferred when copying the ini file.

See Also:

LICENSE: How to Install a Perpetual Group License or a Network License [25285]