The items listed below apply only to the Mechanical APDL product.
On some systems, you may need to use the ‘nohup’ option to allow batch jobs to continue running after you log out of a session. If you are running via the Launcher, select We do not recommend using this setting on systems that automatically set ‘nohup.’
Missing or erroneous documentation files for user interface. Command ignored.
Verify that the documentation list file for the user interface exists in the /ansys_inc/v242/ansys/gui/en-us/UIDL subdirectory.
ls -l /ansys_inc/v242/ansys/gui/en-us/UIDL/menulist.ans
The system should respond with:
-rw-r--r-- 1 root 23 Jan 8 11:50 /ansys_inc/v242/ansys/gui
/en-us/UIDL/menulist.ansMake sure that the pathnames in the menulist.ans file are correct.
Some of the more common error messages follow. See the Ansys Licensing Guide for licensing-related launcher messages.
***Cannot create required
<profile> file. Therefore,
cannot write to profile information during this launcher
session.
If you see this error, you cannot add or modify profile information
during this launcher session. Verify that you have write access to the
directory and restart the launcher session. Typically, this directory is
C:\Documents and Settings\<user
name>\Application
Data\Ansys\v242\launcher on Windows or
~/.ansys/v242/launcher on
Linux.
The following error messages occur if you are running Mechanical APDL in a directory in which the user does not have write permission, or if Mechanical APDL files (that is, Jobname.RST, Jobname.DB) exist in the current directory but you do not have write permissions to the files. The specific messages that appear on each system are shown below.
Input/Output Error 177: Create Failure
In Procedure: fappnd
At Line: 72
Statement: Formatted WRITE
Unit: 19
forrtl: Permission denied
forrtl: severe (9): permission to access file denied, unit 19, file /build/v242/ansys/objs