This has been reported as a successful fix in some cases.
: Open the ANSLIC_ADMIN Utility as an administrator, stop the Ansys license, and then start it again.
: Security software may prevent Ansys from executing necessary Windows script objects, or essential scripting libraries like ole32.dll or jscript.dll may not be correctly registered in the system. This has been reported as a successful fix in some cases
To resolve the "Ansyswbuexe encountered a problem a diagnostic file has been written new" error, follow these step-by-step troubleshooting steps:
Look at the error message for the specific path, or check C:\Users\YourUsername\AppData\Local\Temp . To resolve the "Ansyswbuexe encountered a problem a
Antivirus software or restrictive firewall settings blocking Ansys processes. Step-by-Step Troubleshooting Guide
The most crucial part of the error message is the phrase: “a diagnostic file has been written.” This file is not an error log in the traditional sense; it is a memory dump (often with a .dmp extension) or a detailed crash report. Its location is typically in the user’s temporary folder or the project’s solve directory (e.g., C:\Users\[Username]\AppData\Local\Temp\ or [Project Folder]_files\dp0\SYS\MECH\ ). Its location is typically in the user’s temporary
The Intel MPI library conflicts with the Windows network stack or antivirus firewalls.
When the error appears, a log file is generated. Navigate to the following directory to locate it: C:\Users\<YourUsername>\AppData\Roaming\Ansys\vXXX\Workbench\logs\ (Note: vXXX corresponds to your ANSYS version, e.g., v221, v232).