SteamCMD not working properly with panel/daemon - Windows

[SugarD-x]

When installing or updating/validating a server with SteamCMD through the panel/daemon, it seems to always fail shortly after beginning the verification process, and exits with code 0. If SteamCMD is run from the operating system directly using the same files, it completes the actions successfully without error codes.

This is happening with the "default" mod for Counter-Strike: Source. I'm not sure if this happening with other games installed via SteamCMD, as I have not tested it.

I'm currently using Windows Server 2019 64-bit for the operating system. I don't know if other operating systems are also affected or not.

[SugarD-x]

The temporary workaround to get around this issue seems to be allowing SteamCMD to fail while running through the panel/daemon, and then manually run SteamCMD through Windows, and have it update/validate the server files. Then in the panel, go to the server settings, change the server to an installed status, and save the change.

[SugarD-x]

Running servers also appears to be exiting with code 0 and no error messages. I'm not sure if it is related or not.

[SugarD-x]

Apparently code 0 means it was successful, but the panel/daemon seems to think that is an actual error, and thus does not mark the game server as installed.

[SugarD-x]

Upon further investigation, it appears that the daemon is failing to start the game server executable at all on game server start. When gameap-starter.exe runs, it creates the text files in the game server's directory, and then just outputs the command sent to it, says "Type: start", and closes. The game server executable is never triggered. (It appears the code 0 may be the console output from Windows or the daemon, and not the game server).

This appears to be related to the server start issue, but I'm not sure if it has anything to do with the installation or validation processes or not.

For an example of the console output:

[et-nik]

game-starter.exe -t start ... command running another background game-starter.exe process with game server process. Background gameap-starter monitors game server process. If the game server stops, then the background gameap-starter.exe too

[et-nik]

I faced SteamCMD problem too. I did not find out the exact causes of the problem.
As a workaround I made runs steamcmd via gameap-starter.

[SugarD-x]

Did you modify SteamCMD to your own version to make that work?

[et-nik]

No. Used SteamCMD original build

[SugarD-x]

I tried playing around with the daemon starter to open a text file, and it had the same result as srcds, but when I used it to start a batch file, it ran successfully. Could it be a memory issue preventing scrds from running under the daemon?

[et-nik]

I guess this is an environment problem (environment vars, etc)

[et-nik]

It can also be OS restrictions (security process restrictions).

[SugarD-x]

I'm wondering if that is the case because it seems like srcds isn't even attempting to run when triggered through the application. I think I briefly had a similar issue with the prior panel software I had before I came here, but the developer was able to fix it and didn't say how. I can't find the information on it anymore, either. Several of the paid panels seem to support it, so there must be a solution out there. I'm just not sure where. I couldn't find any similar reports to this one.