Hello there -
GameLift expects whichever process has been integrated with the GameLift Server SDK to be the same process that calls InitSDK() and ProcessReady(). In other words, whichever process you specify in your Fleet's Runtime Configuration (eg. C:\game\server.exe), that executable needs to be the one that is integrated with the GameLift Server SDK and communicates back to GameLift via the InitSDK() method, otherwise registration of your game server process will timeout and the error message you describe above will be shown.
Does this help?
Is there a way to modify the existing server executable files in a running fleet?Accepted Answerasked 2 years ago
Server process run through command do not persist in my Amazon Lightsail Instanceasked 5 months ago
How can I increase the number of devices that you can include in a test run in DeviceFarm?Accepted Answerasked 3 months ago
Time frame for fleet instance to be freed after terminationasked a year ago
Can I extract the code from the aws to save it in Github?asked a month ago
I am not able to stop or terminate the serverasked 2 months ago
Elastic Beanstalk doesn't run commands in the backgroundasked 3 years ago
Is it possible to schedule the number of instances in a fleet?asked a year ago
Server process started correctly but did not call InitSDK() or ProcessReady() within 5 minutes.asked 2 months ago
Can not you call SDKInit () in a background process?asked 5 years ago