|ARM Technical Support Knowledge Articles|
Floating license failures can occur with ARM Developer Suite (ADS) versions 1.2, 1.2.1, and RealView Compilation Tools (RVCT) version 1.2 running on Windows clients (ARM tools that incorporate FLEXlm 7.2 libraries). These failures appear as a FLEXlm -12,122 error.
Assuming that your client-server network communications are otherwise working (for instance, you can ping the server from the client), the cause of these failures is the interaction between the FLEXlm components linked into the ARM tools and certain software which can lead to Windows TCP/IP stack problems on the client. These particular problems are specific to the FLEXlm version 7.2 as used by ADS v1.2x and RVCT v1.2 and do not affect any other ARM tools.
Upgrading the FLEXlm server will not help. The problem lies within FLEXlm client code incorporated into the ARM tools mentioned above. This client code cannot be upgraded in any way.
The following are known to cause problems:
Each of these is explained below.
The antivirus software on the client may be causing problems with the TCP/IP stack.
Try uninstalling (rather than simply disabling) the antivirus software on the client computer and attempting the license checkout again. Macrovision state that particular configurations of the antivirus or firewall software can cause problems with FLEXlm 7.2.
In particular, there are known interactions between McAfee software (VirusScan7, Internet Security 5, and Firewall 4) and FLEXlm. This is fully described in the McAfee knowledge base article 60985.
McAfee recommend upgrading the McAfee software, or uninstalling it. Disabling the software is not sufficient. We have found that removing McAfee VirusScan 7 does not necessarily resolve the licensing problem without a TCP/IP stack reset (see 4 below).
There are known issues with the Microsoft ISA client firewall. The solution from Macrovision is to remove this firewall software; however we have found that if this software is installed it must be enabled for license checkouts to succeed.
We believe that certain “Spyware” can cause the -12,122 failure. Finding and removing spyware may fix the problem.
Removing then reinstalling the TCP/IP protocol on Windows has been seen to fix the problem. This carries some risk to your system so you may want to create a backup, or a Windows XP system restore point.
On Windows 2000, you can uninstall and re-install the TCP/IP drivers to clear the stack.
On Windows XP you will need to modify the registry to clear the TCP/IP stack, as you cannot uninstall the TCP/IP drivers.
Save your current registry settings. Open the registry editor (Start->Run...regedit). Open this registry branch:
Then select Registry -> Export Registry File.
Reset the TCP/IP stack. In Windows XP this can be done using the "netsh" command:
netsh int ip reset [log_file_name]
This is fully described in the Microsoft knowledge base article 299357:
On Windows XP you may also have corrupted Winsock2 registry keys. Corrupted keys may cause networking problems. To resolve this, you need to first delete the corrupted keys and then reinstall the TCP/IP protocol.
To delete the corrupted registry keys:
Note: Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.
To install TCP/IP:
Further information on Winsock2 registry key corruption can be found in the Microsoft knowledge base article 811259:
If after attempting all of the above you are still unable to successfully check out a license, please contact ARM License Support (email@example.com) with details of your product serial number, operating system and what happened when you tried the suggested fixes.
Article last edited on: 2008-09-09 15:47:42
Did you find this article helpful? Yes No
How can we improve this article?