Quote:
Originally Posted by thedeath
how is this done?
i seem to think those errors are resource related.
Printable View
Quote:
Originally Posted by thedeath
how is this done?
i seem to think those errors are resource related.
How to do this ?:robot:Quote:
Originally Posted by thedeath
My dbserver seem freezes sometimes ,But it has run all the same.
dbserver Log:
--SQL KeepAlive
-- -->Error Keeping Query Alive!
-- -->Error Keeping QueryCommand Alive!
and it has show a MessageBox(list index out of bounds 1) sometimes.
The version number of my dbserver is 2007-1-10
go to ms sql, selectthe properties of your lom2 database, select options, set recovery model to simple instead of full
also if your dbserver gives errors that's why your m2server gives rundb :p
the default setting of recovery model is simple!
the error is showing all along.
dbserver :Server Started...
-- SQL KeepAlive
-- SQL Keep Alive not needed.
dose it right?
@2443533 sometimes, when the m2 is erroring constantly, u will get a list out of bounds box pop upfrom the dbserver, this then seems to make the dbserver say
"/error (and then a number)"
and after a while the dbserver will say sql keep alive not needed, think its to save on resourses... perhaps... maybe
@shunt
Yeah!
Just as you say.
the sql keepalive isnt really an error i should delete it :p
same with the not needed, it's just telling you wether or not it executed a query to keep your connections with ms sql open or not
dont delete em keep em in ..Quote:
Originally Posted by thedeath
had 1 list index out of bounds error after 4:25:26[M] so the m2 saidand theni got these problems below..
Ok this is what im getting after over 4 hours ..I was reloading lists at the time of the error .
I had 3 people on for hours and never had an error until i started to reload lists after editing an npc and guildlist, the first set of dbsave errors caused the error 4 in dbserver and the next block of 6 didnt do anything to the dbserver.
As soon as i stopped what i was doing the RUNDB errors stopped.
but the DBserver -- SQL Keep Alive not needed happened at the same time as the RUNDB saveDB timed out.. error in m2..
My sql db is set to simple and allways was but i have stopped all mongen except hens in 11 places .
any ideas on a cause or a resolution please..
i would recommend never ever to reload lists
reboot server dont reload
reloading = verry bad
it lags like hell cause it has to read and process all the stuff + it fucks up bigtime with the excisting items/magics/mobs ingame
Quote:
Originally Posted by thedeath
was only doing the lists while i was editing the npcs and merchants but thought id do the whole list option .
so you think my error was caused by me reloading them ?
i cant be sure ofcourse but most lkely the reloading caused your comp to slow down which probably created them errors (i dont like reloading @ runtime anyway so :p )Quote:
Originally Posted by elvin
i found that the error on my comp was actually when i had my mongen list spawning mobs all over mir, it was eating my cpu, i have cut them down to just the archers and have got no errors since. also found that, if u use the client to play ingame, on same machine ur running the server on the error will appear too.....
VirUs
very true,,, i only have hens spawning, and alls well until i try to run client on same pc as server is running
snap same hereQuote:
Originally Posted by shunt
when u use client it user up too many resources, so try using client on a diff machine