acuity2011
Technical User
All FOH terminals are displaying "Transaction log error, Call tech support". Did have some issues with a starting 1 terminal this morning but its fixed now. How do I clear this message from the terminals.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Aloha - Transaction log error 2
- Thread starter acuity2011
- Start date
- Status
kabaks2013
Technical User
rename the trans.log file which located in \AlohaQS\Data\ or \Aloha\Data from the server and all terminals.
NOTE : by renaming this file you will find there's no sale for this day.
NOTE : by renaming this file you will find there's no sale for this day.
- Thread starter
- #3
acuity2011
Technical User
So how do I get my sales transactions back for today. The FOH terminals are behaving normally except for the message under the number pad on the screen.
There is a suggestion on another web site that says; "Run the fix trans.log batch files in C:\ITTools\Fixlog in sequence (1, 2, 3, and then 4). You should get confirmation messages upon successful completion of each step." Not sure if they mean on each FOH terminal or just on the BOH server. Besides dont see C:\ITTools\Fixlog on the hard drive, create it ?? and run fix trans.log.
Help please.
There is a suggestion on another web site that says; "Run the fix trans.log batch files in C:\ITTools\Fixlog in sequence (1, 2, 3, and then 4). You should get confirmation messages upon successful completion of each step." Not sure if they mean on each FOH terminal or just on the BOH server. Besides dont see C:\ITTools\Fixlog on the hard drive, create it ?? and run fix trans.log.
Help please.
kabaks2013
Technical User
Aloha re seller the only one who authorized to view or fix the trans.log file , you have to send them the file and they will fix it for you . there's no other tools to fix or view the trans.log
-
2
- #5
TheMagicJBone
MIS
If you have that message onscreen, but you can still use the terminals, just keep rolling. The trans.log may have some errors that make for problems generating reports, but finish the day and worry about that later. There's a flag in store settings (continue FOH on log error) that's obviously checked in your case; this is the situation it's designed for.
And any time anybody tells you to rename/move/delete the log in the DATA folder, start looking for help elsewhere. That's not for a user, that's the kind of thing you only want done by trained support.
Case in point: there's plenty you can do to fix the log, especially in a case like this. Once EOD runs, you can run grind/grindq with the /fixlog flag to take care of most corruption. You may have a fixlog program somewhere on your BOH machine that you could run, but note that these are version-dependent. Also, if you had removed or renamed the log and started a new one, you can rename the second log, merge them with a DOS command (copy /b old.log+new.log merged.log) and rename the result to trans.log, put it in the dated subfolder, and regrind. You may need the /fixlog grind/grindq flag or the fixlog.exe for your version after that.
And any time anybody tells you to rename/move/delete the log in the DATA folder, start looking for help elsewhere. That's not for a user, that's the kind of thing you only want done by trained support.
Case in point: there's plenty you can do to fix the log, especially in a case like this. Once EOD runs, you can run grind/grindq with the /fixlog flag to take care of most corruption. You may have a fixlog program somewhere on your BOH machine that you could run, but note that these are version-dependent. Also, if you had removed or renamed the log and started a new one, you can rename the second log, merge them with a DOS command (copy /b old.log+new.log merged.log) and rename the result to trans.log, put it in the dated subfolder, and regrind. You may need the /fixlog grind/grindq flag or the fixlog.exe for your version after that.
- Thread starter
- #6
acuity2011
Technical User
Thanks TheMagicJBone for your invaluable suggestions.
The FOH was running but the BOH would not generate any reports. I was concerned that I may not be ale to run EOD.
I was able to fix the problem on Sept 3 by simply running fixlog and then dropping the resulting file (fixed - renamed it translog)in the DATA folder. The BOH started to grind and generate reports for the day, was also able to run EOD with no issues.
I will keep your instructions handy for future issues - Thanks.
The FOH was running but the BOH would not generate any reports. I was concerned that I may not be ale to run EOD.
I was able to fix the problem on Sept 3 by simply running fixlog and then dropping the resulting file (fixed - renamed it translog)in the DATA folder. The BOH started to grind and generate reports for the day, was also able to run EOD with no issues.
I will keep your instructions handy for future issues - Thanks.
- Status
Similar threads
- Question
