This section lists problems and error messages that you may encounter while installing and/or running Ansys, Inc. products. After each situation description or error message is the user action required to correct the problem.
You can also find answers to commonly-asked questions on our Ansys customer site. After you log in to the Ansys customer site, select Knowledge Resources> Solutions.
For information on licensing-related errors, see the Troubleshooting section of the Ansys License Management Guide .
There are situations which require licensing-related information to be gathered for diagnostic and troubleshooting purposes. At times it may be necessary to provide this information to technical support.
The client-related diagnostic information can be gathered by using the Ansys Licensing Settings Utility. For more information, see, Gathering Diagnostics in the Ansys Licensing Settings Utility section of the Ansys Licensing Guide.
The server-related diagnostic information can be gathered by using Ansys License Management Center or by using the standalone gatherdiagnostics script.
If the GUI installation process appears to "hang" during file extraction, with no activity appearing in the message window, press on the command window used to start the installation. When the installation is complete, check the message window carefully for any installation errors or warnings; however, this situation rarely causes installation errors.
If the installation does not progress beyond the extraction of any single file during the file extraction phase, you may have insufficient disk space in the temporary directory that the file extraction utility uses. Be aware that some components require a lengthy extraction time; we recommend allowing up to 30 minutes for these components to extract if you are running on a particularly old or slow system.
To resolve this problem, remove files from your $TEMP directory to free up disk space, or increase the size of any disk quotas on your $TEMP directory.
If the target machine does not have a DVD drive, we recommend that you download the installation files from the Ansys customer site. For more information on downloading files from the Ansys customer site, see Product Download Instructions. Use a USB Flash drive or follow the instructions in Mounting the DVD Instructions for DVD Installations (Linux x64 Only) to mount to a machine that does have a DVD drive.
If the help for the Product & CAD Configuration Manager does not load into your default browser, set the BROWSER environment variable to the path of your HTML viewer (such as Mozilla or Firefox) and restart the Product & CAD Configuration Manager.
SUSE — On some SUSE Linux systems, if you cannot enter data in text fields during the installation or 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 installation or the ANSLIC_ADMIN utility:
| QT_IM_MODULE |
| XMODIFIERS |
| GTK_IM_MODULE |
You should reset these environment variables when you are finished running the installation or using ANSLIC_ADMIN. Do not permanently unset these environment variables as doing so could affect other applications.
The current platform type is not selected and is not included in current download files. Make sure that you are using the correct media or downloaded file. Continuing with a platform installation may require additional post-install configuration.
Do you want to continue?
This message occurs if you have selected a platform for installation that does not match the files you are trying to install (either from the installation DVD, USB or from downloaded installation files).
Cannot find file
<product>.tar in directory
<dvd_dir>
This error may appear during the Ansys installation if you have entered the wrong DVD pathname. Check Mounting the DVD Instructions for DVD Installations (Linux x64 Only) and enter the correct pathname for your platform.
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.
This message appears during an Ansys, Inc. product installation if the
installed license manager files are newer than the ones being installed.
You should always use the newest files. However, due to system format
changes or other unlikely scenarios, the date check could produce
incorrect results. To override the date check and force the installation
to always install the files from the media, regardless of the file
dates, re-run the installation with the -nodatecheck
option. We strongly recommend that you exercise caution when running the
installation with the -nodatecheck option; installing
older license files can result in licensing errors and the inability to
run Ansys, Inc. products.
Error, could not open display.
***Error, ANSYS242_DIR environment variable is not set. This is a fatal error – exiting.
This message indicates that the ANSYS242_DIR environment variable was not set where necessary for licensing. This environment variable (which is set in the scripts that run Ansys) should be set to the release-specific installation directory.
The following error messages are associated with the High Performance Computing solvers.
mpid: Error: HP MPI version incompatibility detected
You may encounter this or a similar message if you attempt to use Ansys 2024 R2 with a different version of MPI than is supported. See the Parallel Processing Guide for a complete list of supported MPI versions.
With some SuSE Linux configurations, the USB auto-mount function may cause the INSTALL command to appear as lowercase. Using the lowercase install command may cause extraneous files to be left behind after the Ansys product installation.
To correct this lowercase issue, un-mount the USB drive and manually re-mount the drive prior to installing Ansys products.