Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

Procedure Entry Point Cannot Be Located in DLL

Hi, I have been attempting to run the network_planning WinProp API example as part of Altair Feko v2025.1. At runtime, I have been getting a "The procedure entry point could not be located in the dynamic link library C:\ProgramFiles\Altair\2025.1\feko\bin\EngineNet.dll" error.

I have added "C:\ProgramFiles\Altair\2025.1\feko\bin" to my Path Environment Variable, and I know that the DLL is being correctly found at runtime. I have also successfully run the outdoor_propgaation API example, which uses the Engine.dll with no issue. I was wondering if anyone has had success running this or another example that uses the EngineNet.dll in v2025.1. I am unsure if this is an issue on my end or if there has been some reported header mismatch with the EngineNet.dll. Any suggestions would be greatly appreciated.

Thanks!

Find more posts tagged with

Feko

Troubleshooting

v2025.1

Accepted answers

All comments

Jaehoon

Could you check also the files under C:\Program Files\Altair\2025.1\feko\api\winprop\bin?

Best regads,

Jaehoon

image.png

RolandGadbois7

Hi Jaehoon,

I do not believe there is any issue with the files in C:\Program Files\Altair\2025.1\feko\api\winprop\bin. I have attached a similar screenshot as yours. EngineNet.dll definitely exists there, and I am fairly confident that the dynamic-linked library is being correctly found at runtime since when I run where EngineNet.dll in terminal, it correctly returns C:\Program Files\Altair\2025.1\feko\bin\EngineNet.dll.

Thanks again for all your help. Any more advice would be greatly appreciated.

DLLFeko.png

Jaehoon

Hello,

1)Please share here the output of:
C:\Program Files\Altair\2025.1\feko\bin\findinfostrings.exe C:\Program Files\Altair\2025.1\feko\bin\EngineNet.dll

by simply moving to C:\Program Files\Altair\2025.1\feko\bin\ and running as below.

2) Please upgrade to the 2025.1.1 version using the Feko update mechanism and then try again.

3) I think your Path environment variable is right.

4) Could you share which company or academic institute you belong to?

Best regards,

Jaehoon

image.png

RolandGadbois7

Hi Jaehoon,

Thank you for your advice. I upgrade to the 2025.1.1 version as you suggested, resulting in the same output for C:\Program Files\Altair\2025.1\feko\bin\findinfostrings.exe C:\Program Files\Altair\2025.1\feko\bin\EngineNet.dll as you posted.

I still run into the same procedure entry point error however. If you have any other advice, that would be highly appreciated.

As for my academic institution, I work at a University of California school.

Best,

Roland Gadbois

Jaehoon

Hello Roland,

Please remove the %FEKO_HOME%\bin folder from the PATH environment variable,

as the DLLs under %FEKO_HOME%\api\winprop\bin shall be used and then try again..

(Normally, "%FEKO_HOME%\api\winprop\bin" is equivalent to

"C:\Program Files\Altair\2025.1\api\winprop\bin")

Please also check the version of the EngineNET.DLL in %FEKO_HOME%\api\winprop\bin by using "findinfostrings" command…

Best regards,

Jaehoon

RolandGadbois7

Hi Jaehoon,

I have followed your suggestion and still encounter "The procedure entry point could not be located in the dynamic link library C:\Program Files\Altair\2025/1\feko\api\winprop\bin\EngineNet.dll"

As the error suggests, it is now using the DLL under %FEKO_HOME%\api\winprop\bin as a result of changing the PATH environment variable, which I have confirmed below.

The version of EngineNet.dll in %FEKO_HOME%\api\winprop\bin seems to be the same as before:

Should the versions be different? If they are identical, then it makes sense that the procedure entry point error is still occurring.

Thanks for all your help in this matter.

Best,

Roland Gadbois

RolandGadbois7

Hi Jaehoon,

I diagnosed the issue. Took me a little bit but doing some combing using Dependencies, I found that the built executable was using a C:\WINDOWS\system32\NetMan.dll module instead of the C:\Program Files\Altair\2025.1\feko\api\winprop\bin\NetMan.dll module. Since Windows loads the System32 DLLs prior to those in the PATH environment variable, I think this was causing an issue, so to rectify it, I just added the NetMan.dll to the directory of the executable.

Thanks again for all your attention and help to this matter. It was really appreciated.

Best,

Roland Gadbois