|
LuckyTran, thank you very much for your reply.
I checked and double checked everything in the case, but finally I solved the problem by setting up the case again from cero. |
Just a suggestion to this problem that might help someone:
I solved an exact problem when I chose to set my inlet (mass-flow) direction (direction specification method) as " Normal to boundary". Basically as I can understand it was going backwards or something. I hope this helps. Frank |
Check your display driver
Hi folks,
I'm going to add in my solution. I'm using Fluent 16 and I also recently had issues with the program having random crashes (both during problem setup and during a solution run). I noticed that just before crashing, the monitor would usually flick off for a second or two before coming back with Fluent gone. I had recently changed out video cards and had Fluent using the GPU for a boost (GPGPU). I suspect there was a problem with the GPU calls being misread by the new GPU, resulting in the critical failures. Once I unchecked the box, Fluent worked like normal again. So if you are having this random crashing problem and you are using at least Fluent 15, you might check to see if it's a GPU acceleration issue. Edit: I checked my Windows event viewer and found that it was, indeed, the display driver that is causing the problem. Quote:
In fact, minimizing the window and letting the program run seemed to keep the error at bay. So whatever the problem is, it appears to be related to Nvidia and its drivers. |
Failure
Can anyone help me. I have similar problem. Ansys Fluent is working for about an hour and then disappears. It is leaving behind error files equal to number of threads that he is working on, displayed in notepad files but only node 0 file has a message inside:
Error [node 0] [time 14.06.2017 12:37:21] Abnormal Exit! and an additional file with number 999999 with same text but coresponding number. |
Error
Please help me.
|
fluent error 99999
I have the facing same problem which is error 99999 in parallel fluent. Fluent disappears without any warning.
any advice and suggestions will be greatly appreciated Thanks. |
This is also a problem I am facing. Moreover, I have been in contact with ANSYS for weeks. I have to say this is very disappointing after having invested and having worked with ANSYS all these years.
I really think ANSYS should provide all the info and support to users facing this simple yet abstract error: "Abnormal exit"!!! The problems related to the compilation of UDF codes remain unsolved as well by the way! There is no support record nonwhatsoever in their customer portal as well! |
fluent error
[QUOTE=shivakumar;545206]Thanks for the reply.. Nothing worked for me, still the fluent is spitting the same error.[/QUOTE
i also experienced in the fluent error 9999 in the log file and it causes the unexpected closing of fluent file and lost all data, i think its problem with licence if you are using academic version and you using parellel running it cause fluent error 9999 try to use serial running option sorry any kind of mistake from me iam new member of this online forum |
Quote:
Am using ANSYS 2019 R1 and I am also experiencing this "Error [node 0] [time 4/22/20 0:18:37] Abnormal Exit!" error. I doubt it has something to do with the ANSYS version. Did anyone ever find a solution? |
Hello
So, I had the same problem and was stuck for a while. But managed finally. If anyone does get this error, then you can give it a try with this method. 1) Start a new Fluent file with serial processing. 2) Import your mesh file and run your simulation for about few iterations 3) Export the case file 4) Start a new Fluent file with parallel processing 5) Import the case file and initialise 6) Now you should be able to run the simulation without Fluent shutting down Although this is not an eloquent solution, but helped get around the problem. Regards |
| All times are GMT -4. The time now is 23:40. |