Devidian / docker-spaceengineers

A Docker for Space Engineers Dedicated Server
87 stars 21 forks source link

ShellExecuteEx failed: File not found. #37

Closed koolzr closed 3 months ago

koolzr commented 1 year ago

image keep getting is issue when trying to instal on my unraid server

Devidian commented 1 year ago

Hi, i never worked with unraid but i assume that there must be ports forwarded. Might be the steam port mentioned in #31.

ghost commented 1 year ago

I'm running a Debian 11.6 LXC in Proxmox and get the same error.

-------------------------------INSTALL & UPDATE------------------------------
WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work.
Redirecting stderr to '/root/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1679680174
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
"@sSteamCmdForcePlatformType" = "windows"
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Error! App '298740' state is 0x202 after update job.
---------------------------------UPDATE CONFIG-------------------------------
-----------------------------CURRENT CONFIGURATION---------------------------
GAME_DIR=/appdata/space-engineers/SpaceEngineersDedicated
CONFIG_PATH=/appdata/space-engineers/instances/seserver/SpaceEngineers-Dedicated.cfg
INSTANCE_IP=xxx.xxx.xxx.xxx
CURRENT_IP=xxx.xxx.xxx.xxx
CURRENT_WORLDNAME=Star System
SAVE_PATH=Z:\\appdata\\space-engineers\\instances\\seserver\\Saves\\Star System
wine-8.0
----------------------------------START GAME---------------------------------
rm: cannot remove '/appdata/space-engineers/instances/seserver/*.log': No such file or directory
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: File not found.

In the docker logs there is also this error:

Error! App '298740' state is 0x202 after update job.

Based on this page: Error Codes, it appears my container was just running out of disk space so my error is not exactly the same.

Anyway, I did two things:

The issue has been resolved for me