[EU - 2008] Server Full Error

[connzolo]

I managed to set the services and database up completely and make a login.
I used the gameguardless client just so i can screw around with some fiesta server files,
I go to log in and everything and I get to a screen that says Teva - High. I double click on Teva and it says that the server is full. I could really use some help sense im really new to Fiesta Servers.

[MentaL]

[fiestanerd69]

https://forum.ragezone.com/f594/faq-...sting-1059096/

If you have a look at that thread, this is one of the most common errors. All you have to do is wait for a while for it to change from high to low after you start the server. If even after waiting for a long time it doesn't not change, then check your error logs as you may have set something up incorrectly.

[connzolo]

The only weird thing I found was this, in the World Manager debugfiles.
This is repeated continuous.
015600 2015-10-19 15:42:42 <CONNECTING CHAR DB TO 127.0.0.1:9100>
015601 2015-10-19 15:42:42 <CONNECTING ACCOUNT DB TO 127.0.0.1:9000>

- - - Updated - - -

What I might be thinking is that its not connecting to the database. But I set it up following the tutorial. Im quite clueless

- - - Updated - - -

If this is any help
063560 2015-10-19 19:06:02 ERROR - HEARTBEAT OVERTIME, NOW DISSCONNECT WITH DB_ACCOUNT
063561 2015-10-19 19:06:02 <CONNECTING ACCOUNT DB TO 127.0.0.1:9000>
063562 2015-10-19 19:06:02 ERROR - HEARTBEAT OVERTIME, NOW DISSCONNECT WITH DB_ACCOUNT

[fiestanerd69]

Well there's your problem. You've incorrectly setup the database or configured the settings incorrectly for the database. Check your ODBC. If you're running 64 bit make sure you've modified the correct ODBC version. Make sure to check the settings file, sometimes there's two, so make sure you've modified them both or modified the correct one. If your computer does not have a password then you need to setup MSSQL again, this time with a password. Make sure the database names are correct and when you setup the ODBC test the connection, if that's successful then it's the settings file. Check the settings file and make sure that the database names are correct and that the username and password which you are using work, by trying to login into MSSQL using that information.