Page 1 of 1

Game Server crashing on /check

Posted: Thu Apr 02, 2015 3:06 pm
by Elkazan
Hello, fellow FFXI lovers,

Recently updated my server and everything is working splendidly except that every time anyone tries to /check another player or themselves, the Game Server crashes.

I've updated my client by force. It fixes what it finds, but the problem persists. Tried deleting 0.dat and force re-check. Client updates, but the problem persists.

I assume the problem is in the char_check c++ header, since everyone has the same problem, but I've no idea what to do with it, as I'm still fairly new to this.

Any help would be appreciated.

Re: Game Server crashing on /check

Posted: Thu Apr 02, 2015 3:59 pm
by demolish
update your server, think that crash has been fixed already

Re: Game Server crashing on /check

Posted: Thu Apr 02, 2015 4:04 pm
by Elkazan
demolish wrote:update your server, think that crash has been fixed already

Thanks for the quick reply.

I did just update the server. That's when the problem started. I can only assume then that I did something wrong in that process, so is there a step-by-step somewhere that I can follow to the letter?

Thanks again.

Re: Game Server crashing on /check

Posted: Thu Apr 02, 2015 6:23 pm
by kjLotus
update it again ;)

Re: Game Server crashing on /check

Posted: Thu Apr 02, 2015 7:17 pm
by Elkazan
kjLotus wrote:update it again ;)

Can you give me some help?

The way I've been doing it is this;

1.) Copy the important .sql files to a separate folder.
2.) Delete the server folder.
3.) Git-clone a fresh pull.
4.) Copy backed-up .sql files to sql folder and run DSP_Import.bat
5.) Re-build all servers in Visual Studio.

Should I be doing it another way?

Re: Game Server crashing on /check

Posted: Thu Apr 02, 2015 9:11 pm
by whasf
The SQL files mean nothing, it's what is in your SQL server that you care about.

Re: Game Server crashing on /check

Posted: Thu Apr 02, 2015 10:48 pm
by Desufire
Yeah I reported this in the bug thread. I "updated" like you've said you do. Last night I finally figured out how to set up a git fork and update that way. This bug was fixed then :).