ASA does not start since the patch on Winserver 2016

[AveryFoox]

Since update 38.9 on the server it no longer starts and crashes because it cannot find the SetThreadDescription entry point.

The server runs on Windows Server 2016. It has always worked until now...

 

Can you help me ?

[LonelyFire]

I also have the same issue https://ibb.co/X8J3RRh

[VovkaOs]

I have the same SetThreadDescription . Help.

Edited April 2 by VovkaOs

[VovkaOs]

I checked on. The server does not start on Windows Server 2016

Windows Server 2019 and Windows 10 launches and works fine.

[Whighty]

Same issue here on Windows Server 2016.

[invincibleqc]

5 hours ago, VovkaOs said:

I checked on. The server does not start on Windows Server 2016

According to SetThreadDescription:

Quote

Windows Server 2016, Windows 10 LTSB 2016 and Windows 10 version 1607: SetThreadDescription is only available by Run Time Dynamic Linking in KernelBase.dll.

And ArkAscendedServer.exe does not load kernelbase.dll:

Spoiler

File Type: EXECUTABLE IMAGE

  Image has the following dependencies:

    tbb.dll
    dxgi.dll
    d3d9.dll
    d3d11.dll
    SHLWAPI.dll
    DSOUND.dll
    WS2_32.dll
    WINMM.dll
    KERNEL32.dll
    USER32.dll
    GDI32.dll
    ADVAPI32.dll
    SHELL32.dll
    ole32.dll
    OLEAUT32.dll
    IPHLPAPI.DLL
    SETUPAPI.dll
    dwmapi.dll
    CRYPT32.dll
    bcrypt.dll
    WINHTTP.dll
    OPENGL32.dll
    CFGMGR32.dll
    MSVCP140.dll
    UxTheme.dll
    VCRUNTIME140.dll
    VCRUNTIME140_1.dll
    api-ms-win-crt-runtime-l1-1-0.dll
    api-ms-win-crt-utility-l1-1-0.dll
    api-ms-win-crt-string-l1-1-0.dll
    api-ms-win-crt-stdio-l1-1-0.dll
    api-ms-win-crt-convert-l1-1-0.dll
    api-ms-win-crt-math-l1-1-0.dll
    api-ms-win-crt-heap-l1-1-0.dll
    api-ms-win-crt-filesystem-l1-1-0.dll
    api-ms-win-crt-environment-l1-1-0.dll
    api-ms-win-crt-time-l1-1-0.dll
    api-ms-win-crt-locale-l1-1-0.dll
    api-ms-win-crt-conio-l1-1-0.dll
    api-ms-win-crt-multibyte-l1-1-0.dll

  Image has the following delay load dependencies:

    aws-cpp-sdk-core.dll
    aws-cpp-sdk-s3.dll
    steam_api64.dll
    EOSSDK-Win64-Shipping.dll
    LibOVRPlatform64_1.dll
    d3d12.dll
    sentry.dll
    OpenImageDenoise.dll
    libvorbisfile_64.dll
    GFSDK_Aftermath_Lib.x64.dll
    dbghelp.dll

  Summary

      663000 .data
        1000 .msvcjmc
      510000 .pdata
     26BE000 .rdata
      289000 .reloc
        3000 .rsrc
     5FA8000 .text
       5E000 _RDATA

 

5 hours ago, VovkaOs said:

Windows Server 2019 and Windows 10 launches and works fine.

On these that symbol is resolved from:

    KERNEL32.dll
                         562 SetThreadDescription

 

So, unless WC link kernelbase.dll in a future update, it won't work anymore on Windows Server 2016 because its kernel32.dll does not export that function. In any case, I would personally suggest you guys upgrade your environments; that OS has reached EOL for non-security updates for over a year now.

[ThoWoMa]

I say it like I see it. EOL or not, WC tries to prevent dedicated servers. For my taste, an upgrade to 2019 in the “private” area is completely excessive and absolutely unnecessary. WC is simply completely overwhelmed with the use of UE5.

 

[VovkaOs]

invincibleqc, as a moderator, could you bring this problem to the attention of the developers? Everything was working before this patch was released.

Edited April 3 by VovkaOs

[ThoWoMa]

I'm pretty sure the devs know about the problem and added it intentionally under pressure from Nitrado. Or the devs are really incompetent. It's not because of the UE5. Satisfactory has always run stably on Server 2016. Both in the UE4 and UE5 versions. Coffee stain studios didn't sell a paid engine update but switched from one patch to the next from UE4 to UE5. ASA still has the same bugs as ASE since Day1. 1:1 copy with better graphics. It's nothing more. And then selling a Western DLC with Scorched Earth for 30 euros is a bit cheeky.

[Joebl0w13]

12 minutes ago, ThoWoMa said:

And then selling a Western DLC with Scorched Earth for 30 euros is a bit cheeky.

Not that it matters for the 2016 issues but the DLC is for new content for 3 maps. Not just SE. 

[invincibleqc]

29 minutes ago, ThoWoMa said:

I'm pretty sure the devs know about the problem and added it intentionally under pressure from Nitrado. Or the devs are really incompetent. It's not because of the UE5.

Actually, it appears to be caused by simply upgrading FSR 2 to FSR 3.

[slydog1225]

OMG I have been spending hours on this and could not figure out what happened after that update. Nothing about this was popping up on google either so thought I messed something up....