If the license manager will not start, perform the tests below in the order they are listed:

Linux x64 Systems:

Linux x64 systems running the Ansys License Manager require the Linux Standard Base (LSB) package. If this package is missing, you will see one of the following errors when the license manager attempts to run:

/lmgrd -h
./lmgrd: No such file or directory

In this case, try installing the LSB package from the Linux installation media.

Three-Server Environment

In a three-server environment, you could see the following message when you start the first server:

When you attempt to stop the license manager, it may not stop immediately. You should use the Stop the Ansys, Inc. License Manager option of the Ansys License Management Center to stop the license manager. For more information, see Stopping the Ansys License Manager. We do not recommend stopping the license manager manually; however, if you choose to do so, you must stop the components in the following order:

In cases where you have started the lmgrd portion of the ANSYS license manager with the “-local” command, there can be an issue when stopping the server using the following command:

lmutil lmdown -c "C:\Program Files\ANSYS Inc\Shared Files\Licensing\license_files\ansyslmd.lic" -q

Resulting in the following error message:

"Shutdown failed: lmdown/lmreread must be run on the license server machine. (-119,214)"

As a fix for this we have provided an updated version of the lmutil executable which can be found in:

<Installation Drive>:\Program Files\ANSYS Inc\Shared Files\bin\winx64\drivers\flexnet\11_17_2_0.zip

Extract this zip file and replace the current version of lmutil with this updated version and then run the “lmutil lmdown” command.

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 Ansys License Management Center will show that it is stopped. For more information, see Setting Up Redundant (Triad) Servers.

If the Ansys License Manager's licensing configuration log file (install_licconfig.log) indicates that the step to automatically update any existing site preferences (product order) failed, the following procedure can be used to manually update your modified product order file to include any product changes that have occurred in the most recently installed release of the Ansys License Manager.

If you do not see the correct licenses in your application, in Client ANSLIC_ADMIN's Set License Preferences for User option, or in the Mechanical APDL Product Launcher, check the following:

On the license server machine:

For more information, see Specify Product Order.

On Windows systems, you may see unexpected error messages in the FlexNet licensing log file when you shut down the license manager. Messages similar to the following could appear:

These or similar messages in the FlexNet log file can be safely ignored in most cases. You can verify that the service is shown as stopped, and that the ansysli_server, ansysli_monitor, lmgrd, and ansyslmd processes are stopped via Task Manager.

If the license manager appears to start but you cannot check out any licenses, perform the tests below in the order they are listed:

You could also encounter problems with obtaining a license if the Licensing Interconnect is still attempting to restart the FlexNet server. Check the FlexNet license.log file. If you see the following lines multiple times, try rebooting your license server machine:

(lmgrd) ansyslmd exited with status 28 (Communications error)
(lmgrd) Since this is an unknown status, license server 
(lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon.
(lmgrd) REStarted ansyslmd (pid 103864)

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 below in the order they are listed:

On Windows, if the license manager starts and licenses can be taken from the license server, but the FlexNet licensing log file and the ansysli_server.log file are 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 files are to be written.

If queuing does not work, refer to the following list of possible causes and corrections:

If you select the Display the License Status option from the ANSLIC_ADMIN utility and see a message stating that the Licensing Interconnect or FlexNet path is empty, try the following:

In cases where you are unable to retrieve license preferences through the ANSLIC_ADMIN utility, you may be able to resolve the problem by trying the following:

On some Linux systems (for example Red Hat 7 systems), if you cannot enter data in text fields when using the ANSLIC_ADMIN utility, you may be encountering a Tcl incompatibility. To correct the problem, unset the following environment variables before running the ANSLIC_ADMIN utility:

You should reset these environment variables when you are finished using ANSLIC_ADMIN. Do not permanently unset these environment variables as doing so could affect other applications.

Linux x64 System:  —  Linux x64 systems running the Ansys License Manager require the Linux Standard Base (LSB) package. If this package is missing, you will see a message similar to one of the following errors when the license manager attempts to run, or when you attempt to run a licensing utility, such as ANSLIC_ADMIN, getFLEXid, or lmutil.

/lmgrd -h
./lmgrd: No such file or directory

If you have confirmed that the file listed does exist, try installing the LSB package from the Linux installation media.

There are a number of reasons why you may not be able to see an attached dongle. Review the list below to troubleshoot the issue.

To run the Ansys License Management Center, Tomcat must be running. Start Tomcat prior to starting the Ansys License Management Center from a bookmark.

To view PDF files in the  Ansys License Management Center the appropriate PDF plugin for your browser must be enabled.

For Internet Explorer and Firefox: Enable the Adobe PDF plugin.

For Chrome: Enable the Chrome PDF Viewer plugin.

To perform searches of PDF files displayed in the  Ansys License Management Center the appropriate PDF plugin for your browser must be enabled.

For Internet Explorer and Firefox: Enable the Adobe PDF plugin.

For Chrome: Enable the Chrome PDF Viewer plugin.

Installing the Ansys License Manager as root and subsequently attempting to run  Ansys License Management Center as a non-root user may display one of the following permission issues:

These permission issues may be resolved by running the following commands:

During the default Ansys License Manager installation, the Tomcat port number is set to 1084. To change this port number, see, Modifying the Tomcat Port Number

There is a known issue with some VPN tools in which the tool does not clear the IPs correctly or does not clear them immediately after the VPN disconnection.

To address this issue, you need to force a DNS clear by performing the following steps:

The Ansys Licensing Interconnect shuts down with the following message:

2017/09/27 05:43:30 ERROR Error determining if process <PROCESS NAME BEING CHECKED FOR> is running:

Couldn't get hold of a new file descriptor. Too many open files

This is caused by exceeding the Linux "Open Files Limit". To correct this issue, increase the open files limit for the license server.

For each license checkout request, you will see at least two log entries, one for the actual license feature that is checked out from FlexNet and one or more for the capability request to the Licensing Interconnect. (See the Capability definition in Glossary).