You are on page 1of 32

Known Issues and Limitations

ANSYS, Inc. Release 17.0


Southpointe January 2016
2600 ANSYS Drive ANSYS, Inc. is
Canonsburg, PA 15317 certified to ISO
9001:2008.
ansysinfo@ansys.com
http://www.ansys.com
(T) 724-746-3304
(F) 724-514-9494
Copyright and Trademark Information

© 2015 SAS IP, Inc. All rights reserved. Unauthorized use, distribution or duplication is prohibited.

ANSYS, ANSYS Workbench, Ansoft, AUTODYN, EKM, Engineering Knowledge Manager, CFX, FLUENT, HFSS, AIM
and any and all ANSYS, Inc. brand, product, service and feature names, logos and slogans are registered trademarks
or trademarks of ANSYS, Inc. or its subsidiaries in the United States or other countries. ICEM CFD is a trademark
used by ANSYS, Inc. under license. CFX is a trademark of Sony Corporation in Japan. All other brand, product,
service and feature names or trademarks are the property of their respective owners.

Disclaimer Notice

THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFID-
ENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software products
and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreement
that contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exporting
laws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software products
and documentation may be used, disclosed, transferred, or copied only in accordance with the terms and conditions
of that software license agreement.

ANSYS, Inc. is certified to ISO 9001:2008.

U.S. Government Rights

For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use,
duplication, or disclosure by the United States Government is subject to restrictions stated in the ANSYS, Inc.
software license agreement and FAR 12.212 (for non-DOD licenses).

Third-Party Software

See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software
and third-party software. If you are unable to access the Legal Notice, Contact ANSYS, Inc.

Published in the U.S.A.


Table of Contents
Introduction ................................................................................................................................................. v
1. Installation .............................................................................................................................................. 1
2. Licensing ................................................................................................................................................. 3
3. Platform Support .................................................................................................................................... 5
4. Documentation ....................................................................................................................................... 7
5. Advisories ............................................................................................................................................... 9
6. ANSYS Structural Products ................................................................................................................... 11
6.1. Mechanical ..................................................................................................................................... 11
6.2. Mechanical APDL ............................................................................................................................ 11
6.3. Autodyn ......................................................................................................................................... 11
6.4. Aqwa .............................................................................................................................................. 11
6.5. Beamcheck ..................................................................................................................................... 12
6.6. Fatjack ............................................................................................................................................ 12
6.7. ANSYS Composite PrepPost (ACP) ................................................................................................... 12
7. ANSYS Fluids Products .......................................................................................................................... 13
7.1. Fluent ............................................................................................................................................. 13
7.2. CFX ................................................................................................................................................ 14
7.3. TurboGrid ....................................................................................................................................... 14
7.4. BladeModeler ................................................................................................................................. 14
7.5. CFD-Post ........................................................................................................................................ 14
7.6. Polyflow ......................................................................................................................................... 14
7.7. Forte .............................................................................................................................................. 15
8. ANSYS Electronics Products .................................................................................................................. 17
8.1. Icepak ............................................................................................................................................ 17
9. ANSYS Geometry & Mesh Prep Products .............................................................................................. 19
9.1. CAD Connections & Integration ....................................................................................................... 19
9.2. DesignModeler ............................................................................................................................... 19
9.3. SpaceClaim ..................................................................................................................................... 19
9.4. Meshing ......................................................................................................................................... 20
9.5. IC Engine ........................................................................................................................................ 20
9.6. ICEM CFD ........................................................................................................................................ 20
9.7. Fluent Meshing ............................................................................................................................... 20
10. ANSYS Simulation Products ................................................................................................................ 21
10.1. Workbench ................................................................................................................................... 21
10.2. ACT .............................................................................................................................................. 21
10.3. Remote Solve Manager (RSM) ........................................................................................................ 21
10.4. EKM .............................................................................................................................................. 22
10.5. DesignXplorer ............................................................................................................................... 23
11. ANSYS AIM .......................................................................................................................................... 25

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
iv of ANSYS, Inc. and its subsidiaries and affiliates.
Introduction
The following information is relevant to ANSYS, Inc. Release 17.0. The entries describe known non-op-
erational behavior, an error, or limitation at the time of this release. Work-arounds for these items, if
available, are included in the respective descriptions. Inclusion in this document does not imply the issues
and limitations are applicable to future releases.

The parenthetical numbers associated with each entry are reference numbers corresponding to an in-
ternal error tracking system. The numbers are included to help to facilitate ANSYS, Inc. technical support
and help to ensure that the issue described in the entry is resolved.

Service packs may become available for some of the entries. See the ANSYS Customer Portal for inform-
ation about service packs and any additional items not included in this document. First-time users of
the customer portal must register via the ANSYS Web site (www.ansys.com) to create a password.

Additional known issues and limitations may be found in the product Help and/or release notes, both
accessible via the ANSYS Help Viewer within the product.

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. v
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
vi of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Installation
No known issues, limitations, or documentation inaccuracies.

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 1
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 2: Licensing
No known issues, limitations, or documentation inaccuracies.

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 3
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
4 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 3: Platform Support
No known issues, limitations, or documentation inaccuracies.

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 5
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
6 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 4: Documentation
CFX
In “ANSYS Documentation”> “CFX”> “Modeling Guide”> “Expert Control Parameters”> “CFX-Solver Expert
Control Parameters”> “Discretization Parameters”, the default value for parameter “ipmt area density
clip” is documented incorrectly. The actual default value is “t”. (118971)

In "ANSYS Documentation" > "TurboSystem" > "Workflows" > "2.8 Quick Pump Tutorial" > "2.8.1.
Designing the Blade and Creating the Mesh", step 14 currently states:

“In the details view, set Size Factor to 0.7”


This should read:

“In the details view, set Size Factor to 0.8 and Cutoff Edge Split Factor> Trailing to 0.3.”
(119129)

EKM
In section 6.2. Specifying General Server Settings of the EKM Administration Guide, the description of
clusterVisibleDirectories setting should read:

“You only need to specify this setting if users will be choosing working directories for batch
jobs (instead of using the auto-created directories), or if jobSourceRootPath is set to a re-
lative path for a Linux installation.
If jobSourceRootPath is a full/absolute path, EKM automatically considers the path to be
visible, so you do not need to specify that path in the clusterVisibleDirectories setting.
If EKM and RSM are integrating with a Linux cluster, you can specify an absolute or relative
path for jobSourceRootPath. You must always specify full paths for clusterVisible-
Directories.”
(120064)

In section 8.6 EKM and RSM Job Directories of the EKM Administration Guide, the following statement
should be omitted: "If users will be submitting jobs to EKM from Workbench, and Workbench and RSM
are on different machines that refer to the job directory using different paths, then you must specify a
pathMapping in the ekm.xml file. This ensures that EKM passes a job path to RSM that RSM can re-
cognize. See Specifying Remote Process Policies (<remoteProcess>)". (120064)

ICEM CFD
In multiple locations throughout the ICEM CFD Help Manual, duplicate equations are displayed (printed).
(119813)

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 7
Documentation

Mechanical APDL
In the "Mechanical APDL as a Server User's Guide", "Chapter 3: Mechanical APDL as a Server Matlab
Toolbox" is documentation of a beta feature which has not been formally tested nor was intended to
be included in the product documentation. This chapter will be removed at Release 17.1. (120003)

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
8 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 5: Advisories
No known issues, limitations, or documentation inaccuracies.

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 9
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
10 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 6: ANSYS Structural Products
6.1. Mechanical
External layered shell definitions may not be transferred correctly when multiple ACP systems are linked
to an Explicit Dyanmics system on Linux only. Thickness and Material results should be used to verify
that external layered shell information has been transferred correctly. (112863)

For Imported Loads / Imported Traces, depending on the Graphics Card / Display Monitor combination,
display of source points may require excessive memory and hang the product if large number of source
points (2 million and above) are present. It is recommended not to turn Source Points display ON if this
issue is observed. (118425)

Eulerian point trackers scoped to a vertex of an Eulerian body may not provide results at the correct
location on the Linux operating system. Work-around: On the operating system only, use Eulerian point
trackers defined by coordinates using the User Defined Location option (119052)

6.2. Mechanical APDL


Mechanical APDL has not yet been certified for Windows 10. Certain graphical user interface (GUI) ele-
ments may not work properly when running the program on the new operating system. (117804)

In a structural-pore-fluid-diffusion analysis, the TB,PM,,,,SP and TB,PM,,,,FP commands are used to define
the bulk moduli of the solid skeleton and the fluid phase respectively within porous media (to account
for porous media compressibility). In ANSYS 17.0, the porous media is erroneously considered to be always
incompressible (with regard to the continuity equation), thus the bulk moduli definition is ineffective.
(119451)

6.3. Autodyn
When using more than one AUTODYN component system from within a single Workbench environment
only one can be open at a single time. Two workarounds are available:

• Do not open more than one AUTODYN component at the same time

• Create a Workbench project for each single AUTODYN component system.

• Open the (admodel_0.ad) modelfile outside the Mechanical Framework in standalone AUTODYN by
double clicking on the autodyn.exe

(119302)

6.4. Aqwa
No known issues, limitations, or documentation inaccuracies.

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 11
ANSYS Structural Products

6.5. Beamcheck
No known issues, limitations, or documentation inaccuracies.

6.6. Fatjack
No known issues, limitations, or documentation inaccuracies.

6.7. ANSYS Composite PrepPost (ACP)


No known issues, limitations, or documentation inaccuracies.

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
12 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 7: ANSYS Fluids Products
7.1. Fluent
When the Across Zones option is disabled in the Partition Mesh dialog box with Metis selected as the
partitioning method, Fluent may crash depending on the case and core count. Work-around: If the Across
Zones option must be disabled, choose a partitioning method other than Metis. (119755)

Specific to quantities for which units have been specified that have an offset from the base SI unit,
the plots of report definitions will be in the SI base unit but the y-axis will erroneously display the chosen
unit. Example: if Celsius units are chosen for Temperature, a report definition plot will be plotted us-
ing units of Kelvin, but will incorrectly display the unit as "C." Using units of Rankine for temperature will
work correctly as no offset appears in the conversion from Kelvin to Rankine. (119554)

For 2D cases, moment report definitions produce erroneous results. Work-around: Use al moment
monitor. (119261)

If you use the solve/report-definitions/convert-monitors-to-report-defns text command to convert a


monitor that saves output to a file and try to continue a calculation without removing or renaming the
existing monitor file, you will receive a warning message. (119032)

If a zone that is part of an evaluated report definition is deactivated during a calculation, then that report
definition will become invalid and this will interrupt the solution. Work-around: Manually correct the
zone list for the invalid report definition. (119022)

Creating/plotting FFT files using a report definition yields an error message and warning that an interrupt
occurred while reading the journal file. (119027)

The net result of a flux report definition will be incorrect if porous jump, radiator, and/or fan boundary
types are selected in addition to other types for computation as the values from zones of such types
will not be included. (119030)

Interface values computed from reports can be more accurate than those from monitors due to different
interpolation techniques. (118877)

When running Fluent in Workbench, you cannot use an input parameter to define the thickness value
for a wall with multiple shell conduction layers. (119137)

When running Fluent in Workbench on Linux, the Solution tab (opened using the "Show Solution
Monitoring" option in the Solution cell context menu) does not properly display the Fluent Solution
Images (enabled in the View menu). 119567)

Specific to the Red Hat 7.1 operating system with AMD graphics cards, after launching a Fluent applic-
ation with the default settings, the File/Exit ribbon tab item does not function as expected. Work-
around: Use the x11 graphics driver instead of OpenGL. (118461)

While reading data from a CGNS file, Fluent checks the cell dimension of a CGNS base node, where the
cell dimension is 3 for volume cells, 2 for surface cells and 1 for line cells. If it does not match the Fluent

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 13
ANSYS Fluids Products

case dimension (that is, 3 and 2 for 3d and 2d cases respectively), Fluent gives a message and fails to
read further data. (119195)

When running Fluent in parallel, you may experience issues when solving an overset meshing problem
that contains mesh interfaces. (118739)

The following Fluent as a Server commands have been removed, in order to improve the general per-
formance:

• fluent.set_server_output_silent

• fluent.set_server_output_verbose

• fluent.show_output

(103137)

Reading very large mesh files into Fluent solver sessions with very small core counts (greater than 100
million cells or faces per core) may cause problems. Work-around: Increase the core count or read the
files in serial.(120041)

7.2. CFX
In the CFX-Solver Manager, the "Override Default Precision" setting on the Partitioner, Solver and Inter-
polator tabs does not have any effect. The "Double Precision" setting on the Run Definition tab will be
used for all the executables instead. Work-around: Start the run from the command line, or perform
the partitioner step separately if it is desired to override just the precision of the partitioner executable.
(118972)

7.3. TurboGrid
No known issues, limitations, or documentation inaccuracies.

7.4. BladeModeler
No known issues, limitations, or documentation inaccuracies.

7.5. CFD-Post
No known issues, limitations, or documentation inaccuracies.

7.6. Polyflow
The Help tab in ANSYS Polydata will not display information about the following menus (used as part
of a fluid-fluid contact problem) when you use the Help> Current menu pull-down menu item.

• Define fluid/fluid contacts

• Modification of a fluid/fluid contact

• Free surface selection

• Fluid/fluid contact: options for mapping

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
14 of ANSYS, Inc. and its subsidiaries and affiliates.
Forte

Work-around: Information about setting up a fluid-fluid contact problem is available in the Polyflow
User’s Guide, which is viewable in the product Help Viewer (accessed through the Help>Polyflow User's
Guide... pull-down menu item). (100770)

Selecting the “Free surface along boundary/subdomain x” menu item in the Inverse prediction manage-
ment menu yields a Polydata crash. Work-around: Define the outlet of each free surface taking part in
the inverse prediction in the free surface menu. (119624)

When creating a mesh for Polyflow, the Export Unit can be set to control the units in the exported mesh
file. When using Assembly Meshing, the mesh is exported in the correct units but the tag for units in
the file is not. This leads to an incorrect mesh conversion log in Polydata. Work-around: When using
Assembly Meshing, disregard the comment on units in the conversion log and double-check the actual
dimensions of the mesh. (119736)

7.7. Forte
No known issues, limitations, or documentation inaccuracies.

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 15
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
16 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 8: ANSYS Electronics Products
8.1. Icepak
Changes to network node properties are not supported for solution restarts using the full data option.
(119654)

Only binary encoded PPM image files can be used as a source for applying texture to only Solid/Solid-
wire shaded objects. Any other image file format, including ASCII encoded PPM image, causes Icepak
to close without a warning message. Texture is applied on faceted object such as Prism blocks, 2D
plates, board, heat sink and curvaceous objects such as cylinder or sphere. Work-around: To properly
adjust texture for viewing complete image, use texture scaling property to shrink or stretch image texture.
A texture can be applied to multiple objects for only solid/solid-wire shaded objects of same type by
editing them together. To unload texture from all of them, select No texture for Texture in
the Edit panel of each object separately. (119880)

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 17
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
18 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 9: ANSYS Geometry & Mesh Prep Products
9.1. CAD Connections & Integration
No known issues, limitations, or documentation inaccuracies.

9.2. DesignModeler
No known issues, limitations, or documentation inaccuracies.

9.3. SpaceClaim
When negative values are specified for geometry length and angle parameters used by Pull and Move
operations, with AIM's embedded Geometry Modeling or the standalone SpaceClaim Direct Modeler, their
directions may be reversed and their values made positive. Subsequent design point updates may
produce unexpected results. For example, consider a part being moved in the positive X direction by
a distance (length) parameter, P1, and a series of design points with values P1 = 2mm, P1 = -1mm, and
P1 = 3mm. If you update them in that sequence, the first design point will move the part 2mm in the
positive X direction, the second will move the part 1mm in the negative X direction, and the third will
move the part 3mm in the negative X direction (even though the value is positive). (98556)

If you intend to keep the same material, some material property information will be lost once clicking
the OK button in the Material drop-down menu of the Properties panel. (119155)

On Windows 10 operating systems, SpaceClaim is not able to import material properties using a CAD
plug-in. (119255)

There are missing context sensitive Help links for some tools in Simplified and Traditional Chinese,
Korean and Italian. Access the missing Help links via SpaceClaim Options> Advanced> Language to
change the default language to English. (119388)

Ruler dimensions do not maintain negative values. When parameters are generated in SpaceClaim for
use with a Workbench analysis, the parameters always result in a positive value. For example, entering
-5 for translation along an axis results in the geometry moving to the left of the origin, but the final
value of the dimension is 5. (119388)

Measurement Groups do not immediately update with changes to Driving Dimension Groups. (119388)

JT, SolidWorks, Solid Edge and Parasolid CAD files saved with non-English characters (i.e. Traditional
and Simplified Chinese, Korean, French, languages that use accents, etc.) will not display the model
name correctly in the SpaceClaim Structure Tree. Work-around: Save the files using English charac-
ters.(119388)

QIF files containing multiple components may not import all of the components. (119388)

Deleting a model from the SpaceClaim Structure tree while in the Thickness tool may result in a
graphics crash. (119388)

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 19
ANSYS Geometry & Mesh Prep Products

Hidden geometry is not transferred to ANSYS Workbench from SpaceClaim. (119388)

The SpaceClaim Scripting tool is Beta. (119388)

9.4. Meshing
When modifying a mesh in a downstream system, if you set the Model Assembly control to not be read-
only, and if the upstream system has a connected mesh, a warning message is displayed warning you
that the mesh connections from the model assembly will be lost and that the base mesh will be regen-
erated. No user action is necessary. (96640)

9.5. IC Engine
Start with single topology in Geometry and runing the case in Fluent until valve opening, yields an error.
Work-around: Use Keygrids in such cases, which will replace the mesh before valve opening. (105537)

Changing the parameters of the Input Manager and generating after geometry is decomposed may be
unsuccessful. Work-around: Re-decompose the geometry using Decompose command. (116187)

9.6. ICEM CFD


See the Documentation section of this document for items specific to the ANSYS ICEM CFD Help
Manual.

9.7. Fluent Meshing


Prism generation can be slower up to 20% when it is performed after many computation intensive op-
erations such as size field computations and surface remeshing in a same session. Work-around: Call
(%tg-compact-list) before prism generation or generate volume meshes in separate session. (116486)

The graphical operations performance may be hampered while using cut planes, for large mesh dis-
plays. Work-around: Set a cx var using (cxsetvar ‘graphics/show-cut-edges? #f ) (116670)

Polyhedral mesh may generate some isolated cells. Work-around: Use mesh check to see if there is a
warning "boundary face in interior zone", apply meshing/mesh/separate/separate-cell-by-region and
delete the separated isolated cell zone (119498)

Based on number of partitions, there could be some difference between Serial and Parallel (Auto-Parti-
tioning) while Pre-Ignore happens in Prism meshing (119543)

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
20 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 10: ANSYS Simulation Products
10.1. Workbench
On SUSE Enterprise 12, when using a kernel with a version greater than 3.12.36-38.1, Workbench or RSM
may be unstable. This is due to a change being introduced to the kernel which is known to cause in-
stability in the mono runtime. Although this has been fixed in the kernel source, this change has not
been applied to the latest SUSE Enterprise 12 kernel at the time of this writing, kernel version 3.12.51-
52.31.1. For best results, use kernel revision 3.12.36-38.1 or lower. If this is impractical, it is possible to
work around this problem by adjusting the mono nursery size. This can be done by setting
the MONO_GC_PARAMS environment variable. This must be set to a power of 2. An example would
be:

csh: setenv MONO_GC_PARAMS nursery-size=32m


sh/bash: export MONO_GC_PARAMS=nursery-size=32m
(117852)

When running Workbench on Linux, crashes have been observed after errors in simulation. In this situ-
ation, removing the file Addins/Configuration/Ansoft.xml from your installation may prevent the crash.
Note, however, that removal of this file will also disable EBU integration with Workbench. (119095)

In Model-to-Model workflows (i.e. model assembly), if an upstream system is duplicated and an attempt
is made to connect the duplicated system to a downstream system, the duplicated upstream's Model
cell will be in an incorrect state (up-to-date) and will not transfer the data downstream. Work-around:
Upon linking the duplicate upstream system to the downstream, perform a Clear Generated Data or
Reset on the upstream system's Model cell, and then re-update the Model cell. (119556)

System Coupling
No known issues, limitations, or documentation inaccuracies.

10.2. ACT
No known issues, limitations, or documentation inaccuracies.

10.3. Remote Solve Manager (RSM)


Additional detailed information about these issues can be obtained by contacting ANSYS, Inc. technical
support.

When configuring RSM for use with EKM, the ClusterConfiguration (.rsmcc file) for an SGE/UGE cluster
will not support parallel jobs when it is configured as follows:

<nativeSetting name="SGE_PE_SHARED">your_mpi</nativeSetting>
<nativeSetting name="SGE_PE_DISTRIBUTED">your_mpi</nativeSetting>
With this configuration, all parallel SGE jobs are submitted using the shared memory parallel environment
of SGE, regardless of whether the job is configured to run as shared or distributed. (119568)

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 21
ANSYS Simulation Products

If the user makes an error in the set-up of RSM this may result in a set-up failure warning message when
a component update is submitted from Workbench. Generation of the warning message can cause the
Workbench user interface to become frozen. For example, providing an incorrect alternate account
password will trigger an error message that causes a freeze.Work-around: Correct the error described
in the message and restart Workbench to resubmit the job. (120175)

10.4. EKM
Additional detailed information about these issues can be obtained by contacting ANSYS, Inc. technical
support.

The ANSYS EKM server product installation on Windows prevents you from setting the EKM temp dir-
ectory to a UNC path, which causes the default value of the root directory of the fileTransferSer-
vice to be unsuitable for a multi-node EKM server. Work-around: You must manually change the root
directory of fileTransferService in the ekm.xml file to a shared directory on the cluster file
system. (118763)

Errors may occur when uploading large files to EKM via the File Transfer Client when EKM is configured
to use a front-end Apache web server with the mod_cluster load balancer, and is configured to use the
AJP protocol. The AJP listener in the undertow subsystem must have the max-post-size attribute
set to 0. (118816)

When EKM is configured to use a front-end Apache webserver with the mod_cluster load balancer, the
ProxyTimeout directive (which determines how long the mod_cluster load balancer will listen for a
response for the JBoss node) is not set by default, and the default value of 300 seconds (5 minutes)
may be too short for some operations, such as large file transfers. Setting this directive to a higher value
resolves this issue. (118835)

Attempting to interrupt a distributed MAPDL job that was started using the Start MAPDL Job template
does not work. The job keeps running, and the journaling status “Reading Input File” is displayed in
the job view in EKM. (117358)

Parallel (multi-core) project updates and design point updates may fail for Workbench projects containing
Mechanical systems. Use the 'Serial' processing option for such projects. (117577)

When creating a connection to a file or folder on a remote file server, an error occurs if the remote file
server address points to a local path on the EKM server, and the rsmLauncherURL setting in the
ekm.xml file is pointing to a different machine. (118324)

A multi-configuration simulation run from the built-in CFX job template may fail. Please contact ANSYS
EKM support for an updated template. (118395)

When using the command line during an MAPDL job that was started with the Start MAPDL job tem-
plate, specifying a path with a space causes the solver to hang. (118823)

The sessionTimeout setting in the ekm.xml file will not take effect if you leave EKM on a page
that displays an auto-updating status, such as a job view or the Extraction Monitor page. The session
will not time out, meaning that you will not be signed out of EKM, and the EKM license will remain
checked out. (119057)

The simulation details report is not being updated following a project update or design point update
of a Release 17.0 Workbench project. To verify that the update was successful, check the job's Transcript
tab. If the job is no longer available, download the project and open it in Workbench. (119734)

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
22 of ANSYS, Inc. and its subsidiaries and affiliates.
DesignXplorer

An “AccessControlException" error may be displayed in the interface if a script is trying to access a


location that the server does not have permission to access. To resolve this issue, add the full path
shown in the error to the script.policy file located in ekm\v170\ekm-server\conf. (119827)

10.5. DesignXplorer
No known issues, limitations, or documentation inaccuracies.

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 23
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
24 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 11: ANSYS AIM
Negative dimension values can invert the direction vector of SpaceClaim operations that they are asso-
ciated with; this change is applied to the current and subsequent design point updates. As a result,
when a Workbench input parameter is used as a driving dimension for a SpaceClaim geometry, negative
dimension values may result in incorrect or unexpected geometric changes. (112386)

On rare occasions, an archive of a fluid flow workflow will be corrupt and cannot be archived; this occurs
when opening a project containing a fluid flow workflow which was not solved and then immediately
archiving the project. Work-around: Re-open the original fluid flow project and execute any opera-
tion/command before archiving. (116713)

Under Tools> Options, ANSYS AIM does not respect the settings listed under the Appearance and Graphics
Interaction categories.(117027)

If a region interface has faces from separate parts on one side, then this can cause problems such as
hangs or software failures when solving or post-processing. Work-around: To avoid this problem the
interface can be broken down into multiple interfaces. (119084)

Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 25
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
26 of ANSYS, Inc. and its subsidiaries and affiliates.

You might also like