Ok, new server with a game banged 4/2. I have a trader who is being kicked out while eprobe exploring. I am running v1.01.59, but the game was banged with .58 I understand that the ANNOUNCE.DAT error is a know bug. But what is "Index already locked" mean ?

Does anyone know what this error is ?

<<Details and logs>>

Turbo Posted - 04/03/2004 : 1:09:04 PM
-- The server seems a little slow, and it keeps kicking me out of the game for no reason (once during Tri-cron, several times while eprobe exploring).

TWerror log initialized 04/02/2004 06:49:23 AM
04/02/2004 06:32:20 PM Turbo (2) Halted:
Unknown file error (998) on file ANNOUNCE.DAT.
04/02/2004 10:40:45 PM Noallin (3) Halted:
Timed out due to inactivity.
04/03/2004 08:57:20 AM Noallin (3) Halted:
Index already locked - 302 (1000056)
04/03/2004 08:59:47 AM Noallin (3) Halted:
Index already locked - 302 (1000056)
04/03/2004 09:00:52 AM Turbo (2) Halted:
Index already locked - 302 (1000054)
04/03/2004 09:01:57 AM Noallin (3) Halted:
Index already locked - 302 (1000056)
04/03/2004 09:05:26 AM Turbo (2) Halted:
Index already locked - 302 (1000054)

<GAME LOGS>
08:56:30 AM 04/03/2004 24.x.x.x Turbo(2): Ran Tradewars 2002.
08:57:20 AM 04/03/2004 Noallin(3): Abnormal exit - Index already locked - 302 (1000056)
08:59:28 AM 04/03/2004 4.x.x.x Noallin(3): Ran Tradewars 2002.
08:59:47 AM 04/03/2004 Noallin(3): Abnormal exit - Index already locked - 302 (1000056)
09:00:12 AM 04/03/2004 4.x.x.x Noallin(3): Ran Tradewars 2002.
- Noallin made a planet: Mt Home


09:00:52 AM 04/03/2004 Turbo(2): Abnormal exit - Index already locked - 302 (1000054)
- Noallin made a planet: .
- Noallin made a planet: Mt Home
09:01:13 AM 04/03/2004 24.x.x.x Turbo(2): Ran Tradewars 2002.
- Noallin made a planet: .
09:01:57 AM 04/03/2004 Noallin(3): Abnormal exit - Index already locked - 302 (1000056)
09:04:31 AM 04/03/2004 4.x.x.x Noallin(3): Ran Tradewars 2002.
09:05:26 AM 04/03/2004 Turbo(2): Abnormal exit - Index already locked - 302 (1000054)
09:14:21 AM 04/03/2004 Noallin(3): Normal exit

Heh, I'm "intimately" familiar with that error message!

My Sysop and I were testing the brand new Server I just downloaded this morning, and guess what kept happening?

Both of us getting booted back to the menu continually. This problem only occurred when more than one node in use. All day I've used this server without being booted.

I know how you guys love the "goods" so here it is.

04/04/2004 04:07:04 AM Supreme Galactic Overlord (1) Halted:
Index already locked - 302 (1000052)
04/04/2004 04:12:08 AM Trumpf (2) Halted:
Index already locked - 302 (1000054)
04/04/2004 04:17:21 AM Trumpf (2) Halted:
Index already locked - 302 (1000054)
04/04/2004 04:22:29 AM Supreme Galactic Overlord (1) Halted:
Index already locked - 302 (1000052)
04/04/2004 04:27:30 AM Supreme Galactic Overlord (1) Halted:
Index already locked - 302 (1000052)
04/04/2004 04:32:31 AM Supreme Galactic Overlord (1) Halted:
Index already locked - 302 (1000052)
04/04/2004 04:37:46 AM Supreme Galactic Overlord (1) Halted:
Index already locked - 302 (1000052)
04/04/2004 04:39:52 AM Supreme Galactic Overlord (1) Halted:
Index already locked - 305 (1000052)
04/04/2004 04:42:58 AM Supreme Galactic Overlord (1) Halted:
Index already locked - 302 (1000052)
04/04/2004 04:48:03 AM Trumpf (2) Halted:
Index already locked - 302 (1000054)
04/04/2004 04:53:15 AM Trumpf (2) Halted:
Index already locked - 302 (1000054)
04/04/2004 04:58:26 AM Supreme Galactic Overlord (1) Halted:
Index already locked - 302 (1000052)
04/04/2004 05:03:29 AM Trumpf (2) Halted:
Index already locked - 302 (1000054)

I'm just verifying that this is with the public download here on EIS. The reason I ask is these problems were occuring with a private beta of .59, but testing made it look like it was fixed.

It appears that the wrong build of .59 was put up for download. The correct one is now available for download as .60 at http://www.eisonline.com/twgs/beta/ Sorry for the problems, let us know if they continue after upgrading to .60

Thank you Harley. I'm upgrading to .60
I'll keep checking to be sure that the upgrade fixes the problem.

Please don't hesitate to let us know if you have any problems.