Updated March 22, 2011.
1. Error Retrieving License Sources
2. Error with ERDAS hardware-key-based license file
3. License Borrowing
4. Symptom: Difficulty Returning Borrowed Licenses
5. Virtual Machines and System IDs
6. Error: "Reason: Services can not be queried, started or stopped as executable SC is not found at . "
7. Slow LAN, WAN, or VPN and ERDAS-Net Licensing
8. Error when loading license file: "String index out of range: -1"
9. Problem: The user can see the license server and the licenses from the License Admin Tool, but cannot gain access to a license when running ERDAS software, or the license may have been updated or changed but the user still sees the old license configuration.
10. IPv6 internet protocol inconsistencies
= = = = =
1. Error Retrieving License Sources
Occasionally, after installing a license, when you try to expand the License Sources view, an error occurs, "Error retrieving license sources...", with a follow-on reason message that may state several things, such as "Error creating the view...," "Loading Children...," "java.lang.NullPointerException," etc. Here is how to correct it:
First, try this:
1. Delete the file named ERDASNET_LICENSE_PATH located at C:\Documents and Settings\All Users\Application Data\ERDAS\Shared\Licensing.
2. Try to start your ERDAS software again.
If the error persists, then try:
1. Open the ERDAS-Net License Admin Tool (Start > All Programs > ERDAS > ERDAS-Net Licensing > License Administration) and remove the license sources.
a. Expand the License Sources list.
b. Highlight the source and select Server > Remove License Source.
c. Choose to delete license file if prompted or given the option.
d. Close the ERDAS-Net License Admin Tool.
2. Open the FLEXlm Tools located at C:\Program files\ERDAS\Shared\Licensing\Bin\NTx86\LMtools.exe.
a. Delete the ERDAS-NET service.
b. Close the FLEXlm Tools.
3. If there is an older 9.x license manager running, open the Windows Services (Start > Control Panel > Administrative Tools > Services) and stop the service named “ERDAS License Server.”
4. Delete the file named ERDASNET_LICENSE_PATH located at C:\Documents and Settings\All Users\Application Data\ERDAS\Shared\Licensing.
5. Retrieve the 9.3 license file and double click to install.
2. Error with ERDAS hardware-key-based license file
The most common error when self-licensing using a traditional ERDAS SafeNet hardware key is to truncate part of the system ID. For version 9.2 and earlier, an ERDAS hardware key reported a system ID like this: d1fb3ad2123fb. For version 9.3, the same hardware key reports this system ID: erdasnet=3ad21234.
The common mistake is to use "3ad21234" as the system ID rather than "erdasnet=3ad21234." If you self-generated a license this way, the license will have to be revoked and re-issued by ERDAS. Please send a technical support request for this that includes the incorrect and correct system IDs.
3. License Borrowing
a. ERDAS-Net licensing offers license borrowing. It is disabled by default. To enable it, please see the instructions.
b. A working network card is required on the borrowing computer for the duration of the borrow. Floating licenses require TCP/IP to work, and a working network card is required after borrowing, even when not connected to a network. If your network card is manually turned off or if it automatically turns itself off to save power, your borrowed license will not work.
c. 1. The lower-level prerequisite modules must be available for borrowing for the top level application to borrow licenses. This mostly pertains to ERDAS IMAGINE. Example: You have IMAGINE Professional. When editing the options file, you delete all lines except for IMAGINE Professional, and set the low-water mark to zero:
BORROW_LOWWATER improf 0
The borrow will fail. The license features for the lower-level IMAGINE Essentials and IMAGINE Advantage are also required for IMAGINE Professional to run, along with other features included in IMAGINE Professional, such as IMAGINE Radar Interpreter and unlimited ECW compression, i.e.:
BORROW_LOWWATER imess 0
BORROW_LOWWATER imadvan 0
BORROW_LOWWATER improf 0
BORROW_LOWWATER imradar 0
BORROW_LOWWATER imcomun 0
4. Symptom: Difficulty Returning Borrowed Licenses
In order to return borrowed licenses, you must have a working connection to the license server(s) from which the license(s) were borrowed. If you are unable to return borrowed licenses, even when the connection to the license servers is available, you can reset your own borrow state by renaming the following file:
c:\document and settings\all users\Application Data\ERDAS\shared\licensing\erdasnet_BORROW_STATUS.xml (Windows XP)
c:\ProgramData\ERDAS\shared\licensing\erdasnet_BORROW_STATUS.xml (Windows Vista)
You should only do this if you are unable to re-establish connection with the license server, or if the license server does not respond to your return request. Resetting this file only makes you eligible to borrow more licenses from an active server; it will not release any licenses reserved for you on an inactive server.
5. Virtual Machines and System IDs
ERDAS licensing does not support system IDs from virtual machines. ERDAS licensing is based upon unique system identifiers, and the virtual network adapters are not sufficiently unique. ERDAS software may be installed onto a Virtual Machine, but it must use a floating license from an actual (non-virtual) license server. Running a license server on a virtual machine is not supported.
6. Error: "Reason: Services can not be queried, started or stopped as executable SC is not found at . "
This error comes from trying to run ERDAS-Net licensing on Windows 2000. Windows 2000 is not supported.
7. Slow LAN, WAN, or VPN and ERDAS-Net Licensing
Using a fixed port number for a license server speeds up all requests made to the license server, since FLEXnet no longer has to scan the default port range of 27000 to 27009. Edit your license file to specify the fixed port number; otherwise the number may vary, depending upon what other license servers are running on your machine.
Microsoft Windows clients can also address the problem by adjusting the FLEXLM_TIMEOUT environment variable. The default time-out value is 100000 (measured in microseconds). Adjust this value to 200000 or 300000 to improve the likelihood of connecting to a distant license server. This also increases the time required for the software to fail when the license server is not available, particularly if you have not specified a fixed port number.
8. Error when loading license file: "String index out of range: -1"
October 4, 2010, update: This new procedure has proven most effective with this error. The previous procedure remains listed below.
New procedure:
1. Open Regedit and rename registry key as follows
HKEY_LOCAL_MACHINE\SOFTWARE\Aladdin Knowledge Systems\HASP\Driver\Installer
to
HKEY_LOCAL_MACHINE\SOFTWARE\Aladdin Knowledge Systems\HASP\Driver\Installer1
2. Close Regedit
3. Detach any HASP dongles from the machine.
4. Open the License Administration Tool and load license using File->Load License.
5. Open Regedit and rename registry key as follows:
HKEY_LOCAL_MACHINE\SOFTWARE\Aladdin Knowledge Systems\HASP\Driver\Installer1
to
HKEY_LOCAL_MACHINE\SOFTWARE\Aladdin Knowledge Systems\HASP\Driver\Installer
6. Re-attach HASP dongles.
= = = = =
Previous procedure:
This error is caused by a conflict between certain versions of the Aladdin HASP dongle driver and FLEXnet licensing. This can often be resolved by updating your Aladdin HASP driver to the latest version, available from http://www.aladdin.com/support/hasp/enduser.aspx#lm. Select the latest NetHASP License Manager version 8.32.5.40. It is the first item to download in the NetHASP License Manager Downloads section. During the installation, choose to install as a service and to allow the HASP drivers to be updated. When asked if you want to start the service, choose “Yes”. Restart the system and check the ERDAS-Net license manager.
If this procedure does not work, please completely remove all HASP drivers, install ERDAS-Net licensing and ERDAS software, then reinstall HASP drivers (if in use).
9. Problem: The user can see the license server and the licenses from the License Admin Tool, but cannot gain access to a license when running ERDAS software, or the license may have been updated or changed but the user still sees the old license configuration.
Pertains to Windows 7, Vista, and Server 2008.
On Windows 7 and Vista operating systems, the VirtualStore folder creation is a ‘security innovation’ from Windows for Windows 7, Vista, and Server 2008. It can be created from user accounts that have administrative privileges. It is created when the IMAGINE application fails to administer sufficient security to configure the licensing task properly.
In this case, C:\Users\%username%\AppData\Local\VirtualStore\VirtualStore\ERDAS is created when the IMAGINE application evokes the licensing request. The IMAGINE application does not apply the security needed to administer licensing for the Default User, and as a result the VirtualStore/ERDAS folder for this user is created. The ERDAS License Manager (ERDAS-Net License Admin Tool) application does not have this issue when configuring licensing.
This can happen when a user attempts starts an IMAGINE session when IMAGINE hasn’t been licensed yet for the Default User. When no license is available, the IMAGINE application attempts to configure the licensing. At this point if the user correctly sets up the licensing, then IMAGINE should start for the user. But licensing is only available for this user because only the user’s VirtualStore/ERDAS folder is consulted when the user is starting IMAGINE.
If, however, the user specifies incorrect licensing information in IMAGINE, that incorrect information will be stored in the C:\Users\%username%\AppData\Local\VirtualStore\ERDAS\shared\licensing\erdasnet_LICENSE_PATH file, and the user will be unable to operate the application. Removing the ERDAS directory from the VirtualStore directory should alleviate the problem
This problem has been fixed in ERDAS 2011 software.
10. IPv6 internet protocol inconsistencies