Need help fixing a Trans.log in Aloha 6.x

[LDigital]

I'm trying to fix a bad trans.log from yesterday on Aloha 6.1.14 and I've never seen a fixlog.exe at any of our units for any verison over 5.2.5.72. I know I should be able to run a gind.exe /Fixlog from the dated directory to fix it but nothing happens when I run it, any ideas

thanks
J

 

[jjr2144]

Try this
To repair a corrupt log for previous days business, open a command prompt, 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

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

or

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

 

[LDigital]

I did finaly get the Grind /fix to work but after rename the fixed.log file Im still having problems. let me give you a little history. Grind.exe crashes at 85% when running with the typical windows error "Aloha Grind TS has encountered a problem and needs to close.". I know there's data in the log I can run Reports on the translog but I can't regrind it. All other grinding today otherdays etc work fine. When the System went down last night is was really strange all the aloha terminals would start up and Iber would crash reading the translog and put them in to a windows desktop without rebooting the terminal or a error message. after backing up and trying to fix the log file I just did a manual EOD, and were up fine today.

thanks for the help.

 

[posknowitall]

Check your debouts. Sometimes this can point to what file is crashing. Perhaps a deleted item, employee, comp or something of that nature. Try copying the .dbf files from a previous dated sub as long as there was not some major programming done after that. Grind again and see if that helps.

 

[LDigital]

Thanks for the info, added the old dbf files and getting the same errors, here is a copy of the Debout we get



Jul 03, 09:04:38,, [STATUS],,""
Jul 03, 09:04:38,, [STATUS],,"................................................................"
Jul 03, 09:04:38,, [STATUS],,"GRIND v6.1.14.970 started for 20080630..."
Jul 03, 09:04:38,, [INFO],,"LoadIberStrings() - Loaded version 6.1.14.0, C:\Aloha\bin\IBERSTR.DLL"
Jul 03, 09:04:38,, [INFO],,"Database Versions and Generation are Current."
Jul 03, 09:04:38, [2604], [INFO],,"Total Disk Space (bytes) = 3227017216 Free (bytes) = 1729589248"
Jul 03, 09:04:38, [2604], [INFO],,"Database Versions and Generation are Current."
Jul 03, 09:04:38, [2604], [INFO],,"Reading data...(C:\Aloha\20080630)"
Jul 03, 09:04:39, [2604], [INFO],,"Read in 545 employees"
Jul 03, 09:04:40, [2604], [INFO],,"ConvertTransLog(): Analysing TRANS.LOG for conversion..."
Jul 03, 09:04:40, [2604], [INFO],,"GRIND: No log conversion required."
Jul 03, 09:04:40, [2604], [INFO],,"updating checkout payments for drawer 2 "
Jul 03, 09:04:40, [2604], [INFO],,"updating checkout payments for drawer 2 "
Jul 03, 09:04:40, [2604], [INFO],,"updating checkout payments for drawer 2 "
Jul 03, 09:04:40, [2604], [INFO],,"updating checkout payments for drawer 2 "
Jul 03, 09:04:41, [2604], [INFO],,"Table not found ! Check id : 5242949"
Jul 03, 09:04:41, [2604], [INFO],,"WARNING! Ordering items on a closed check! (c=3145780)"
Jul 03, 09:04:41, [2604], [INFO],,"//====================================================="
Jul 03, 09:04:41, [2604], [INFO],,"Exception code: C0000005 ACCESS_VIOLATION"
Jul 03, 09:04:41, [2604], [INFO],,"Fault address: 0073D795 04:00006795 c:\aloha\bin\grind.exe"
Jul 03, 09:04:41, [2604], [INFO],,"Registers:"
Jul 03, 09:04:41, [2604], [INFO],,"EAX:00000000 EBX:00000000 ECX:00000000 EDX:00000000 ESI:0014236B EDI:7C80B6A1"
Jul 03, 09:04:41, [2604], [INFO],,"CS:EIP:001B:0073D795"
Jul 03, 09:04:41, [2604], [INFO],,"SS:ESP:0023:0012D9B0 EBP:0012DA90"
Jul 03, 09:04:41, [2604], [INFO],,"DS:0023 ES:0023 FS:003B GS:0000"
Jul 03, 09:04:41, [2604], [INFO],,"Flags:00010246"
Jul 03, 09:04:41, [2604], [INFO],,"version 6.1.14.970"
Jul 03, 09:04:41, [2604], [INFO],,"Operating system is Windows XP (BuildNumber 2600, Platform 2, Version 5.1, Service Pack 2)"
Jul 03, 09:04:41, [2604], [INFO],,"Call stack:"
Jul 03, 09:04:41, [2604], [INFO],,"Address Frame Logical addr Module"
Jul 03, 09:04:41, [2604], [INFO],,"0073D795 0012DA90 0004:00006795 c:\aloha\bin\grind.exe"
Jul 03, 09:04:41, [2604], [INFO],,"0040C826 0012DAA4 0001:0000B826 c:\aloha\bin\grind.exe"
Jul 03, 09:04:41, [2604], [INFO],,"004E4165 0012DAC0 0001:000E3165 c:\aloha\bin\grind.exe"
Jul 03, 09:04:41, [2604], [INFO],,"004E4486 0012DF34 0001:000E3486 c:\aloha\bin\grind.exe"
Jul 03, 09:04:41, [2604], [INFO],,"004DB564 0012DF58 0001:000DA564 c:\aloha\bin\grind.exe"
Jul 03, 09:04:41, [2604], [INFO],,"004D8EFA 0012FF18 0001:000D7EFA c:\aloha\bin\grind.exe"
Jul 03, 09:04:41, [2604], [INFO],,"006D8D0B 0012FFC0 0001:002D7D0B c:\aloha\bin\grind.exe"
Jul 03, 09:04:41, [2604], [INFO],,"7C816FD7 0012FFF0 0001:00015FD7 C:\WINDOWS\system32\kernel32.dll"
Jul 03, 09:04:41, [2604], [INFO],,"Begin looping through registered threads..."
Jul 03, 09:04:41, [2604], [INFO],,"End looping through registered threads."
Jul 03, 09:04:41, [2604], [INFO],,

 

[IndexRobert]

Try running a fixlog with the /debug command. It should give you the offset where it goes haywire. Use that to read the trans.log and see what the faulty transaction is.