FLEXlm error -15,10 "Cannot connect to license server" or "WinSock: Connection refused"

Saturday, September 15, 2001

Topic:
For floating license trouble shooting:

Symptom:

When starting a Windows IDL or other RSI product session from a floating license client machine, you encounter an error message like the following:

    % LICENSE MANAGER: Cannot connect to license server
    The server (lmgrd) has not been started yet, or
    the wrong port@host or license file is being used, or the
    port or hostname in the license file has been changed.
    Feature: idl
    Server name: myserver
    License path: C:\Program Files\ITT\license\license.dat;C:\Program Files\ITT\license\*.lic
    FLEXnet error: -15,10. System Error: 10061 "WinSock: Connection refused"

Discussion:
This error indicates that the FLEXlm routines in the application are unable to make a TCP connection to the server and port specified in the license file. Possible causes/solutions for this behavior are listed below


1.) PROBLEM:
The wrong license file is being referenced by IDL.

SOLUTION:
Verify that the application is using the proper license file. Check the paths and spelling of the licenses listed in the "license path" indicated in the error message.


2.) PROBLEM:
The server machine specified in the license file is down;

SOLUTION:
Verify that specified server machine is up and reachable by executing another command that uses TCP, such as ping, from the client to the server. For example, if the IP address of the license server machine "myserver" is 123.456.789.0, open a DOS command prompt on the IDL client machine and issue the command:

     ping 123.456.789.0
or
     ping myserver

TCP must be available on both the client and the server machines in order to use a floating license. If network problems are suspected, contact your system administrator for assistance.


3.) PROBLEM:
The license manager service is running but the IDL vendor daemon specified in the
     DAEMON line of the license file (IDL_LMGRD.exe) is not running;

SOLUTION:
Check the license manager debug log file and run the lmstat command to try to determine if the vendor daemon is down and to get clues about how to resolve the problem=:

a.) Verify that the vendor daemon is running. Check the license manager debug log file that was specified when configuring the license manager.

b.) Examine the license manager debug log file to see if any problems are reported, particularly messages indicating that the vendor daemon has quit.

c.) Run lmstat -a from the server machine to verify that the vendor daemon is alive.

For example, if your IDL 6.4 installation is located at C:\Program Files\ITT\ IDL64 and license manager was started using a license file with the following SERVER line:

    SERVER myserver 00b012345678 1700

Open a DOS command prompt and issue the following commands.

    C:
    CD C:\Program Files\ITT\IDL64\bin\bin.x86
    LMUTIL LMSTAT -a -c 1700@myserver

Where 1700 is the number at the end of the SERVER line of the license file and "myserver" is the name of the license server machine as it appears in the license file.


4.) PROBLEM:
The host name in the license file is not recognized by the system;

SOLUTION:
If the license manager or the vendor daemon (idl_lmgrd) is down, make the necessary corrections to the license manager setup on the license server machine and then start or restart the FLEXlm license manager service on that server machine. (Note that the FLEXlm license manager service for an ITT license should only be started (only one instance), on the designated license server machine that is listed in the SERVER line of the license file.) Information about configuring, starting and stopping the FLEXlm license manager on Windows 2000 or XP can be found in the "License Management Guide" (license.pdf) in the IDL Online Manuals of your installation or on your product CD.


5.) PROBLEM:
The network between the client machine and the server machine is down.

SOLUTION:
Run lmstat -a (see item (3c) above) from the client machine to verify the connection from client to vendor daemon across the network. Also run lmdiag to get additional clues about a network related problems and how to resolve them in the context of this problem. For example:

    LMUTIL LMDIAG -C 1700@myserver


6.) PROBLEM:
TCP is not running on your machine.

SOLUTION:
From the client machine, try using telnet host port where host and port are the same as on the SERVER line in your license file. Using the example license and installation example above, open a DOS command prompt issue the following command:

    telnet myserver 1700

If a connection is established, the DOS prompt will not be returned since a TCP connection has been established with the license manager service.

However, if a connection is not established this may indicate that the license manager is not running properly or that there is a network communication problem between the client and the server machine. (Close the DOS window to end a telnet connection to the license manager.)

SOLUTION:

If there is no firewall up open the 'license.dat' file, in a plain text editor, and change the hostname to the IP address of the computer. For example, if the SERVER line in the license data file reads:

SERVER servername 0000123abcd 1700

... change the line to read:

SERVER 127.0.0.1 0000123abcd 1700




NOTE: If network configuration problems are suspected in causing the licensing problem, please contact your system administrator for assistance.


7.) PROBLEM:
There is a firewall on either the server system, client machine, or both that is enabled and preventing the connection.

SOLUTION:
Make sure that port 1700 is opened for TCP communication through any firewall that is enabled on the server or client machines. You may also need to define and open the port used by the vendor daemon, which is dynamically assigned when the license manager starts by default. To define this port, please see Tech Tip 1210Solution:
[Edit this field in the IDL-based Tech Tip Editor, v80]
Rate this article:
No rating
Related Topics: Licensing, Help Articles
Tags:

Number of views (7491)/Comments (0)

Please login or register to post comments.

FEATURED HELP ARTICLE

ENVI LiDAR Hotfix/Patch Available: Southern Hemisphere Projection Systems

11/14/2012

An issue regarding southern hemisphere projection systems has been addressed in the latest patch/hotfix ... more »

MOST POPULAR

© 2014 Exelis Visual Information Solutions