The procedure entryu point RtlGetPersistentStateLocation could not be located in the dynamic link library .........\IPHLPAPI.DLL

[grzech1983]

Hello,

do you have any idea what could cause this error:

The procedure entryu point RtlGetPersistentStateLocation could not be located in the dynamic link library .........\IPHLPAPI.DLL

when trying to start compiled FileZilla FTP service or even GUI?

Thanks

[grzech1983]

Ok. I thought that this was related to .dll files being installed to install dir because of not applying filezilla-server patch but even without additional .dll files I'm still getting this error.

[iam-sysop]

What version of Windows are you trying to install on?

I will try to reproduce the error on this end.

[grzech1983]

Actually when I try to run in locally on Windows 11 it works but when I try to run it on Windows Server 2016 Version 1607 OS Build 14393.6252 I'm getting those errors.

Hmm .. I've installed vcredist recently and today I've restarted this system and now I can run filezilla-server.exe but filezilla-server-gui.exe returns similar errors:

The procedure entryu point __CxxFrameHandler4 could not be located in the dynamic link library .........\OLEACC.DLL

The procedure entryu point __CxxFrameHandler4 could not be located in the dynamic link library .........\UxTheme.dll

The procedure entryu point __CxxFrameHandler4 could not be located in the dynamic link library .........\WINMM.dll

and

The program can't start because api-ms-win-shcore-taskpool-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.

[iam-sysop]

You might need to install "Desktop Experience" feature on Windows Server 2016 in order to get access to uxtheme.dll and winmm.dll -- those are desktop theme component dlls in Windows.

I will spin up a VM later of Server 2016 to test with. Everything I run on is 2019 or newer with Desktop Experience installed (Win 10 or newer for desktop) -- Server 2016 is the equivalent to Windows 8 - so I'll have to setup an environment to test on.

[grzech1983]

I have normal GUI on this Windows Server (this is not a Core installation). I'm planning to update my systems to 2022 in near future so it will not be a problem but still it would be good to know what is causing this issue.

[iam-sysop]

I'll have a complete test result shortly --

[iam-sysop]

So I spun up a Windows Server 2016 Standard Edition (Desktop Experience) version - not Core -- and 1.7.3 installed and ran without issues (even before any Windows Updates or patching.

I started thinking about your issue above and it seems something is very odd about that 2016 Server configuration you have because uxtheme.dll and winmm.dll are both part of Windows Desktop Experience (they're the multimedia and theming engine for the desktop) -- if your FZ install can't find them then there might be a permissions or path resolution issue.

I'm going to run again against a Datacenter Edition install and a couple other "configurations" as well.

[grzech1983]

So far my findings:

I have two versions in two folders. One is with additional .dll files inside installation folder and second one is without them. When I installed latest vs redist 2019 on first system I was able to run filezilla-server.exe using directory with additional .dll files. When I run filezilla-server.exe from second one without additional .dll files I'm still getting RtlGetPersistentStateLocation error.

When I tried to do the same on other 2016 system but without installed VC redist 2019 both versions (with and without DLLs) are returning RtlGetPersistentStateLocation error so for sure vc redist 2019 is needed.

Maybe I will try to run processmonitor and check what files are being used.

When I tried to run it on 2012 R2 I was getting errors for missing api-ms-win-core-heap-l2-1-0.dll. Does this solution need to have .net core installed?

I even tried to run it on Windows Server Standard 2022 (with GUI) and I've got error:

The procedure entry point GdiWaitForTextReady could not be located in the dynamic link library PATHTOFILEZILLA\UxTheme.dll

for filezilla-server-gui.exe BUT I was able to run filezilla-server.exe from both folders (with and without additional .dlls).