March 22, 2011. ERDAS-Net Licensing 2011 has some new IPv6 v. IPv4 incompatibilities not seen in previous releases:
- (Windows XP/2003) ERDAS 2011 applications may be unable to use licenses hosted by ERDAS-Net 2010, while ERDAS 2010 applications may be unable to use licenses hosted by ERDAS-Net 2011. This only affects applications running on the same machine as the license server.
- (Windows Vista/7/2008) ERDAS 2010 applications stop getting licenses from ERDAS-Net 2011 when another FLEXnet-enabled license server (e.g., ArcGIS or XPro) is active. Even the ERDAS-Net License Administrator tool would report “Error retrieving license source, local” once the other license server was active.
These problems only occur on machines that are “dual-stack”, having both IPv4 and IPv6 addresses. Because the ERDAS-Net 2011 license server starts up on the IPv6 stack, older IPv4 applications (including the ERDAS-Net License Admin Tool itself), are unable to retrieve licenses from it. To date, this problem only affects applications running on the same machine as the license server--other remote machines do not seem to care.
To resolve the issues, please follow these steps according to the OS being used:
Windows XP
- Uninstall the 2011 ERDAS-Net Licensing Tools, reboot, and then install the 2010 ERDAS-Net Licensing Tools.
- Open the License Admin Tool and load the license via File->Load License. Close License Admin Tool.
- Open the file “erdasnet_LICENSE_PATH” located at C:\Documents and Settings\All Users\Application Data\ERDAS\Shared\Licensing using Microsoft WordPad. Delete all entries in the file and then add the following entry:
- Save the file and close Wordpad.
This will allow the user to license both 2011 and 2010 using the 2011 license file. User will also be able to view licensed features in the License Admin Tool.
Windows Vista/7/2008[R2]
On Windows Vista/7/2008[R2], the problem is a hidden port conflict. With ERDAS-Net 2011 running on port 27000 on the IPv6 stack, another IPv4-only license server is eligible to run on port 27000 on the IPv4 stack. In most cases this problem is occurring with the ArcGIS 10 license manager running on the same system ERDAS-Net 2011. Customers who were previously running ArcGIS 10 and ERDAS-Net 2010 all of sudden have connection issues when upgrading to ERDAS-Net 2011. This conflict can also occur with other FlexLM license managers, so it is best to determine which ports are being used by all FlexLM license managers and modify as necessary to ensure they are all running on unique ports. Here is how to modify the ERDAS-Net 2011 license for use on a different TCP port:
- Open the “LocalServerLicense.elf” file located at C:\Program Data\ERDAS\Shared\Licensing\Licenses\Floating-Licenses using Microsoft Wordpad.
- Edit the first line of the license file to include a port number. This example adds port 27001.
- Save the file.
- Open the Windows Services and Stop and Start the ERDAS-Net License Server service.
Please also ensure that you modify any firewall settings to allow communication on any TCP ports that are specified.