Errors, though undesirable, are inevitable in software products as large and as complex as Ansys products, and even the most rigorous product tests do not always catch every error. Ansys' policy is to correct errors in our products and/or notify customers about the errors and provide workarounds as quickly as possible.
Error Reporting and Resolution
Anyone can report an error in Ansys products. Once an error is reported or found, it is tracked in the bug tracking system and the resolution process begins. If a customer reported the error, Ansys will notify the customer when it's resolved. All efforts are made to correct any bugs affecting customers as quickly as possible.
Class 3 Errors — which allow the program execution to complete and yield results that may be wrong but not easily identifiable as incorrect — are accorded a high priority in the investigation and resolution process. All Class 3 Error Reports are posted on the customer portal.
For information on obtaining Ansys Class 3 Error Reports, contact the Quality Assurance team at ansys-qa-services@ansys.com.
Service Packs
To minimize the impact of errors on customers between major releases of our products, Ansys occasionally issues service pack releases that include error corrections. A Service Pack is a release delivering little or no new functionality and primarily intended to provide customers with urgently needed bug fixes to existing Major or Focused Release software. The Service Pack may be delivered as a patch to be applied to an existing software installation.
How to report Errors?
When you discover errors in any Ansys product, always inform an Ansys channel partner or technical support staff member.
When reporting an error, describe it as specifically as possible. The more information and details you provide to your support contact, the faster we can diagnose and solve the problem. You can also help your support contact and us by following these tips:
- Document the circumstances that produced the error. For example, how was your Ansys environment configured when the error occurred?
- What type of analysis were you doing? What analysis options were active? What did you do (or what happened) immediately before the error occurred?
- Try to reproduce the error and save output data if possible. Forward the data to your support contact along with your input file and error report.
- Provide information about any temporary workarounds you found for the error.
- Provide information if the analysis that produced the error differed in any way from similar analyses that ran without problems.