Corrupt Transaction Log

[AlohaWahini]

Hey all,

We've got a store on 5.3.15. Someone did a refresh during a busy dinner, and the system came back with a corrupt trans. Running the fixlog 5200 found (and supposedly removed) some corruption, but did not entirely fix it. Still showing something about gift certs and listing some numbers, but would get stuck when trying to launched the Front of house with the "fixed" log. Had to remove the log entirely so they could get up and running to keep doing business.

It's been my experience that when this happens, the data is pretty much gone. You used to have the option of sending to Aloha to "fix" the log, but my recollection of this process was that it usually wasn't worth it to the customer.

Does anyone know of an additional utility that might get this data back or know of anything else that might work?
It would be nice to give them at least some idea of the business that day.

Thanks in advance.

 

[DTSMAN]

Aloha 5.3.12 and up work different. I copied this from the new knowledge base.

Repair a Log Using Grind in Aloha Versions 5.3.12 and Higher
Grind will automatically detect the log version and repair any transaction log from Aloha version 4.0x and higher. If the transaction log is from an older version than the grind, grind will upgrade the transaction log prior to repairing it. Unlike fixlog, which requires a different application file for each version of transaction log, the single grind application will work for all versions of transaction logs from 4.0x through the version of grind.



To repair a corrupt log for the current day's business, stop the FOH on all terminals, rename the Trans.log to BadTrans.log, open a command prompt and navigate to the Data folder on the file server. Use Grind.exe or GrindQ.exe to repair the transaction log on the file server using the following command line:



..\BIN\GRIND.EXE /FIXLOG BADTRANS.LOG



Grind does not alter the original transaction log (renamed BadTrans.log), but, instead, creates a new transaction log labeled Fixed.log. Once you repair the log, you must rename Fixed.log to Trans.log and restart the FOH terminals.



To repair a corrupt log for previous days business, open a command prompt and navigate to the dated folder on the file server, repair the transaction log in the dated folder using the following command line, and then manually regrind (refer to document AKBID1016) the dated folder:



..\BIN\GRIND.EXE /FIXLOG TRANS.LOG



Grind does not alter the original transaction log, but, instead, creates a new transaction log labeled Fixed.log. Create a backup copy of the original transaction log and rename Fixed.log to Trans.log.



Bo

Kentucky phone support-
"Mash the Kentrol key and hit scape."

 

[AdamDR]

5.3.12 and up def has that utility, but for some reason (call it experience!) I don't trust it. If you use fixlog, you HAVE to use the right version. There are 7 versions of this utility. You have to use the one that is made for your version. for 5.3.12 you have to use fixlog5.2.5.72.exe. I've learned this the hard way! If you use the wrong version it will say that it fixed it, but it won't. Hope that helps.

Adam