Server process started correctly but did not call InitSDK() within 5 minutes

[dusanfpwn97]

I managed to upload a linux build to the gamelift but on fleet creation in the ACTIVATING stage i get this error:

Server process started correctly but did not call InitSDK() within 5 minutes, launchPath(/local/game/Mul/Binaries/Linux/MulServer), arguments(null), instanceId(i-0758a58563c9fc6df)

I searched for the solution very hard but in the end I had to ask you guys here. Are you familliar with this error?
Most of the solutions that I have found online were inputting correct "launchPath", but as you can see from the error, it is a correct path.

Thanks in advance

[Jeff-Stapleton]

I had this same error. It was an issue with the path I provide the AWS Game Lift console when trying to deploy

[keyserjaya]

https://forums.awsgametech.com/t/unity-build-exe-did-not-call-initsdk/3248/9

try run .exe with the -batchmode -nographics

[Dhamu143]

is there any update on this issue? i am also getting the same error.

[devpateltech007]

I had this same error. It was an issue with the path I provide the AWS Game Lift console when trying to deploy
What patch did you provide @Jeff-Stapleton ? Please Help I am also facing the same InitSDK() timeout issue

[chris-gong]

These types of issues are kind of vague but it basically means that the server process is either crashing prematurely at startup or near startup time, or that the server is quite literally not calling the gamelift server sdk InitSDK function.

Back then I would use GameLiftLocal to test my server process before deploying to AWS but it seems they've retired that for a new testing approach.