CFD Online Discussion Forums - ANSYS Workbench mesh crashes (ANSYSWBU.exe problem)

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)

- ANSYS (https://www.cfd-online.com/Forums/ansys/)

- - ANSYS Workbench mesh crashes (ANSYSWBU.exe problem) (https://www.cfd-online.com/Forums/ansys/77498-ansys-workbench-mesh-crashes-ansyswbu-exe-problem.html)

Quote:

Originally Posted by sogold (Post 612397)

Hello!! I have the same problem. I start the Ansys 12.1, but when I start the DesignModeler or Mesh appears:

AnsysWBU.exe encountered a problem. A diagnostic file has been written:
..../AppData/Local/Temp/AnsysWBDumpFile.dmp

I did everything that you said in the post: update drivers, install the environment variable ANS_OLD_ATTACH...and I work without Ethernet and I don't know what do! please help me!

hi, sogold, I solved my problem by following this post:
http://www.cfd-online.com/Forums/ans...tml#post500479

Quote:

Originally Posted by Soitin (Post 577391)

In my case it was a problem of interference ANSYSWBU.exe with program for sound driver 'Nahimic for MSI'. The error was disappeared when I removed 'Nahimic.exe' from autorun. The challenge was hard...

System description:
Laptop MSI GE62
CPU Core i7 5700-HQ
RAM 16 Gb
OS Windows 10 Home
Ansys WB 16.0.

Thank you very much Soitin!!
Disabling "Nahimic" from autostart also worked to me (I also have a MSI laptop).
It really had to be a hard work to find this out!
Still, I think ours was not exactly the same ANSYSWBU.exe problem... but very useful tip for all the MSI users.
Thanks

Hello!! I have the same problem. I start the Ansys 18.1, but when I start the DesignModeler or Mesh appears:

AnsysWBU.exe encountered a problem. A diagnostic file has been written:
..../AppData/Local/Temp/AnsysWBDumpFile.dmp

please any help?

Quote:

Originally Posted by emreg (Post 336234)

click folder ANSYS (in where it locates , i guess drive C: ) with ur mouse button and select properties..

leave all the permissions checked on security tab..

inform me if it works.

Hello, I have tried this, but it didn´t work, so that I uninstall and instal program again, and now is everything all right. I know it´s not very simple way, but it works :)

Thank you! useful in 2018 too!

Hi guys, I have the same message (AnsysWBU.exe encountered a problem. A diagnostic file has been written:
..../AppData/Local/Temp/AnsysWBDumpFile.dmp)
My problem is a little different: DM works but when I decompose my geometry (I'm using IC engine Fluent), then the message appears and the decomposition stops. I just tried to change the name of directory and other things you suggest but nothing.

I use version 17, but I tried with 18.1 and there the same problem at the same point of decomposition. My PC is Dell XPS 15, 16Gb RAM, i7, intel HD 530. If someone has some advice, I'm gratefull. Thanks

ANSYSWBU.exe problem

Hello Laura,

What worked for me in version 17 was ending tasks of some programms that got in conflict with ANSYS at certain point (specifically in my case one called Nahimic). You may also want to prevent them to autorun at Windows startup.

If this does not work, you can also try running ANSYS with a dedicated GPU, which you most probably have,but maybe don't use (I have found out that some computers try to avoid it to save resources).

Give it a try.

Quote:

Originally Posted by Héctor Lodoso (Post 705398)

Hi Héctor! First of all, thanks a lot for your reply. I don't have Nahimic on my PC so it's not the problem. I read on Ansys webpage https://www.ansys.com/-/media/ansys/...s-aa-v9-i1.pdf
that my GPU (NVIDIA GeForce GTX 960M) isn't recommended beacuse it's a gaming class card. Anyway, the decomposition works with a different engine geometry, do you think it's possible that the problem is linked with the geometry? I really appreciated your kindness.

Best regards.

Running fluent in workbench in v191 on WIndows 10.
When it comes to Mesh, it show 3 messages:
1.ANSYSWBU.exe encountered a problem. A diagnostic file has been written: C:\...\Temp\AnsysWBDumpFile.dmp.
2.Update failed for the Mesh component in Fluid Flow (Fluent). Unable to update model. Either the application crashed or Workbench lost communication with it.
3.(DP 0) Unable to initialize addins in Meshing. Either the application crashed or Workbench lost communication with it (No connection could be made because the target machine actively refused it XXX.XXX.XXX.XXX:XXXXX).

※I followed ntech's method, but the problem is still there.

※I tried Maks001's method, but the problem is still there.
a.My graphic card is Intel(R) HD Graphics 630. I have updated the driver today, but the problem is still there.
b.Changing the folder name"C:\Users\...\AppData\Roaming\Ansys" will result in a fewer items in toolbox in workbench.
Changing the folder name"C:\Users\...\AppData\Roaming\Ansys\v191", but the problem is still there.

※I deactivated the graphic card from the control panel, but the problem is still there.

I don't understand what "Workbench lost communication with it" means.

201905
OK...I remove v191 and reinstall it. Then The problem solved.
I think that it is due to windows update.

Try to suppress surface in ansys mechancial that has zero elements/nodes ( you can see by clicking on "Worksheet" option on the top of ansys mechancial. this could be one of the solution.)

Quote:

Originally Posted by ntech (Post 500479)

I'm using Ansys 15.0 and windows7 64bit, seems to be the only combination having this problem. After two weeks I finally found a solution. You might need some experties to adapt it to your case depending on your version of Ansys and type of windows 7.

Here is it

1.
Check to make sure the following folders exist
C:\WINDOWS
C:\WINDOWS\System32
C:\WINDOWS\System32\wbem

2.
Press your "start" button and type "cmd" (Command Prompt DOS) right click and run as administrator'.
You should have "c:\windows\system32>_" in the black window

Type in the following one after the other and press enter.

regsvr32.exe ole32.dll
regsvr32.exe atl.dll
regsvr32.exe oleaut32.dll
regsvr32.exe scrrun.dll

regsvr32.exe jscript.dll

regsvr32.exe vbscript.dll

Between step 2 and 3, you might have to restart your system OR use the task manager. When you open the task manager, end every process related to ansys (hint: they will usually be at the top and ansys will be visible in the name and/or descripition section Under "processes" tab in the task bar.

3.
Rename v150 from %APPDATA%\ansys\v150 to v150.old (where %APPDATA% is where your APPDATA variable is set to - 'Just type %APPDATA% in the Explorer Address bar' and it will take you there).
Rename .ansys from %TEMP% to old.ansys (same as above, just type: %TEMP% in the address bar)

4.
Run the ProductConfig.exe from C:\Program Files\ANSYSInc\v150\commonfiles\tools\winx64
and configure the application again, by right-clicking the productconfig.exe file and select 'Run as Administrator',
First click on "Add .Net security exception for ANSYS, Inc products"
Secondly click on "configure products" and select everything..

5.
Run the CLIENT ANSLIC_ADMIN Utility > Set license preferences for user... > v150 and make sure that the license options are set correctly here, (license order you want to have and that is showing the features you will use with ANSYS), so that the new preferences file is created.

6.
Check the graphics driver for the card installed on the machine and make sure it is running the latest driver. If not, update the driver.

Many part of this tread has offered the solution prescribed here in bits, essentially this is everything combined together.

Enjoy Ansys.

I did all of these steps, and finally it worked for me too. Thanks.

The system properties:
- windows 7, 64 bit
- graphic: ATI Radeon

I have faced error in Ansys 2019 while Model Update after geometry uploaded Error while waiting for Mechanical initialization to complete. Either the application crashed or Workbench lost communication with it.
Please help me for same problem, if any solution.

Quote:

Originally Posted by fr33m4n (Post 434898)

I had the same problem and resolve it with a new user profil in windows.
Rename the profil user to create or regenerate a new one.
I try to practice solution you give but they didn't work in my case.
When i try with another user profile, Workbench works well ...

I tried what you said and actually it works!! But why is that, and what if I need to resolve the problem in the old profile.

Quote:

Originally Posted by reggenzi (Post 332915)

>>START
>>COMPUTER (Right Click)
>>Properties
>>Advanced System Settings
>>Environment Variables

Then

On System variables select -> New
On variable name -> ANS_OLD_ATTACH
On variable value -> 1

OK & Save

I having the same issue here, after setting the new variable ANS_OLD_ATTACH. Please help me..

have you all solved the problem? I am using the ANSYS 13 and it still has the problem. dickssportinggoods feedback www.lowes.com survey

It is not working for me either

Hello! This is still an issue in 2023R1, on Windows 11.

I only followed steps 3 and 4 and that resolved the issue for me.

As a reminder, steps 3 and 4 was:
"

Quote:

3.
Rename v150 from %APPDATA%\ansys\v150 to v150.old (where %APPDATA% is where your APPDATA variable is set to - 'Just type %APPDATA% in the Explorer Address bar' and it will take you there).
Rename .ansys from %TEMP% to old.ansys (same as above, just type: %TEMP% in the address bar)

4.
Run the ProductConfig.exe from C:\Program Files\ANSYSInc\v150\commonfiles\tools\winx64
and configure the application again, by right-clicking the productconfig.exe file and select 'Run as Administrator',
First click on "Add .Net security exception for ANSYS, Inc products"
Secondly click on "configure products" and select everything..

"

The steps slightly changed though. Obviously, in Step 3, "v150" needs to change to whatever installation you currently have, mine was v231.

Also, Step 4, I had to run "Product and CAD Configuration 2023 R1" from the Start Menu, as the method mentioned above did not work for me - still running it as Administrator though! The rest of the steps, adding ".Net.... " and etc. still remained the same.

Another potential issue that it could have been: I had multizone meshing enabled with Ansys Mechanical Meshing, and following the above steps reset all of the settings back to default. Perhaps there was some issue there?