Neuralog Frequently Asked Questions - NeuraInstallation

How do I find out the EthernetID of my computer?

Neuralog software is often licensed to the EthernetID of your PC.  The EthernetID, or HostID, or Physical Ethernet Address, can be most easily found by running the utility below.

If the software is already installed and running:

The EthernetID is a 12 digit hex number, that is it is made up of the digits 0123456789abcdef and has exactly 12 characters.

Where can I find the latest FLEX lm versions? (lmgrd.exe, lmtools.exe, lmutil.exe)
    Get Latest FLEX lm
The following error occurs during my product installation: Move Data Process -105

What does this mead?

    The Move Data Process failure occurs when an application is already running your machine, causing the copy to fail. Make sure you have closed all Neuralog applications.

    The problem may also occur if you are updating an existing floating network installation and the Flexlm license server is running. Be sure to shut down the license server during the installation.

When starting my Neuralog product the following error occurs. No such feature exists. License path:... What does this mean?
    This error indicates that a valid feature line for the Neuralog product you are running does not exist in the license file the application sees. First notice that the license path is printed to the screen. Is this the location of the Neuralog license.dat file? If not place the license file there or read the other FAQ entries to determine how to change where the software looks.

    If this is the correct license file, open it in notepad and make sure this software product is included as a feature line. Feature lines look something like the following example:
          FEATURE NeuraMap lmgrd.nli 3.1 permanent uncounted...
    If your feature line has a product name of the form nds.map instead of NeuraMap, this is an older license. You will need to contact Neuralog for an updated product license.

    Be aware that altering your license.dat file may invalidate it, i.e., cause it to not work.

(PC) When starting my Neuralog product the following error occurs. Invalid host. The hostid of this system does not match the hostid specified in the license file. I am using a dongle (hardware key).
    This error is indicating that the software does not see the dongle specified in the license file. Make sure that you are using the correct dongle and that it is securely plugged in to the parallel port.

    If this is the case, then it is likely that the dongle driver is not installed. Dongle drivers are available on your CDROM in the /Pclicnse folder or are downloadable from www.neuralog.com SUPPORT section, utilities->Installation and Licensing. Download or copy the drivers folder. Then run Pclicnse/SentinelMedic/SentMed.exe. This utility will automatically determine the drivers you need and help you install them.

(PC) When starting my Neuralog product the following error occurs. Cannot find license file. The license files (or server network addresses) attempted are listed below... I know my license file is there.
    This message indicates the application cannot find the license.dat file. Neuralog products use the following order of precedence when looking for the license file.

    1. Check to see if the environment variable LMGRD.NLI_LICENSE_FILE has been set. If it has, use that license.dat.

    2. If #1 is not true, check to see if the environment variable LM_LICENSE_FILE has been set. If it has, use that license.dat. Note that this may have been set up by another software vendor using FLEXlm licensing.

    3. If #2 is not true, check to see if the environment variable NDS_HOME has been set. If it has, use that path to license.dat. This may have been set up with earlier product versions.

    4. If #3 is not true, use the NDS_HOME path stored in the registry to locate license.dat.

    By default the environment variables are not set and the registry entry NDS_HOME is used. This is normally your /nds directory. Make sure the license file is directly in /nds.

    If you are running multiple applications using FLEXlm, please use the recommended approach described in this FAQ to set up your licensing. This involves setting LMGRD.NLI_LICENSE_FILE to point to your license.dat.

I need to install a network license of my Neuralog product(s) on a license server that has other FLEXlm applications (other vendor license services) already running. What is the recommended approach?
    Use LMTOOLS to configure and launch the Neuralog license service on your Flexlm license server. Make sure you are logged on as administrator.

    The number 1 issue users deal with when running multiple FLEXlm services is getting each application to see the correct license file. One common approach to solving the problem is combining the license files to a single license.dat. The feature lines of each product reside in the single file. The approach is fine for knowledgeable users, but can make debugging difficult.

    The recommended solution is to set up a vendor-specific environment variable (EV) for each Flex application on each client machine. FLEXlm uses this EV as the primary location to look for that vendor's license.dat. For Neuralog products set the EV LMGRD.NLI_LICENSE_FILE to the value somepath/license.dat. This ensures that Neuralog products will use the correct license.dat file without affecting your other Flex applications.

How do I find out what my license key # is to get online updates?
    The license key # appears on the 'About' splash panel. To get there, start up the program and select Help -> About NeuraLog. All the information you will need is there.

    You can also request an update or see if you need an update by choosing Help->Support->Check for Updates... This process will determine whether an update and/or new license file is needed, and allow you to easily make the request.

When starting my Neuralog product the following error occurs. Invalid returned data from license server. What does this mean?
    This error indicates that the data from the license server returning to the client is invalid or the client has timed out while waiting for the data. Things to try/check.