Jump to content
darkdespair55

[Resolved] Unable to launch dedicated server after update on Aug 23rd

Recommended Posts

Hello to anyone that manages to help out, 

After the update yesterday to the dedicated server client I am no longer able to launch and run the server.  I had steamCMD revalidate the hosting files, removed all mods, reset to vanilla settings and right at the end of the server launch it closes itself. Even tried updating my GUI (I use Serverify) to see if it was something there and it still happens. Server was running fine until I asked steamcmd to update its files yesterday to match client versions.  Any help would be appreciated. 

 

It is not currently set to auto load a mission, a map or anything. Just open and go to the mission selection/vote screen. Here is the snippet from the end of the .rpt file. Full file can be found here on pastebin   https://pastebin.com/1zPf2AZd

Version 2.10.149799
Fault time: 2022/08/24 08:37:00
Fault address:  EB7BF01C 01:011BE01Cll C:\SteamCMD\steamapps\common\Arma 3 Server\arma3server_x64.exe
file:     
world:    Stratis
Prev. code bytes: F7 F1 48 89 1C 24 48 63 C2 48 8D 0C 40 49 8B 00
Fault code bytes: 4C 8B 0C C8 48 63 44 C8 08 48 8D 0C 80 4D 8D 1C
=======================================================
note: Minidump has been generated into the file C:\Users\owner\Documents\ServerifyA3_1.5.1.0\Profiles\021d3ddb-1e9b-4c70-a154-8508deddb056\arma3server_x64_2022-08-24_08-36-51.mdmp

 

 

 

For those that ask, server is running on windows 10 pro 21h2,  with an i7-10600k and 64gb of ram available, reboot did not resolve, runs heedlessly with access via remote desktop to startup/shutdown. 

 




**EDIT** The issue appears to be with serverifya3. Changed over to FASTER and the issue does not occur.  Still reproducible in serverify. 
 

Edited by darkdespair55
Found a work around
  • Sad 1

Share this post


Link to post
Share on other sites

I can confirm that this is the same crash I'm experiencing since the August 23rd update. It's been driving me mad, but it does indeed seem to be ServerifyA3 that is the culprit as switching over to FASTER cleared the fault. In hindsight I wish I had tried it before spending a few hours rolling up a Linux VM to temporarily host from groups missions from. I can't imagine what is causing the issue, but if I had to take a guess I'd say it has to do with how the config files are handled. I'll likely drop this post as a Issue on ServerifyA3's GitHub.
 

Full Log - Minidumps

Mods: @cba_a3;@enhanced_movement;@enhanced_movement_rework;vn;A3;curator;kart;heli;mark;expansion;jets;argo;orange;tacops;tank;enoch;aow
ServerMods: vn;@enhanced_movement_rework;@enhanced_movement;@cba_a3
Version 2.10.149799
Fault time: 2022/08/29 03:47:03
Fault address:  00EFE5D3 01:00E9D5D3ll D:\Arma 3\arma3server.exe
file:     
world:    Stratis
Prev. code bytes: 84 C9 75 EB 8B C2 33 D2 F7 77 04 8B 07 8D 0C 52
Fault code bytes: 8B 34 88 8B 44 88 04 8D 04 80 8D 3C 86 3B F7 74
 
Registers:
EAX:00000000 EBX:025FD6C8
ECX:16466C61 EDX:076CCECB
ESI:025FD6CD EDI:025FECB0
CS:EIP:0023:00EFE5D3
SS:ESP:002B:025FD604  EBP:FFFFFFFF
DS:002B  ES:002B  FS:0053  GS:002B
Flags:00010212
=======================================================

 

  • Sad 1

Share this post


Link to post
Share on other sites

I have the same error.
I tried to report this error on the github but I was unable to find the "report" issue".   ?

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×