Table of Contents
This chapter lists problems and error messages that you may encounter while setting up licensing. After each situation description or error message is the user action required to correct the problem.
For more troubleshooting information, see the FLEXnet Licensing End User Guide (accessible from the ANSLIC_ADMIN utility) .
The following troubleshooting topics are available:
Use the following suggestions to display or generate additional error messages and debugging information.
Set the ANS_FLEXLM_DEBUG environment variable to display debugging information. You can choose from two levels of detail: 1: basic licensing debugging information is displayed and 2: All licensing debugging information is displayed. The default is to show no licensing debugging information. You will not want to keep this environment variable set all the time because it will generate a large quantity of information.
If a licdebug file already exists and is dated today, the information is appended. If it is dated before today, the existing file will be renamed with a .old extension and a new file will be started.
The licdebug file resides in the directory specified by the TEMP environment variable (Windows) or in the $HOME directory (UNIX). The licdebug filename will vary depending on the product:
ANSYS: licdebug.ans.110.out
ANSYS Workbench: licdebug.wb.110.out
ANSYS LS-DYNA: licdebug.dyna.110.out
Connection functionality: licdebug.anscon.110.out
ANSYS CFX: licdebug.cfx.110.out
ANSYS ICEM (includes AI*Environment): licdebug.icem.110.out
ANSYS Thermal applications: licdebug.hti.110.out
ANSYS CADOE applications: licdebug.cadoe.110.out
ANSYS DesignModeler: licdebug.dm.110.out
ANSYS Part Manager (used for ANSYS Workbench Geometry Interfaces): licdebug.pm.110.out
ANSYS borrow utility: licdebug.ab.110.out
The directory specified by the TEMP environment variable may be hidden on your system. To view the directory and file, click on My Computer. Choose Tools from the menu, and then click on Folder options. Click on the View tab and select Show hidden files and folders. Click OK.
Set the ANS_FLEXLM_LMSGS environment variable to control whether error messages appear in long or short format. By default, when the ANS_FLEXLM_DEBUG environment variable is NOT set, ANSYS, Inc. displays error messages in short format. Set this environment variable to a value other than 0 (zero) to display the long format. Long messages are automatically displayed when the ANS_FLEXLM_DEBUG environment variable is set, even if ANS_FLEXLM_LMSGS is not set.
Set the ANS_FLEXLM_ENABLE_FLEX_DIAG environment variable to 1 to enable the use of FLEXLM_DIAGNOSTICS for ANSYS, Inc. products.
Set the FLEXLM_DIAGNOSTICS environment variable to a value of 1, 2, or 3, where 3 provides the most debugging information. You should set this environment variable only under the direction of Macrovision's technical support. For more information on this environment variable, see the FLEXnet Licensing End User Guide (accessible from the ANSLIC_ADMIN utility) .
If after following these suggestions, the resulting debug information does not make sense, try these suggestions:
Confirm that the license manager was restarted or the license file was reread after any changes were made to the license file. If the user did not make any changes to the license file for the server, check the date/time that it was last changed. Get the relevant path information from the debug output. Also, confirm that the same path is being used.
Try restarting the license manager and then attempt to run again. See if the same situation occurs.
If the user put a license key in a license file but is not seeing it even after restarting the license manager, confirm that the correct license file is being used to start the daemon/service. In this case, neither the client application nor the daemon/service is using the changed file.
If the license.dat file is at the end of the path and it is a license file that uses the license manager daemon/service, then confirm that the license manager is started with the same path as the license.dat file's path. The license manager could be looking at one file in the client application but the license manager daemon/service was started with another file.
You can use the Gather Diagnostic Information option of the ANSLIC_ADMIN utility to query the system for various pieces of information that may be needed for troubleshooting certain problems. The underlying utility, ansys_pid, collects information about the system as well as about ANSYS licenses.
ansys_pid sends all of the information that it collects to the log area. At times it may be necessary to provide the information for technical support. Use the Write to File button at the bottom of the ANSLIC_ADMIN to write a file. Then forward the file to the appropriate person.
This section describes problems you may encounter when setting up licensing or running an ANSYS product, as well as actions you can take to correct the problems.
If the license manager will not start, perform the tests that are listed below. Perform the tests in the order that they are listed.
Check the license.log file in the licensing directory on the license server for errors. See the remainder of this chapter for a list of possible errors and their resolutions.
Verify that TCP/IP is installed and configured correctly. Verify that the IP address is static. See Communications Requirements for information about configuring TCP/IP.
Verify that the hostid has not changed. If the hostid has changed, you must obtain a new license.
Windows Pentium III Systems. The version of FLEXlm used at ANSYS Release 11.0 no longer supports using a CPU ID as the hostid. As a result, if you are using a Windows Pentium III system as a license server, you will need to obtain a new license file to be able to run this release. To obtain your new license, run the Register License Server Information option on the ANSLIC_ADMIN utility on the system you have designated as your license server. Send the resulting file LICSERVER.INFO to your ANSYS sales representative. We will then supply you with a new license file.
Three-Server Environment. In a three-server environment, you could also see the following message when you start the first of the three servers:
***Attempting to start the license manager...
Start the License Manager status:
The license manager failed to start.
You may examine the license log file for more information or possible errors (by clicking the 'View Status/Diagnostic Options' button). Additionally, you can reference the Troubleshooting section in the ANSYS Licensing Guide for more details.
NOTE: The currently-installed license file is a three-server license file. With three-server license files, the license manager will not fully start until at least two of the three license servers are running.
This message results when a quorum of servers (2 of the 3) are not yet started. Start the other servers, or verify that they are already started. When at least two of the three servers are started, you will see the status window of this server change to reflect that it is now running. Do NOT attempt to stop the license manager by pressing the Stop the License Manager button.
If you verify that at least two servers are started and you still see this message, and the status window does not update to running in a reasonable time, follow the three steps noted above in License Manager Will Not Start.
When you see this message, do NOT press the Start the License Manager button again. Doing so will cause another copy of the lmgrd license manager daemon/service to start without the corresponding ansyslmd vendor daemon/service and will require you to carefully remove the extra ANSYS lmgrd manually.
When you attempt to stop the license manager in a three-server environment, the license manager does not stop immediately. You will see a message stating that the currently-installed license file is a three-server license file. With three-server license files, the license manager could take 60 seconds or longer to successfully stop. Wait at least 60 seconds. When the license manager has successfully stopped, the status window will show that it is stopped.
On Windows systems, you may see unexpected error messages in the licensing log file when you shut down the license manager via Services or via the ANSLIC_ADMIN utility. Messages similar to the following could appear:
13:47:49 (lmgrd) Shutting down ansyslmd pid=1860 because of signal 15
13:47:49 (lmgrd) Can't connect to the license server system. Shutdown ansyslmd failed.
13:47:49 ((lmgrd)) 13:47:49 Loop info:(lmgrd) Cannot read data from license server system. (-16,10009:10054 "WinSock: Connection reset by peer")
MT:0 VD_HB:5913:47:49 (lmgrd) reset:0Can't shutdown the license server system. Shutdown ansyslmd failed. clients:013:47:49 (lmgrd) fd's:0EXITING DUE TO SIGNAL 15
13:47:49 (lmgrd) ansyslmd exited with status 58 ()
13:47:49 (lmgrd) Since this is an unknown status, license server
13:47:49 (lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon.
13:47:49 (lmgrd) EXITING DUE TO SIGNAL 1
13:47:49 (lmgrd) Can't remove statfile C:\Documents and Settings\All Users\Application Data\Macrovision\FLEXlm\lmgrd.620: errno No such file or directory
These or similar messages in the log file can be safely ignored in most cases. You can verify that the service is shown as stopped, and that the two lmgrd processes and the ansyslmd process are stopped via Task Manager.
If the license manager appears to start but you cannot check out any licenses, perform the tests that are listed below. Perform the tests in the order that they are listed.
Verify that the license.log file exists in the licensing directory on the license server machine(s). Note that license.log in the licensing directory is the default location of this file. To see whether the file's location has been changed, choose Modify Startup Options on the ANSLIC_ADMIN utility on UNIX. On Windows, run the LMTOOLS utility in the ANSYS FLEXlm License Manager folder and choose the Configure Services tab. Check the name in the "License log file" field. If the license.log file does not exist or has zero length, verify the write permissions on the directory and file.
On the license server machine(s), review the license.log file for error messages. See the remainder of this chapter for a list of possible errors and their resolutions.
If you are running in a three-server environment and ANSYS program jobs abort when one of the license managers goes down, perform the tests that are listed below. Perform the tests in the order that they are listed.
If this problem persists after you perform the steps below, you may want to consider switching to a single-server environment.
When using a three-server environment, we strongly recommend that all three servers be on the same subnet. If this is not the case, you should consider using three machines which are in the same physical location and are on the same subnet.
Verify that two of the three license managers are still running. Use the ANSLIC_ADMIN utility (Display the License Status). If the license manager is not already running on all servers, start it on all of them.
Check the ansyslmd.ini file in the licensing directory to make sure the server specification is correct.
Check to see whether the ANSYSLMD_LICENSE_FILE or LM_LICENSE_FILE environment variable is set. If it is, verify that the settings are correct.
Verify that the same license file exists on all three license servers in the licensing directory. The hostnames of all three servers must appear in these files and in the same order. If the license files are not the same on all three servers, make corrections as necessary and restart the license manager.
Verify that the date and time on all license servers are consistent and correct. Make corrections as necessary and restart the license manager.
Verify that the hostid has not changed on any of the license servers. If any hostid has changed, you need to obtain and install new licenses on all license servers.
Verify that the license manager and utilities are installed locally on each license server. If not, run the installation from the product CD and choose to install the license server only. See the installation manual for your product and platform for more information.
Verify that the ansyslmd.opt files match exactly on all three license servers.
Check the license.log file for error messages. See the remainder of this chapter for a list of possible errors and their resolutions.
On Windows 2000 systems only, if the ethernet address shows 12 zeroes when you view it (using the LMTOOLS utility in the ANSYS FLEXlm License Manager folder on Windows), the network cable has been removed. To correct, re-connect the network cable.
On Windows, if the license manager starts and licenses can be taken from the license server, but the licensing log file is not written, check the Administrator account. Verify that the Administrator (as well as the individual user) has write privileges to the directory where the log file is to be written.
If queuing does not work, refer to the following list of possible causes and corrections:
The license manager is down. In this case, use ANSLIC_ADMIN to start the license manager.
The hostname is mistyped in the ansyslmd.ini file or the ANSYSLMD_LICENSE_FILE or LM_LICENSE_FILE environment variables. If so, correct the name and retry.
You are not licensed for the requested feature. In this case, request a product for which you are licensed.
All licenses for the requested feature are reserved in the license options file. If so, have the license administrator correct the license options file.
The user is excluded via the license options file from using the licenses for the feature(s) that are installed on this machine.
The License Queuing option may not be available on all products.
The FLEXlm utility lmcksum may give misleading information. Do not rely on its results to verify the accuracy of your license file.
If the launcher takes an excessively long time to startup (Windows only), make sure the hostnames in the ansyslmd.ini file and in the ANSYSLMD_LICENSE_FILE and the LM_LICENSE_FILE environment variables are typed correctly and that the hosts specified by the hostnames exist. Replacing hostnames with IP addresses may improve the speed as well. Also verify that the port number is correct.
If the ANSYS Product Launcher does not use the product specified by the ANSYS110_PRODUCT environment variable the first time that the launcher is run, you may need to clear your profiles and settings. In the launcher, choose Options >Delete All Settings/Profiles. This option will remove any profiles you have saved for this release, and revert back to using the ANSYS110_PRODUCT setting. Please see the discussion on Launcher Menu Options in the Operations Guide for more details on using the Delete All Settings/Profiles option before choosing this option.
Attempting to shutdown the ANSYS FLEXlm license manager ... Cannot find license utilities in <dir>. Please enter the directory where the ANSYS files currently reside.
If you see the above message, the installation procedure cannot find the valid utilities to stop the license manager. You should exit the installation, stop the license manager (via the ANSLIC_ADMIN utility), and then rerun the install. This is most likely a problem if the system has changed ANSYS platform names or if the shared_files directory was removed without shutting down the license manager.
If the ANSLIC_ADMIN utility is not available to shutdown the license manager, you may have uninstalled ANSYS, inadvertently leaving an ansyslmd and an lmgrd process running on the system. These processes will be stopped when you reboot your system. You can also stop these processes manually, but use extreme caution, because other products that use the FLEXlm license manager will also have lmgrd processes running. If you do want to stop an lmgrd process, use the ps command to find the ANSYS lmgrd process. Do not use kill -9 (on UNIX systems) to shut down the license manager. If you must use kill, omit the -9 option.
***Licensing files currently installed for <platform> are more recent than those on the installation media. The <platform> files will not be installed and will be deselected.
You will get this message if you install an earlier version of the product after a later version. The latest version of the license manager should always be run. If you feel the date was calculated incorrectly and want to install anyway, rerun the license manager installation using the -nodatecheck command argument. Use caution when using this option, however, because installing an older version of the files can prevent your product licensing from working correctly.
Some messages that you see from the launcher are related to product licensing. These messages follow. For additional launcher error messages, see the Troubleshooting section of the ANSYS, Inc. Installation Guide for your platform.
***Unable to retrieve any valid licenses for <simulation environment.> Please see the ANSYS, Inc. Licensing Guide's Troubleshooting section for more information.
***Required <Product> license was not found. Therefore, simulation environment simulation environment will not be available.
***Could not initialize FLEXlm licensing.
***Error: No license path found.
***No licensed products found.
***No products available for this simulation environment.
***Unable to load profile <name> because license <product> is not available. However, simulation environment <simulation environment> was selected.
***License list unavailable. [ANSYS Workbench Products Only]
If you see any of the above messages (or any similar licensing error messages), the launcher has encountered an error while trying to find or retrieve a license. Possible causes are the license manager is not running, no licenses were found, or the existing licenses have expired. Also check the license manager log file in the licensing directory. If any of these messages appear, perform the tests that are listed below in the order presented:
Use the ANSLIC_ADMIN utility to verify that the license manager is running. Choose Display the License Status. If you are running in a three-server environment, verify that two of the three servers are running.
Verify that the license manager is running. If the license manager is not running, start it on the license server machine(s). Check the license.log file on each license server for errors.
Run ANSYS from a command prompt to check for additional error messages. (Use the -p command modifier to specify the correct product name. See Product Variable Table for details.)
Example (Windows):
"C:\Program Files\Ansys Inc\V110\ANSYS\bin\intel\ansys110" -p ane3
Check the ANSYS Output window for error messages and additional information about the failure.
Use the ping command to test communication between the client machine and the license server.
If the ping command does not work, modify the hosts file or the DNS server to contain the correct host names and IP addresses. Verify that the license server and the client machines have unique IP addresses.
Verify that the ansyslmd.ini file exists in the licensing directory and that it contains the correct hostname of the license server. If this file does not exist, see Designating Server(s) for License Check-out of the ANSYS, Inc. Licensing Guide to specify the license server. If the ANSYSLMD_LICENSE_FILE or LM_LICENSE_FILE variable is used to specify the license server, verify that the hostname of the license server is correct.
Verify that the port number used on the license server and the client machine match.
Verify that the correct version of the license manager daemons (lmgrd and ansyslmd) is being used. The current version is FLEXlm 10.8.0.7.
***Unable to load profile <name> because simulation environment <simulation environment> is not available.
If you see this message, the simulation environment specified in the named profile was uninstalled since the profile was created. You will need to specify a new simulation environment and re-specify any launcher settings to continue. To avoid seeing this message in subsequent launcher sessions, update and resave the profile, or re-install the desired simulation environment.
*** Licensed number of users already reached.
You may have reached the number of ANSYS product tasks that you have licensed. Wait until a task has been freed up and try again. If this error occurs on a regular basis, you may want to talk to your ANSYS sales representative about obtaining additional licenses.
This error may also occur when licenses have been reserved for certain users, or when certain users have been excluded from licenses via the license options file.
*** All licenses are reserved for others.
This error may occur if you have multiple INCREMENT lines for the same feature in the license file, and there are differing fields on each INCREMENT line (such as VENDOR_STRING and the version field), and licenses have been reserved for this feature. In this situation, the number of reserved licenses is reserved out of each INCREMENT, rather than the sum total of both.
*** Cannot connect to license server.
or
***Unable to connect to FLEXlm license server
The license manager is currently not running. Use the ANSLIC_ADMIN utility to start the license manager. Your license must exist on the license server prior to starting the license manager.
If you install the license manager and a license file, and it appears that the server is running, but you cannot connect to your license server, try rebooting.
If you think the license manager should already be running, check the license log file for errors.
Some other possible causes for this error include:
The wrong hostname is in the license file (machine ID is correct in the file and when the license keys were generated). The license manager could not be started.
The wrong license file is on the system (both hostname and machine ID are incorrect and the license keys were created with the wrong ID). The license manager could not be started.
The wrong license file is on the system AND the user changed the server line to have the machine's hostid but not the hostname. The license manager could not be started.
An incorrect port number was used on the SERVER line(s) in the ansyslmd.ini file or in the setting of the licensing path environment variables (ANSYSLMD_LICENSE_FILE or LM_LICENSE_FILE)
All of the installed license files have expired.
*** Feature removed during lmreread, or wrong SERVER line hostid
Some possible causes of this message include:
There is a typographical error in the license file's SERVER line. Typically, the machine ID was mistyped when manually entering the license file on a machine.
The user tried to install another machine's license file on a machine and changed the SERVER line in the file to have this machine's hostname but not the machine ID.
A laptop with a docking station (with an Ethernet card in it) is removed from the docking station and the license file was made using this card's Ethernet address.
The feature was removed during lmreread but the client is reading an old copy of the license file that still contains the removed feature.
*** Clock difference too large between client and server.
This message will appear if the date on the client machine has changed. The date should never be set ahead or behind the actual date.
*** License server does not support this feature.
This message can be generated if the feature has expired (on the server), or has not yet started, or the version is greater than the highest supported version, or the license file has been edited while the license server is running and the license file is not reread. Additional causes for this message include:
If the user is trying to install another machine's license file on a machine AND changes both the hostname and the machine ID information on the SERVER line to be this machine's information. The INCREMENT lines contained in the license file are still invalid for this machine.
If new information for the requested feature was added to the license file but neither an lmreread was issued nor was the license manager restarted.
If a laptop with a docking station (with an Ethernet card in it) is removed from the docking station, and the license was made using this card's Ethernet address, AND the user edited the SERVER line, replacing the Ethernet address with the disk signature of the machine (in an attempt to fix the problem). Such an attempt will not succeed because the INCREMENT lines were created using the docking station's Ethernet address, which in this situation can no longer be seen on this machine.
If one or more INCREMENT lines that were made for machine A were installed in machine B's license file and those features were trying to be checked out from machine B.
*** Feature has expired.
*** No such feature exists.
A license does not exist for the requested product. Verify that the ANSYSLMD_LICENSE_FILE and the LM_LICENSE_FILE environment variables and the ansyslmd.ini file are pointing to the correct license server.
Verify that you are running the correct product. Use the ANSYS110_PRODUCT environment variable (for ANSYS), the -p command line option, or the Product selection box from the launcher to select the product that you are licensed to run. If you are not licensed to run this product, contact your ANSYS sales representative to obtain a license. If you are licensed to run this product, install the license from the license supplied by ANSYS, Inc. or your ANSYS sales representative using the ANSLIC_ADMIN utility. If you have already created the license, use ANSLIC_ADMIN to reread the license file.
You could also see this message if you are trying to use a license manager daemon from a previous release. The license manager daemons (lmgrd and ansyslmd) at this release are FLEXlm 10.8.0.7.
*** License file does not support this version.
The build date in the program is newer than the version in the license file. You may not be authorized to run a new release or you may not have installed your new license. If this is the case, install the license using the ANSLIC_ADMIN utility. If you have installed the new license, use ANSLIC_ADMIN to reread the license file. To view the build date in ANSYS, use the -v command line option.
*** Invalid (inconsistent) license key
The license manager daemons for this release are FLEXlm 10.8.0.7 (lmgrd and ansyslmd). Verify that you are not using the license manager daemons supplied with a previous release.
*** Local checkout filter rejected request.
Set the ANS_FLEXLM_DEBUG environment variable to 2 to find the specific cause of this message.
*** Cannot find server hostname in network database.
This message will appear if one or more of the SERVER computer names do not appear in the client computer's /etc/hosts file (UNIX) or the services file (Windows).
On SGI systems, if running under NIS, see the resolver man page for more information.
*** The License Manager is currently running and failed to shutdown. There may be some remaining processes that need to be killed manually.
If you attempt to uninstall the license manager without first successfully shutting it down, you may inadvertently leave an ansyslmd and an lmgrd process running on your system. These processes will be stopped when you reboot your system. You can stop these processes manually, but use extreme caution, because other products that use the FLEXlm license manager will also have lmgrd processes running. If you do want to stop an lmgrd process, use the ps command to find the ANSYS lmgrd process.
***The ANSYS license manager server is down. Unless a connection is reestablished, ANSYS will exit in nn minutes.
This message occurs in a one-server license environment if your license manager has quit running. In a three-license server environment, the ANSYS license manager must be running on at least two of the three license server machines at all times. If two of the license server machines go down, or two of the machines are not running the license manager, this error message will appear in the program output or in a message box. The program will continue to run for nn minutes to allow the license manager to be restarted or to be started on a second machine if using redundant servers. When this error message appears, start the license manager on the other machines designated as license servers.
If you get this message and determine that the license manager is still running, and you are running in a one-server environment, then the IP address of the license server machine was changed while the ANSYS product was running (this is usually caused by connecting to or disconnecting from an Internet Service Provider (ISP) that dynamically allocates IP addresses). To correct this situation, you must return the IP address to the same address that the license server had when the ANSYS product was started.
If the IP address changes after you start the ANSYS product (either because you connected to or disconnected from your ISP), you can correct the error by restarting the ANSYS product. You should not need to restart the license manager.
You can avoid this problem by remaining connected to or disconnected from the ISP the entire time you are running the application.
***FLEXlm version of vendor daemon is too old.
The license manager daemons at this release are FLEXlm 10.8.0.7 (lmgrd and ansyslmd). Verify that you are not using the license manager daemons supplied with a previous release.
***Cannot read data from license server.
The server and the client are having difficulties communicating. This error is usually caused by the network setup or by the network data being different from the data in the license file (for example, the server name, machine ID, port number, or vendor daemon).
Confirm that the information on the SERVER line of the license file is the correct information for the server.
Confirm that the syntax of the SERVER and VENDOR lines of the license file is correct.
Verify that TCP/IP is enabled correctly.
Check that the hosts file on the client machine contains the license server.
Try using <port>@<host> when specifying the server.
***Unable to return <Product>, encountered “feature not found” attempting to return license feature <Product.>
or the following will appear in the log file:
UNAUTHORIZED lmremove request from <user> at node <host>.
If you see the above message when attempting to return a borrowed license before the expiration date, the -2 -p license manager startup option was set. Unset the option. See Modifying License Manager Startup Options for more information on using the license manager startup options.
***Not a valid server hostname, exiting. Valid server hosts are: xxx
The hostname in the SERVER line of the license file does not match the hostname of the system. In this case, change the hostname in the license file. Other possible causes include:
The license file was put on a machine other than the one for which it was created; therefore, the hostname is not correct.
The hostname of the license server changed. Change the hostname on the SERVER line of the license file to correct this problem. REMEMBER to send ANSYS the new hostname so that future license files are made with the correct hostname.
The license file was put on a machine other than the one for which it was created AND the user changed the machine's ID on the SERVER line but did not change the hostname. If the machine ID is also wrong, you will also see a message about the wrong hostid on SERVER line after correcting the hostname.
The wrong hostname was used to create the license file. As long as the correct machine ID was used, you should be able to change the hostname on the SERVER line of the license file to fix this problem. REMEMBER to send ANSYS the correct hostname so that future license files are made with the correct hostname.
***Invalid license key (inconsistent authentication code)
The INCREMENT lines in the license file are not valid for this system (HostID mismatch). This error will also occur if the license file was typed incorrectly. Additional causes for this message include:
If a license file created for machine A is being installed on machine B AND the user changed the hostname and the machine ID to machine B's in the SERVER line.
If INCREMENT lines created for machine A are appended to an existing license.dat file on machine B.
If a laptop with a docking station (with an Ethernet card in it) is removed from the docking station, and the license was made using this card's Ethernet address, AND the user edited the SERVER line, replacing the Ethernet address with the disk signature of the machine (in an attempt to fix the problem). Such an attempt will not succeed because the INCREMENT lines were created using the docking station's Ethernet address, which in this situation can no longer be seen on this machine.
In a three-server license environment, if the license file was created using an incorrect hostid for one of the license servers, this message will appear and will prohibit an ANSYS product from running on any machine. Verify that the hostid in the license file matches the hostid on all three license servers. If it does not, the license file must be created using the correct hostid for all license server machines.
***Wrong HostID on SERVER line for license file: <path to license file>
License file is not valid for this machine. Possible causes include:
There is a typographical error. If the license file was entered manually, the machine ID may have been incorrectly typed in the SERVER line.
The user installed a license file created for machine A on machine B and changed the hostname in the SERVER line but did not change the machine ID.
The hostid changed on a machine but the hostname stayed the same.
A laptop with a docking station (with an Ethernet card in it) is removed from the docking station, and the license file was made using this card's Ethernet address.
A license file was made for a Pentium III CPU ID and the hyphen was not put after the first four characters of the ID (e.g., ABCDEF01 was entered as the ID rather than ABCD-EF01). Ethernet address would be expected.
A license file was made using the Windows disk signature but the keyword 'DISK_SERIAL_NUM=' was not put before the ID. Ethernet address would be expected.
*** “XXX” : Not a valid server hostname, exiting. Valid server hosts are: “YYY”.
The hostname listed in the license.dat (YYY) file does not match the hostname of the system (XXX).