SpaceEngineersDedicated: System.IO.IOException

I am unable to run a dedicated server instance upon a Windows Server 2019 machine, due to the following error:

"Server was stopped.System.IO.IOException: the process cannot access the file 'C:\Users\Administrator\AppData\Roaming\SpaceEngineersDedicated\SpaceEngineersDSGUI_20240810_12212641.log' because it is being used by another process.

at System.IO__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)

at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)

at Sandbox.MyErrorReporter.TrySendReport(String longName, String gameId, String email, String feedback, CrashInfo info, String reportType, IEnumerable`1 files)"

Yes, this is a duplicate of about 7 other issues, but since all of them have been closed without resolution, and since I believe I have identified the actual nature of this issue, I am posting this.

This error message is actually NOT the cause of the server crash. It appears to occur AFTER the crash, when the game attempts to report the crash to Keen. The game process attempts to access all relevant log files to include them in the crash report, but the DSGUI log in particular is still locked by the Manager GUI process, which hasn't crashed. Un-checking "Send log files to Keen" in the Manager GUI, before starting the server process eliminates this error from the log, without resolving the server crash itself.

I, like most people encountering this issue, assumed that the file access exception was the root cause of the crash, because the Console log in the Manager GUI does not display any other errors. Once I realized that this is not the root issue, I was able to go to the text log files and identify error messages there that were not being shown in the GUI, which revealed the real issue.