starttimer exception (weird one)

[DanPL]

<b><font size="4">[ODBC] - every successfully tested</font></b>

<br><br>I've checked all posts related with that problem... and i have no idea wtf is going on... any suggestions ?<br><br>thanks in advance <br>

 

[Coly]

You have a problem with your Monster DB, check the Mon txt files, spawns etc.

 

[DanPL]

logs from CruelDragonMir3G.exe:

Holley legendary 3G plug-in log file ......
17:04:11: INI configuration file loaded successfully!
17:04:11: Application parameter abnormal, check the parameters
17:04:12: plug-in parameters to the INI file saved successfully!
17:04:12: Monster talking file loaded successfully!
17:04:12: automatic timing script file loaded successfully!
17:04:13: is beginning to load the SQL database ............. record number of items = 1480
17:04:14: Automatic full-service announcement file loading goods success!
17:04:14: Item Database loaded successfully!
17:04:14: the monster is beginning to load the SQL database records = 402 .............
17:10:32: the monster is beginning to load the SQL database records = 402 .............
17:10:32:17:10:32: I / O error 123
17:10:32: the monster is beginning to load the SQL database records = 402 .............

when i try to reload monsters after starttimer exception i get this message:

I / O error 123
17:10:32: the monster is beginning to load the SQL database records = 402 .............

i'll appreciate any help cause i need to figure it out

ps. those files i got from kaori site, untouched 3.55, just configured

 

[mapadale]

You need to be checking your MonDB as it's referencing to that and Coly told you that as well.

You have a mistake somewhere that's causing it, investigate it as we can't help as we don't know whats in your files or what you have done.

 

[DanPL]

is this problem can be caused because i use win 2003 serv enterprise edition ? what things exactly would u check as first ? im newbie and i dont really know how works those files.. i dont stop until i get it done ^^

 

[mapadale]

You would check the Monster DB for starters, then you would need to check the Mon.gen's as you could have a missed read Mon file. Basically check anything that is to do with the Mon files and no 2003 wouldn't cause it.

 

[Josiko]

delete your db monster and add 1 for 1

 

[DanPL]

thx but the problem is already fixed... solution: read carefully