Learning Forum

[Brayden York]

Hi all,

I made a post a few days ago about an error that's been plaguing me, but fear it may have been in the wrong category. Perhaps someone here is able to help.

I've been running a parametric fluent study, and while many of the design points solve okay I have been hit with the error:

Error: Communication with WB failed due to wrong XML format

Error Object: #f

Writing "| gzip -2cf > SolutionMonitor.gz"...

Writing temporary file C:\Users\MACDON~1\AppData\Local\Temp\flntgz-43562 ...

Done.

in the fluent transcript many times. This error comes after a solve is complete, but it will not move on to the next design point automatically which makes overnight/weekend runs near impossible (unless I get lucky). I am using ANSYS Academic Research CFD 2020R1 on a windows 10 64-bit machine, dual Xeon 8 core (16 core total), 64 GB ECC memory, quadro P2000 5GB VRAM, and 7200 RPM HDD.

A previous post with the same error was solved by setting the retained design point setting to "update full project" however that has not worked for me. Many times, simply running the same design point again will work but it is hit and miss. I have made workbench workbench projects and have gotten the same error. Any insight into why this may happen would be greatly appreciated as its been slowing my work down tremendously.

Regards,

Brayden

 

 

[KR]

Hello,

My apologies for this delayed response. 

Do you have any solution monitors set in Fluent? If yes, could you please try and remove these solution monitors, re-run the simulation, and verify if you obtain this error message?

Thank you.

Best,

Karthik

[Brayden York]

Yes I will try that, it may be some time before I find if it solved it since the error only occurs occasionally.

Thanks,

Brayden

[Brayden York]

Hi Karthik,

By solution monitors, do you mean general output parameters/definitions, or plots like what would be seen in the solution monitoring tab in workbench?

Regards.

Brayden

[Brayden York]

After turning off my pressure drop plot I have yet to run into this issue. I am still monitoring the residuals however. Thank you for your input Karthik.

Regards,

Brayden

[Julio Gutierrez]

I had the same problem and the solution given, although not ellegant, worked.

 

However, in my case, I just had to delete the Monitor plots, that I did especifically defined, not the ones automitically created with reports.