Using a VPN with ArcGIS License Manager prevents borrowing/returning and enterprise activation.
Last Published: August 25, 2014No Product Found
Bug ID Number
NIM053680
Submitted
February 2, 2010
Last Modified
June 5, 2024
Applies to
No Product Found
Version found
10.0 Beta
Status
Will Not Be Addressed
The development team has considered the issue or request and concluded it will not be addressed. The issue's Additional Information section may contain further explanation.
Additional Information
We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.
Workaround
Consuming licenses is fixed by applying this patch:
http://resources.arcgis.com/content/patches-and-service-packs?fa=viewPatch&PID=160&MetaID=1741#install
Borrowing remains an issue, see workarounds:
Workaround 1:
Also, set the FLEXLM_TIMEOUT value on the client side to 20000000 as indicated in the below article:
http://resources.arcgis.com/content/kbase?fa=articleShow&d=35659
Edit service.txt file to specify port range 27000 & 27001 as the port for the LMGRD and ARCGIS processes. See http://resources.arcgis.com/en/help/install-guides/license-manager/10.1/0079/00790000000w000000.htm for details
Workaround 2:
Disable any "Virtual Adapters" on the system. (See \\archive\Nimbus\ArcGIS\Licensing\NIM053680\flexera patch update 03-2010.doc for details.)
Workaround 3:
Borrow licenses from the corporate/local license manager when the remote system is at the site with the locally deployed license manager. Once borrowed, the license will remain valid regardless of connectivity for the duration of the defined borrow period. (License borrow period is configurable from 1-365 days)
Workaround 4:
Use Single Use Licenses for those systems that need to leverage borrowing for extended remote use.
Workaround 5:
Use Enterprise Activation Licenses for remote clients; and de-authorize those clients only before they are decommissioned.