| Copyright © 2002-2007 ARM Limited. All rights reserved. | ARM DUI 0209G |
| Non-Confidential | |
 PDF version | |
| Home > Frequently Asked Questions about Licensing > Problems with client configuration > Problems communicating with the server |
| |||
| Home > Frequently Asked Questions about Licensing > Problems with client configuration > Problems communicating with the server | |||
If you are using ARM development tools with a floating license, your workstation must be able to communicate with a server running FLEXnet server software. If such communication cannot be established, a commonly reported FLEXnet error code on the client is -15. Possible reasons for this are:
the wrong license file is being referenced by the application program
the server machine or machines specified in the license file are not running
you are using the wrong port@host information
the vendor daemon specified in the license file is not running
the hostname in the license file is not recognized by the system
the network between the client machine and the server machine is down
To solve these issues, refer to Chapter 5 Configuring a Client to Use a License Server and the Tools Licensing FAQs on the ARM Technical Support website.
You can try running tests on your server or client computers to identify possible causes of the failure:
Try running the lmutil
lmdiag utility, which is designed primarily for this purpose.
Verify that the application is referencing the correct license file.
Verify that the vendor daemon, armlmd,
is running (you can use ps on the server to look
for it on Unix/Linux, or the Windows Task Manager).
Examine the server log file to see if any problems are reported, particularly messages indicating that the vendor daemon has quit.
Run lmutil lmstat -a on the server
machine to verify that the vendor daemon is alive.
Run lmutil lmstat -a on the client
machine to verify the connection from client to vendor daemon across
the network.
If none of the above tests identifies the cause of the licensing
failure, check whether your client machine can communicate to the
server via TCP/IP using a utility such as ping.
If this fails then it is possible that communication is being blocked
between the server and client.
Your license server and client may be on opposite sides of a firewall. If so, you must configure the firewall to allow access to fixed ports for both the lmgrd and armlmd license daemons. Define these ports in the server license file by modifying the top of the license file as shown, substituting your own values:
SERVER myserver server_hostid 8224
VENDOR armlmd port=portnumber
If your license server and client are on different subnets, then using the server’s fully qualified domain name or IP address may solve the problem. Using the IP address should circumvent issues surrounding domain name resolution.
There is a character length limit for server hostnames used in the license files. For FLEXnet 8.1b and older, this limit is 32 characters. If you are using newer versions of FLEXnet, the limit is 64 characters. Should your license server name be too long, you should use the server’s IP address in the license file and client license environment variable instead of the hostname.
You might encounter intermittent licensing failures if your server is under very heavy load, for example, if you use automated build scripts. These failures can be caused by intermittent networking failures. The current versions of the ARM development tools are more resilient with respect to such temporary network interruptions. Users of older tools should consider adding retry capability to their build scripts to work around the behaviour.
| Copyright © 2002-2007 ARM Limited. All rights reserved. | ARM DUI 0209G |
| Non-Confidential | |
| PDF version | |
| Home > Frequently Asked Questions about Licensing > Problems with client configuration > Problems communicating with the server |