Aloha 5.3 crashes when check is closed

[posknowitall]

Whenever a bartender attempted to close a check Iber closes with a windows error bringing the term to desktop. I found about 30 .olk files in the BOH data folder and deleted them hoping this was the cause. Only 1 of 2 terms had this problem so in the interim I had them close checks on the other terminal.
This was the error right when the crash occured:

Dec 14, 21:42:02 Employee Num 3026 FAILED to lock tabledef_id 0 (t->number is 0) since it is currently locked on terminal 0
Dec 14, 21:42:02 //=====================================================
Dec 14, 21:42:02 Exception code: C0000005 ACCESS_VIOLATION
Dec 14, 21:42:02 Fault address: 006F35A4 04:0000B5A4 C:\Aloha\BIN\IBER.EXE
For whatever reason the 2nd term is not master/server capable so it would also go down when this term went down. I attempted to copy and use a mirror log renamed to trans.log but this didn't work.
So I guess my real question is does this sound like a network comm problem? Power problem? I don't believe a fixlog would have worked because only one jobcode was causing this issue--the bartender who runs tabs. Servers who use tables were fine...
Thanks in advance for any replies.

 

[coorsman]

delete the *.lck file on the terminals \aloha\data. Should fix itself at eod.



cheers,
Coorsman


Hardware: the parts of a computer that can be kicked. ~Jeff Pesis

 

[posknowitall]

Well, they weren't .lck files they were .olk and they were not residing in the terminal. Never a problem once eod runs...until the next time.

 

[alohaakamai3]

My only experience with this was also olk or lck files on the terminal, took a long time to track this one down back in the day. Too date, it was the only time I ever saw this problem with aloha. But when it got to a check number that was the same as the file that was stuck in the DATA directory on one of the terminals, I believe it would get the ILLEGAL OPERATION message.