Learning Forum

[prabhakar]

[prabhakar]

This is the problem. Kindly help me to solve this

[Naresh Patre]

PrabhaCADME I am checking with the development team and will get back to you. Can you let me know if this issue occurs on any specific fluid flow model or across any model?

Meanwhile, can you try running the model on a single processor and see if it helps? To set single processor, go to Flow - Solver Options - Solver Settings.

[prabhakar]

Naresh Patre  not in specific models, for all models, 

Already solved and new fluid models have not been opened. 

I try Single processor and let you know..

Thank you

[prabhakar]

Naresh Patre  Its not working kindly update me with solution

[Naresh Patre]

PrabhaCADME Thanks for confirming.

This sort of issue is always difficult to debug as there are all sorts of things that could cause it such as something in the environment, corrupt installation, interaction with anti-virus software, and so on.

Could we get a listing of v191AFDafdwinx64runTimeLibrariesfluent from the installation folder to make sure necessary DLLs are there?

Also, can you share the list of all environment variables on your machine?

[prabhakar]

Is it  sufficient For you? Naresh Patre

 

 

[Naresh Patre]

PrabhaCADME The development team needs a text file containing all the information as images are not very clear. In a Command Prompt, do

set >env.txt

This will write the environment values to the file env.txt in the current directory shown in the Command Prompt.

Similarly, a text file containing the directory listings would be useful:

dir "C:Program FilesANSYS Incv191AFDafd" /S >dir.txt

This will write a recursive directory listing to the file dir.txt in the current directory.

[prabhakar]

Naresh Patre 

🛈This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions

[Naresh Patre]

PrabhaCADME The files that you shared did not show anything problematic. So the development team has suggested to try out below mentioned steps to debug the issue.

First of all, in a command prompt, just check that AFD can be launched successfully:

“C:Program FilesANSYS Incv191AFDbinafd.bat” 3ddp -m ue

(If you have installed Discovery in other directory, please specify appropriate path)

You should see something like below. The list of releases may be different in your case depending on the license you have.

Next, at the “>>>” prompt, type:

RootObject()

We expect to see 

‘/FLUX’

on the next line.

Then type:

quit() 

at the >>> prompt to exit.

I would expect everything to work so far as the reported failure seems to happen at a later point.  If you are seeing anything different, please share the snapshot of the output

 

Assuming the above worked OK, I have attached a script and data files that exercise standalone AFD more fully. I would either expect this to show the same issue as reported or, if it does not, it might give some clues about where else to look.

To try this out, unpack the zip file into a convenient directory.

You should see two files, run.py and runafd_bat.txt, and a single directory UpdateMesh_001.

Rename runafd_bat.txt to runafd.bat 

(If you have installed Discovery in other directory , open runafd.bat in Notepad or any text editor and specify appropriate path)

Open a Command Prompt and navigate to the directory where the zip file was unpacked (i.e. the directory containing the runafd.bat file).

Type runafd.bat at the prompt and wait for it to finish executing.

A file named output.txt should have been generated. Please send this to us along with any errors that are seen in the Command Prompt window.

🛈This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions

[prabhakar]

[Naresh Patre]

PrabhaCADME 

Thanks for sharing the output. I will get back to you with team's observation.

[Naresh Patre]

Hello  PrabhaCADME

The image shows that you did not run afd.bat with the '3ddp -m ue' options that were mentioned in my reply. Can you execute the command again with these options and follow the steps as mentioned earlier?

[prabhakar]

Naresh Patre 

[prabhakar]

Naresh Patre 

[prabhakar]

Naresh Patre first cmd runs well

the second you mentioned showing error.

 

[Naresh Patre]

PrabhaCADME

Good to know that the output from first section was as expected.

In the 2nd image you shared, you have specified options like 3ddp -m ue -R run.py 1>output.txt. There is no need to specify any of these options. Also, it looks like you are executing afd.bat from the Discovery installation directory. As mentioned in my earlier post, in this section you first need to download and unzip the attachment at a convenient location, then rename the file and follow next steps. I request you to go through the steps again send the snaps and output file.

[prabhakar]

Naresh Patre 

 

🛈This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions

[Naresh Patre]

PrabhaCADME The development team looked at the outputs you shared and below is their reply:

 

This confirms that there is an issue in the AFD package that is independent of the broader AIM environment but unfortunately it doesn't give us any more information about what the issue might be.

This is really difficult to debug remotely. All I can think is to ask the customer if they could run a Microsoft tool called ProcessMonitor while running the runafd.bat file again.  This records a lot of information about DLLs being loaded and it might be possible to pinpoint what is going wrong.

Instructions

1. Download ProcessMonitor from here.
2. Unzip the downloaded file to any convenient directory.
3. In Windows File Explorer view the directory from (2) . A file named 'Procmon.exe' should be visible. Leave the File Explorer window open.
4. Open up a Command Prompt window and change to the directory containing the previously sent runafd.bat script. 
5. Start 'Procmon.exe' by double clicking on it in the File Explorer from (3). A Window will pop up to allow customisation of filters. Do not change anything here. Just press OK. The Process Monitor window should then be visible. It will immediately start recording events.
6. Run the runafd.bat batch file in the Command Prompt (4).
7. When the bat file finishes go to the File menu in the Process Monitor window and unselect Capture Events to turn off event recording.
8. Also in the File menu in the Process Monitor window go to the Save... menu. Leave all defaults alone. Note the Path where the file is being saved to and press OK.
9. Send me the saved file (probably called Logfile.PML).  It is likely to be quite big (70 MB in the case I just tried) so it is probably worth zipping it before sending.

 

Can you please try out the above mentioned instructions and send the generated output file?

[prabhakar]

Naresh Patre  zip file showing unsupported file type during upload.. sent your other contacting details 

[Naresh Patre]

PrabhaCADME Please send the file to ansys-discovery-support@ansys.com

[prabhakar]

Naresh Patre  I have sent the file

[Naresh Patre]

Hello  PrabhaCADME

Thank you for sending the file. I have passed it on to development and will let you know their response.

[prabhaxdesigner]

Naresh Patre Thanks in advance

[Naresh Patre]

PrabhaxD  Below is the reply from development:

 The output is showing the following:

Note that the error occurs while ComputeNode.py is executing. This means that this file (ComputeNode.py at the path shown) must have been loaded. In that case I would expect to see the file mentioned in the ProcessMonitor log. i.e., I would expect to see something like the following, which is what I see when I run this locally:

However, in the provided log file, there is no mention of ComputeNode.py. Because of this, I suspect that the same error was not being seen when the customer recorded the log.

Can you please confirm whether you are continuing to see the same message about “DLL load failed” as shown above when you try solving physics in AIM?

[prabhakar]

Naresh Patre  still having the same "DLL load failed" error.

[Naresh Patre]

PrabhaCADME 

Sorry for the confusion but can you retry the steps from 3 to 9 mentioned in previous reply and confirm whether you get same  "DLL load failed" error in command prompt? Can you send the snapshot of command prompt and the new log file generated, to  ansys-discovery-support@ansys.com?

Secondly, the developer mentioned that he was involved in a similar query earlier and it was noticed that virus scanner was preventing the load of a dependent DLL. So can you try disabling virus scan and see if you still see the same error while running "runafd.bat" file?

[prabhakar]

Naresh Patre I have sent you both files.. Sent zip fie vi gmail.. becasue file size.

Also tried by disabling Anti-virus.. same error

[Naresh Patre]

PrabhaCADME Thank you for sharing the file. I will let you know the response from development.

Meanwhile, did you try disabling virus scan and see if you still see the same error while running "runafd.bat" file?

[prabhakar]

Naresh Patre Yes.. error happens to be the same

[prabhaxdesigner]

Naresh Patre It works, when i switched OS from Win 7 to Win 10.

[Naresh Patre]

PrabhaxD Glad to know that switching the OS resolved the issue. I will also update the development team about this resolution.