Known Issues and Limitations

The following are known issues at the time of release, as well as system and software limitations:

  • KDE is not supported on SuSE Linux Enterprise Server & Desktop 12.

  • When a job is submitted that requires the MAPDL solver, and no MAPDL license is available, the job may appear to be in the 'starting' state in the job monitor for up to 20 minutes before the issue is reported. Additionally, if you check your system processes (with ps on Linux or Task Manager on Windows), you may see some solver processes still running after 20 minutes. These may run for up to 80 minutes, but are small and do not consume significant resources.

  • When running or updating a Workbench project on a Linux machine that generates many files, such as a large number of Design Points running concurrently, the solver can fail with the following exception:

    System.IO.IOException: Too many open files

    To prevent this failure, increase the maximum number of files able to be opened at one time by running the ulimit command ulimit -n [limit] where limit is either a numerical value (for example, 1000000) or, “unlimited”.

  • When running Workbench on a Linux machine, it crashes when you select Extensions > ACT Start Page from the menu bar or click ACT Start Page on the Project tab toolbar. This crash is caused by the libtotem-mozplugin.x86_64 version 2.28.6-4.el6 dll package, used for video playback in browsers. To avoid the crash, uninstall the package.

  • The Excel feature in Workbench requires Microsoft Office Excel 2013 or 2016.

  • The Excel feature is only available on Windows systems.

  • In a project with retained design points, switching to a different up-to-date design point using the Set as Current menu option automatically updates the Excel system, which could be time-consuming if the spreadsheet contains macros or extensive calculations.

  • Files written by Ansys products cannot be synchronized with Microsoft's OneDrive file hosting service.

  • Workbench products do not support running a network user installation as local root administrator.

  • On Linux, transferring DesignModeler geometry from the geometry cell to a downstream HFSS Design system fails if the upstream geometry is not open in the DesignModeler editor. In this case an OnRefreshTransferData failed! error message is displayed. Open the geometry in DesignModeler before transferring it so that the transfer succeeds.

  • When Material Designer is linked to Engineering Data, modifying a material name in Material Designer does not change the corresponding material in Engineering Data but rather creates a new material with the new name. The prior material should be deleted from Engineering Data before updating downstream components.

  • Parameterizing a non-integer, non-zero number in a Forte project when your system is set to a European number format (the decimal separator uses a comma) causes the parameter value to be displayed as zero in Workbench. Ensure your system is set to a number format that uses a period as the decimal separator.

  • Workbench can stop working when updating multiple design points in one task through Remote Solve Manager installed on a Linux cluster. The following error message is displayed in the Remote Solve Manager Job Monitoring application:

    ClusterJobs Command Exit Code: 134

    Assertion at class.c:2876, condition 'iid <= 65535' not met

    To work around this issue, reduce the number of design points that are updated in each task.

  • When using Workbench on Linux systems, you cannot use a Mechanical APDL system to launch MAPDL when the graphics mode is set to 3D. You must use the X11 graphics mode.

  • Because Workbench and Ansys AEDT use two different unit systems, upstream parameter values are transferred to AEDT with SI unit values. There are no computations errors, but when you graphically display the design in AEDT, you cannot see the units as specified in Workbench. They are displayed as unitless values in SI.

  • If you select the Physics Definition check box in the Geometry cell properties after importing a Discovery file, then click Update Project or Refresh Project, the following error can occur:

    Data entity not found: /Schematic/Component:Setup

    To work around this issue, refresh each component one at a time.

  • Older Sherlock projects resumed in 2025 R1 require you to rescope Mechanical loads if you re-export Sherlock FEA or reinforcement data. After refreshing the new data into Mechanical, rescope the boundary conditions that use the Geometry Selection scoping method. This step must occur before the analysis can be updated again.

  • The following workflow produces an error:

    1. Drag and drop an external model CDB file into the schematic.

    2. Update the project.

    3. From the downstream Model cell, open Mechanical and notice the material assignments.

    4. Double-click the External Model Setup cell or right-click the Setup cell and select Edit from the context menu. This opens the External Model tab.

    5. Change the file Identifier (for example, from File1 to MYFILE) and change Number of Copies to 1.

    6. Update the downstream model cell again. You will notice that material are wrongly assigned.

  • For Workbench/Mechanical models involving an upstream system linked to a downstream system, if the model was previously saved in Windows and is now being opened in Linux, any updates done on the downstream system can cause an error message to be displayed.

    The error message indicates to relink the upstream system. Once the relink is done, you can update the downstream system and it should go back to normal state.