Search results for query: *

Upon settling batch, one restaurant I assist with is getting the following error: "Rejected batch - header record field 18, error E" This has apparently been occurring for 3 days, so there are a couple of hundred transactions now for which the batch has not closed. The CC processing company...

Okay.. I was wrong on my previous post.. none of the above has worked.. and it's still going to tomorrow. I've been continuing to rig it everyday... not going to work when I'm out of town next week. I've made 'term2' master as suggested to no avail, and found/located/tested every timezone/date...

Just to report back.. I did finally find the solution. Even though all the terminals, and the BOH computer were all set to Central Standard Time Zone.. and the correct time, I noticed that the timezone.ini in the data dir had the timezone listed as 'Aloha Standard Time' The Windows 95...

Thank you very much.. Thats exactly the info I was looking for.. I'll give disabling term1 as a master a try, and quadruple check that there are not multiple EOD events, dates, times and report back :) Thanks again

EOD is set for 2800 It may not have been clear in this post, but it's not running at two different points of the day, or the wrong point in the day. EOD runs TWICE at 2800 (4am). Runs yesterdays day.. makes dated dir.... looks happy.. faster terminals come up fine and have right system date...

You can make a copy of it, and then do fixlog on it, if you have fixlog for your version... See this thread : http://www.tek-tips.com/viewthread.cfm?qid=1200614

If you have a bad trans log.. it should show up in your EOD logs. Since this is happening over multiple days, I don't think it can be a bad trans log, because that gets moved into the dated dir each night, and a new one gets created. (There should not be a trans.log at all in the newdata...

When it is displaying that message, you might test at that point and see if the UNC path works from term to term, and from a term to boh and vice-versa. Might be something as simple/annoying as the BOH networking locking up/bad network card/driver or something in BOH server, since you...

Have you tried to see if you can see the terminals from the boh server or vice versa ? Try a UNC path from the BOH server in Windows Explorer like \\term1\bootdrv\aloha and see if you pull anything up -- adjust the path to suit your system name/path if needed. Make sure the ctlsvr service...

The Aloha install I'm working on tries to do EOD twice and skips the current day. After I reset it (either via aloha.ini or with GUI/System Date) - and refresh data, it works for the current day, but next morning it goes through the same process again. (As soon as term1, the master, finished...

Timezones/time/date on all the terminals and the BOH server are all correct. Terminals show the System date at the bottom properly - just after the second EOD that occurs as explained origianlly the DOB date is 1 day ahead as picked up from the aloha.ini I assume. Thanks for the suggestion

I have a problem I'm hoping you Aloha guys can help me on, I'm not an authorized Aloha reseller/expert by any means, very little experience, but I'm in a situation where I've become responsible for several restaurants about 2 months ago due to their situation.... I've learned allot fast due...