To run ANSLIC_ADMIN on Windows, choose (for the server version) or (for the client version). To run the utility on Linux, type the following:
/ansys_inc/shared_files/licensing/lic_admin/anslic_admin
To change the language to a localized version of the utility,
first issue the following command with the -setliclang option. On Windows, run:
"<os drive>\Program Files\ANSYS Inc\Shared Files\Licensing\licadmin\anslic_admin.bat"
-setliclang languageOn Linux, run:
/ansys_inc/shared_files/licensing/lic_admin/anslic_admin -setliclang languageThis command changes the language used for both the server ANSLIC_ADMIN utility and the ANSYS Licensing Interconnect log file. Use the language
directory name in the language subdirectory of the licensing directory
(en-us, fr, de, etc.) as the
language value. This option is valid only with the server ANSLIC_ADMIN. Then launch the ANSLIC_ADMIN
utility using the above methods.
Important: Changing the language will affect all users of the server ANSLIC_ADMIN utility and the ANSYS Licensing Interconnect. Verify with your licensing system administrator before making this change.
To change the language setting locally for only the current
session of the server or client ANSLIC_ADMIN utility, you can launch the utility using the -lang option:
<os drive>:\Program Files\ANSYS Inc\Shared Files\Licensing\licadmin\anslic_admin
-lang languageor
/ansys_inc/shared_files/licensing/lic_admin/anslic_admin -lang languageWindows 7 Administrator Privileges On Windows 7 machines, you need to always run these ANSLIC_ADMIN options as an administrator, preferably with UAC turned off. If UAC is on, even as administrator, you must right-mouse click the ANSLIC_ADMIN selection from the Start menu and choose .
Windows 8.1 and Windows 10 Administrator Privileges On Windows 8.1 or Windows 10 machines, you need to always run these ANSLIC_ADMIN options as an administrator. Additionally, you should right-mouse click the ANSLIC_ADMIN selection from the Start menu and choose .
See the User Account Control (UAC) section of the ANSYS, Inc. Windows Installation Guide for more details on working with Windows and UAC.
We do not recommend running the ANSLIC_ADMIN on Windows machines by double-clicking the executable directly. Doing so could launch the utility with unexpected permission levels.
To use the utility, select an action from the list of buttons on the left.
The ANSLIC_ADMIN utility consists of the following options:
Launch the ANSYS License Management Center (Server Option)
Run the ANSYS Borrow Utility (Windows only) (Client Option)
Set Site Preferences -- includes the following options:
Specify Product Order (Server Option)
Modify Startup Options (Server Option)
Specify License Servers to Cache (Server Option)
View Status/Diagnostic Options -- includes the following options:
From the menu, you can select (server only) and then choose a different language in which to view the server ANSLIC_ADMIN utility and the ANSYS Licensing Interconnect log file. You must close and reopen the ANSLIC_ADMIN utility for this setting to take effect. This option is valid only with the server ANSLIC_ADMIN.
From the menu, you can select:
To exit the ANSLIC_ADMIN utility, choose .
Use this option to launch the ANSYS License Management Center (LM Center). The ANSYS License Management Center is a browser-based user interface that centralizes many of the ANSYS licensing administrative functions. For more information, see License Server Administration Using ANSYS License Management Center.
Use this option to set the ANSYS Licensing Interconnect and ANSYS FlexNet servers. Using this option creates or updates (lists, adds, modifies, deletes, or reorders) entries in the ansyslmd.ini file in the licensing directory for the local machine. With this option, you can specify single servers, multiple single servers, or redundant triad servers. You also use this option to specify the Licensing Interconnect and ANSYS FlexNet port numbers. Run this option on every machine where you installed an ANSYS product. We recommend using this method for specifying your license server preference.
This option is available for both the server and client versions
of ANSLIC_ADMIN on Windows machines.
In most situations, you should use the client version. The client
version is appropriate regardless of where you have installed the
product. You should use the server version of this option only to
specify the license server machines for Release 11.0 and lower versions.
You can also use the server version to specify license server machines
if you have installed the product into <os drive>\Program Files, but we recommend
using the client version anytime you are working with the current
release.
If the product is installed in <os drive>\Program
Files (by a user with administrative privileges), you must have
administrative privileges in order to add or modify your server specification. If you
are running on a Windows 7 machine, you must run as an administrator, preferably with
UAC turned off. If you are running with UAC turned on, you must launch ANSLIC_ADMIN using the Run as
administrator option. If you are running on a Windows 8.1 or Windows 10
machine, you must run as an administrator. Additionally, you must launch ANSLIC_ADMIN using the Run as administrator option. For more
information, see the User Account Control (UAC)
section of the ANSYS, Inc. Windows Installation Guide for more details on working with Windows and UAC.
To add a server:
Click .
Click .
Enter the ANSYS Licensing Interconnect and FlexNet port numbers (2325 and 1055 by default, respectively). Specify the number of servers and enter the host name(s) of your license server(s). You cannot enter a path or a filename in place of the hostname.
To specify multiple single servers, click on this screen after adding the first server. Then click the button again and add information for the next server. Repeat this process for each single server.
To specify redundant triad servers, click the option and enter the hostname for each of the three servers in the spaces available.
Click .
To delete a server, highlight the server in the list and click .
To edit a server, click one of the listed servers and click . You can then change the ANSYS Licensing Interconnect and the FlexNet port numbers, the number of license servers, or the hostname(s).
The ansyslmd.ini File The option creates or updates the ansyslmd.ini file that is located in the licensing directory. Entries in the ansyslmd.ini file tell ANSYS, Inc. products which license server(s) to query to find a valid license. Using this option allows all users at your site to use this setting without having to individually set the ANSYSLMD_LICENSE_FILE or ANSYSLI_SERVERS environment variables to specify the license server machine(s). It also eliminates the need to have a copy of the license file on every system at your site.
The order that the SERVER lines are listed in the ansyslmd.ini file dictates the order in which the license request is granted. To reorder the entries in the list, highlight a server and use the or buttons.
You are not limited to designating one set of license server machines for your network. You can have multiple single-server or three-server (redundant triad) licensing systems on your network. In this situation, you would have certain licenses connected to a set of server machines (one or three) on the network, and other licenses connected to a different set of server machines (one or three) on the network.
The format of the ansyslmd.ini file created by ANSLIC_ADMIN follows. Each server's specification entry in this file will typically begin with ANSYSLI_SERVERS= and SERVER= to specify the Licensing Interconnect and FlexNet port numbers, respectively.
On a single server:
ANSYSLI_SERVERS=<ansysliport>@<host> SERVER=<flexnetport>@<host>
For multiple single servers, each server should have its own ANSYSLI_SERVERS= and SERVER= lines.
On redundant (triad) servers on Linux platforms:
ANSYSLI_SERVERS=<ansysliport>@<host1>:<ansysliport>@<host2>:<ansysliport>@<host3> SERVER=<flexnetport>@<host1>:<flexnetport>@<host2>:<flexnetport>@<host3>
Windows platforms use semicolons (;) instead of colons:
ANSYSLI_SERVERS=<ansysliport>@<host1>;<ansysliport>@<host2>;<ansysliport>@<host3> SERVER=<flexnetport>@<host1>;<flexnetport>@<host2>;<flexnetport>@<host3>
Do not use commas as separators; use colons (:) on Linux machines and semicolons (;) on Windows machines.
The ANSYS Licensing Interconnect default port number is 2325 and the ANSYS FlexNet default port number is 1055. The host is the license server hostname. For example, if the license server name is alpha1:
ANSYSLI_SERVERS=2325@alpha1 SERVER=1055@alpha1
The order of the ANSYSLI_SERVERS and the SERVER lines in the ansyslmd.ini file specifies the order in which the requested license will be granted.
You must use the port@host format; you cannot enter a path or a filename in place of the hostname.
Overriding the ansyslmd.ini File If you want to override the server specification settings in the ansyslmd.ini file, you can do so by setting the ANSYSLMD_LICENSE_FILE and ANSYSLI_SERVERS environment variables on individual machines. These environment variables are useful if you want to temporarily point to a different license server machine without disrupting the machine's configuration. Use the ANSYSLI_SERVERS environment variable to specify the Licensing Interconnect port number. Use the ANSYSLMD_LICENSE_FILE to specify the FlexNet port number.
If the ANSYSLMD_LICENSE_FILE environment variable is set but the ANSYSLI_SERVERS environment variable is not set, the same server machines will be used to specify the Licensing Interconnect but the port number will be replaced by the Licensing Interconnect default port of 2325. When both variables are set, ANSYSLMD_LICENSE_FILE explicitly defines the FlexNet servers while ANSYSLI_SERVERS explicitly defines the Licensing Interconnect servers.
If you set the ANSYSLMD_LICENSE_FILE or ANSYSLI_SERVERS environment variables on a three-server (redundant) system, specify all three systems, in the same order as the SERVER lines are listed in the license file. If you specify only the master and it is down, you could see a “License Server Down” or “No License Found” message and the search for a license could fail. Join redundant or multiple single server systems by separating the system names with colons on Linux systems and semicolons on Windows systems.
To have your license server preference known each time you log in, set the environment variables ANSYSLMD_LICENSE_FILE and ANSYSLI_SERVERS (both Windows and UNIX systems). On UNIX systems, place these environment variables in your login startup file (e.g., .cshrc file).
Suppose that you have a company with two departments, Design and Engineering. The Design Department has one license of ANSYS Mechanical and one license of DesignSpace with the server DES1, and all users in the Design Department run on DES1. The second department, Engineering, has two licenses of ANSYS Multiphysics with the server ENG1, and all users in the Engineering Department run on ENG1. The ansyslmd.ini file states ANSYSLI_SERVERS=2325@DES1 and SERVER=1055@DES1 for the Design Department, and ANSYSLI_SERVERS=2325@ENG1 and SERVER=1055@ENG1 for the Engineering Department. These settings limit users in each department to work only on their own server. If individual users in the Design Department need to run on the engineering server, ENG1, they could set the following environment variable:
setenv ANSYSLMD_LICENSE_FILE 1055@ENG1
This example would automatically use 2325@ENG1 for the Licensing Interconnect license path. For this example, you would need to set ANSYSLI_SERVERS only if you were not using the default Licensing Interconnect port number.
Use this option to review the licenses available and prioritize the licenses. Settings specified here apply only to the username shown in the button title. When you select this option, you will first choose the release for which you want to set preferences. Select the release and click . All licenses available to you on your license server machine(s) are shown under the appropriate tab on the next dialog:
Solver
PrepPost
Geometry
HPC
You control the order in which the system attempts to check-out a license by moving the licenses up and down in the list using the or buttons. When you open an application, the license manager attempts to check-out the license listed first in the list. If unable to check-out that license, then the license manager attempts to check out the next license in the list that can be used by the application. The license manager will continue through the list until an available license is found. If none are found, a message displays.
By default, all licenses available from your license server are shown and marked as available for use. If you do not want a particular license to be available for your use, select the license in the list, and set the field to 0.
If you received a new license, you may need to reset your preferences. If you had previously set your license preferences using this option, add the new license to your list in the desired order.
If you have made changes to your license preferences, you can return the settings to the default state by selecting the button.
When you have completed your changes, click to make the changes and close the dialog box. Click to make the changes without closing the dialog box. Selections you make here will take effect with any new sessions/license checkouts but will not affect the current session or change the license(s) currently in use.
ANSYS Workbench users can also specify whether to use the shared or separate licensing method.
For details on setting user license preferences, including shared vs. separate licensing for ANSYS Workbench and specifying HPC licensing settings, see Establishing User Licensing Preferences in the End-User Settings section.
License borrowing (available only on Windows machines) allows a user to take a license for use outside of the company facility, such as for an engineer to take a license home on his laptop. Before users can take advantage of license borrowing, you need to set up the borrowing environment.
License borrowing is available only if you have borrowable licenses and only on Windows machines; however, the license server machine that is managing the licenses can be any system that ANSYS, Inc. supports as a license server. You cannot run both borrowed and non-borrowed licenses simultaneously. For example, if you borrow licenses but remain connected to a network from which you can use licenses, you will be able to use only the borrowed licenses. Likewise, if the machine on which you borrowed licenses is also a license server from which you could normally use licenses, you would be able to use only the borrowed licenses.
This option is available only for the client version of ANSLIC_ADMIN.
To use license borrowing, you must have license keys that specify borrowable licenses. License features that can be borrowed will contain the keyword BORROW.
You can use the optional FlexNet options file settings to further control borrowing at your site. To use these settings, you must first specify which users are allowed to borrow licenses by adding an INCLUDE_BORROW group to the options file. Any user not in the INCLUDE_BORROW group will not be allowed to borrow licenses. You may also want to set up an EXCLUDE_BORROW group to prevent specific users from borrowing licenses.
You can also limit the number of licenses that can be borrowed from your total pool of borrowable licenses. Set the BORROW_LOWWATER option in the options file to the number of licenses that cannot be borrowed. For example, if you have 15 licenses total and want to limit the number that can be borrowed to 5, set BORROW_LOWWATER=10.
The maximum number of hours a license can be borrowed at any one time is defined by your license file. You can set that limit lower for your users by setting the MAX_BORROW_HOURS option in the options file. MAX_BORROW_HOURS cannot exceed the limit specified in your license file. The total maximum number of borrowable hours is defined by your license agreement.
Compatibility between versions Flexera Software has created an incompatibility in license borrowing between FlexNet releases. Since different versions of FlexNet are used at most releases, the borrowed licenses are not compatible between different ANSYS releases. The ANSBORROW utility includes a selection for the ANSYS version you are planning to run using the borrowed license. Choose your version carefully, because you will only be able to run one of the versions at a time with borrowed licenses.
The ANSBORROW utility allows you to borrow either initial release or service pack (SP) versions. The SP versions for a given platform use the same FlexNet version as the initial release; therefore, licenses selected for an SP should work for the initial release.
To run the license borrowing utility, you must be running on a Windows machine connected to a network, and you must have borrowable licenses. For more information about borrowable licenses, contact your ANSYS sales representative.
Connect to the network where the license server machine is running.
Launch the client license borrowing utility: . Select .
On the Borrow tab, specify the version number and return date. The return date defaults to the third day from the current date.
If you change any of the borrowing criteria, the product list will automatically update in five seconds. To update the list immediately, click the button.
Select the product(s) you want to borrow. The product list includes add-on features or geometry interfaces. If you do not see a product listed that you think should be available, verify that you have selected the correct version.
Click .
Disconnect from the network. Note that even when you've disconnected from the network, you must still run the products from the same account you used to borrow the licenses. For example, if you use a network account to borrow the licenses, you cannot then run from a local account.
Be sure to verify that you can run the correct product with the borrowed licenses from your machine AFTER you've disconnected from the network. If you encounter any difficulties, reconnect to the network, return the license, and then re-borrow the correct license.
If you keep a license for the full amount of time, there is no need to check the license back in. Your borrowed license will simply expire at the end of the borrow period, and the license will be released into the pool of available licenses.
To return a license early:
Reconnect to the same license server from which you borrowed the license(s).
Launch the client license borrowing utility: . Select .
Select the tab. Click . If you want to keep some but not all of the licenses you borrowed, you will need to re-borrow them.
Disconnect from the network.
The license(s) you borrowed will be returned to the pool of available licenses.
Note: You must return borrowed licenses from the same account you used to borrow the licenses originally.
Some multi-feature products include other products and/or add-on features. The utility will automatically check out any such included products or add-on features. If you borrow one of these multi-feature products and then click the tab, you will see the product you selected, as well as any other products and add-ons that it includes. If you return a multi-feature product early, these products and add-on features will also be returned.
This option is used for license server machines only.
The following site preference settings are available:
This option launches a utility that allows you to designate the order that the licensed products are listed in the Mechanical APDL launcher and the order in which licenses are tried in all applications. You first will need to select the product release. You can choose one of the following:
Release 11.0: Selecting this option affects the product ordering for Release 11.0 for this machine (including all users who run a Release 11.0 product on this machine or mount to this machine). If you select this option, the product ordering you specify will NOT affect any releases after 11.0.
Release 12.0 and higher: Selecting this option affects the product ordering for Releases 12.0 or later and is applicable ONLY if this machine is a license server machine. The product ordering you select with this option will affect all users who use this machine as a license server machine.
After you choose a release level, click . You will then need to select the installation directory (Release 11.0 only), product category (Solver, PrepPost, Geometry, or HPC). To re-order the products, select a product and click the or button. When you have finished reordering all products that you want to reorder, click and then .
All products available in a given category are shown, regardless of whether you have licenses for them.
If you have made changes to your product ordering, you can return the settings to the default state by selecting the button.
For Release 12.0 and higher, after making changes to the product order (including resetting to the default), you will need reread the license file or restart the license manager for the changes to take effect.
Only those logged in as root or superuser (Linux) or with administrative privileges (Windows) can use this utility. You should set the product order before any of the users at your site run; once a user sets his preferences, the user preferences will take precedence.
Note: When installing the License Manager, if you have modified the product order in a previous release, the installation process will automatically update the product order to reflect any changes you made as well as any changes (such as naming conventions) that may have occurred between releases.
Note: Only those users who are logged in as root or superuser (Linux) or with administrative privileges (Windows) can use this utility.
Use this option to modify your license manager startup options. License manager startup options that you can modify include:
You can specify the path to the ANSYS Licensing Interconnect debug log file (ansysli_server.log, by default), the detail level of the file (standard, connections, or verbose), the size limit of the file (default is 10MB; minimum is 1MB), and the number of log files to save (default is 10; minimum is 1).
ANSYS Licensing Interconnect Debug Log File Detail Descriptions
STANDARD level logs ansysli_server STARTUP options, license cache information (such as features/counts and FlexNet options file content), CHECKOUT, CHECKIN, RESERVE, and RETURN_RESERVE. It also logs CLIENT_SHUTDOWN for all but ansysli_monitor.
CONNECTIONS level logs everything that STANDARD logs, and CLIENT_ACCEPT and CLIENT_SHUTDOWN for the monitor.
VERBOSE level logs STANDARD plus CONNECTIONS, and ADD (product definitions and shared capabilities) and REMOVE (shared capabilities).
You can specify the path to the FlexNet debug log file (license.log, by default). By default, a new license.log file is created each time you start the license manager; you can choose to have new information appended to the existing file instead.
You can also set
the -local setting (Linux only).
The -local option restricts the ability to
shut down the FlexNet components of the license manager to only
an administrator running on the same machine where the FlexNet components
of the license manager was started. This option is off by default.
See the FlexNet License Administration
Guide for more information on using this option.
The -local option is not recommended if you
will be using license borrowing.
You can specify the ANSYS Licensing Interconnect port number here. The default port number is 2325.
All machines that have this server machine in their Licensing Interconnect paths must use the same port number. If you change the Licensing Interconnect port number here, and other machines use this machine's Licensing Interconnect, then on each of those machines, you must change the Licensing Interconnect port number by one or both of the following options, as appropriate for your configuration:
option of the ANSLIC_ADMIN utility
option of the ANSLIC_ADMIN utility
You can also disable the ability to reserve licenses for a design point study in ANSYS Workbench and/or the users' ability to track licenses used by ANSYS Workbench. For more information on reserving licenses for design point studies in ANSYS Workbench, see Reserving Licenses for Design Point Studies in the ANSYS Workbench documentation.
On Linux machines only, you can also specify who can shut down the ANSYS License Manager. By default, anyone can stop the license manager. You can restrict shutdown capabilities to only the user who started it, or to a group, such as lmadmin. If you choose group, you will need to specify the name of the group. If you specify a group restriction, any users in that group who want to stop the license manager must have the specified group as their primary group. Note that the user who started the license manager will still be able to shut it down, even if he is not part of a group with shutdown capabilities.
Warning: The license.log file and the ansysli_server.log file for each server should be located on a local disk. Writing to an NFS-mounted disk or remote file server creates a situation where the license server(s) may fail. If the remote system containing these files crashes, the license manager would be unable to log license transaction data. This would create a fatal error condition.
When the Licensing Interconnect starts, it caches the licenses for any ANSYSLI_SERVERS lines that are in the ansyslmd.ini file in addition to its own licenses. As you run ANSYS applications and they connect with the Licensing Interconnect, it caches the licenses for any servers in your ANSYSLI_SERVERS path that have not yet been cached. Sometimes, especially due to network traffic, this caching process can impact the time it takes to check out a license. Use this option to cache your servers when you start the ANSYS License Manager, rather than at the point that you request individual licenses.
Note: Only those users who are logged in as root or superuser (Linux) or with administrative privileges (Windows) can use this utility.
When you select this option:
On the Specify License Servers to Cache dialog, click .
On the Specify License Servers to Cache - Edit Selected Server Machine dialog box, enter the Licensing Interconnect port number. The default Licensing Interconnect port number is 2325.
Enter the hostname of the server.
Click .
Repeat steps 1 - 4 for any additional servers that you want to cache.
When you have finished specifying servers, click on the Specify License Servers to Cache dialog.
To delete a cached server, highlight the server in the list and click .
To edit a cached server, click one of the listed servers and click . You can then change the ANSYS Licensing Interconnect port number or the hostname(s).
The following reporting options are available:
When you select one of these options, the data will appear in the log area on the right side of the utility. appends the customer number to the session log itself; the other options create their own display in the log area. Each option is explained in the following sections.
Use this option to see the status of licensing activity. All features are displayed in the status window, along with the users of those features. You can append this information to the session log or write it directly to a file using the buttons at the bottom of the window. This option displays information based on the same license path rules as ANSYS, Inc. products, taking into account the settings in the ANSYSLMD_LICENSE_FILE environment variable and the ansyslmd.ini and license files. Setting the ANS_FLEXLM_DISABLE_DEFLICPATH environment variable will affect the information displayed by this option.
Use this option to see a list of capabilities that are queued and awaiting availability, and the applicable licenses that are being used. The report will have the following format:
Capability Timestamp User Count Host PID Platform
Product1 Count
Timestamp User1 Count Host PID Platform
Timestamp User2 Count Host PID Platform
Timestamp Usern Count Host PID Platform
Product2 Count
Timestamp User1 Count Host PID Platform
Timestamp User2 Count Host PID Platform
Timestamp Usern Count Host PID Platform
Where the first line shows information for the requesting user, and subsequent lines under that capability show information for the users who are currently using the licenses for each of the licensed products that satisfy the requested capability.
An example report is shown below. Each line is numbered for reference in the discussion following the example. Note that the actual report does not contain line numbers.
Capability Product Timestamp User Count Host PID Platform 1 ANS_SOLVER 2010/04/27 09:39:27 JQD 1 mach1.win.acme.com 1234 winx64 2 ane3fl 3 3 2010/04/27 08:01:10 JXS 1 mach2.win.acme.com 5678 winx64 4 2010/04/27 07:29:13 MQD 2 mach3.win.acme.com 8765 winx64
Line 1: User JQD is running a process, 1234, on the machine mach1.win.acme.com, which has requested one license with the ANS_SOLVER capability.
Line 2: Based on the site/user preferences, the ane3fl product can satisfy the requested capability, and this site/user is permitted to use up to 3 licenses of this product.
Line 3: User JXS has been using 1 of the available licenses since 8:01:10, from machine mach2.win.acme.com, running process number 5678.
Line 4: User MQD has been using 2 of the available licenses since 7:29:13, from machine mach3.win.acme.com, running process number 8675.
Since users JXS and MQD are already using all of the available licenses, user JQD must either wait for one of those licenses to be freed, or contact one of those users and request that a license be freed.
Select the Auto-Refresh button to have the information automatically refresh every five (5) seconds.
You can also display the queuing report via command line, without launching the ANSLIC_ADMIN utility. To do so, run the following command on Windows systems:
"C:\Program Files\ANSYS Inc\Shared Files\Licensing\licadmin\anslic_admin" -queueinfo
If you need to view the queuing report frequently, you may find it convenient to set a desktop shortcut using the above command.
Run the following command on Linux systems:
/ansys_inc/shared_files/licensing/lic_admin/anslic_admin -queueinfo
Use this option to display your customer number (necessary when requesting customer support). The license manager must be running for you to obtain your customer number.
When you choose this option, ANSLIC_ADMIN gathers various licensing-related files, logs and related information about your license client system and places them in a single directory.
This feature is useful if you want to easily review the files from a single location, or if you need to compress the files and send them to a technical support representative. Every time you choose to gather these files, you are prompted to specify the path of the diagnostics directory or to accept the default location. If you do not define the path of the diagnostics directory, the log and error files will be copied into a new, date-stamped subdirectory in your $HOME/.ansys directory on Linux or in the directory specified by the TEMP environment variable on Windows. Be aware when choosing this option that some of these files can be large and could require significant disk space. You may want to delete these directories when you are finished reviewing them because of the disk space usage.
Using the ansys_pid utility:
After all relevant files are gathered (if selected), this option runs the ansys_pid utility, which queries the system for information that may be useful for troubleshooting certain problems. This operation may take a few minutes. You can append this information to the session log, or you can write it out directly to a file using the buttons at the bottom of the window.
When you run this ansys_pid utility, information about your licensing information is displayed in the ANSLIC_ADMIN log area. Information displayed may include:
operating system info
environment information, including environment variable settings
firewall information
available license information
The contents of specific log and error files will not be displayed in the ANSLIC_ADMIN log area. You will need to review these files individually for specific errors and other status/log information.
Note: If you have set the ANS_FLEXLM_DISABLE_DEFLICPATH environment variable, the information will be displayed based on the ANSYSLMD_LICENSE_FILE environment variable setting; settings in the ansyslmd.ini file in the licensing directory will NOT be used.