Aloha: EOD running twice, and System thinks it's Tomorrow

[Shatner]

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 to necessity.. much from this site (thanks!), I've replaced/moved/rebuilt terminals and printers, and solved several longstanding issues for them.. but now I have hit a roadblock:

System Summary: Aloha version 5.2, 4 terminals

Starting about a week ago, one restaurant system stopped automatically running EOD. The restaurant manager forced EOD a couple of days in a row, ran into a problem with the server (unknown what this was, or what they thought this was), but he made terminal1 the master.... and then called me.

I went out on site, did fileserver recovery, worked fine. Except we now had a blank Tuesday data.. It was now Thursday, but the system thought it was Friday (dates at bottom of terminals/reports etc.)

So I went in after they were done for the day, but before 4am EOD run, I stopped FOH, erased the incorrect blank Tuesday dated dir, (After backup of all data of course), renamed the wed dir to the correct Tuesday date and on down the line, edited aloha.ini on each dated dir for correct date, and in both data and newdata directories. Erased downtime.ini from all terminals, did refresh data.. and did a regrind of all those directories for good measure... and all seemed fine.

Next day, it had skipped a day again -- all the data Tue-Thur was fine and matches up. Friday dated dir now exists and is all zeros in reports, and it thinks it's Saturday. -- Debugging files are/were yielding no help as far as errors/triggers.

Now for the last week, every time EOD does run (forced or auto).. it runs twice. Runs for the current day, copies data to dated dir, copies data from newdata, increments aloha.ini's, auto grinds new dated dir, terminals come backup up. About the time they all get back up they switch to waiting for EOD or processing EOD respectively, Whole process runs again and leaves that blank day for the current date... system now thinks DOB is tomorrow.... increments aloha.ini's etc. Then everything is fine except it's on the wrong day. Terminals have DOB vs. System Date 1 day off (DOB being +1).. I hop in, move it all around again, edit .ini's and refresh data -- and all is happy..as long as I leave the current days wrong dated directory in the aloha directory.. If I delete it, as soon as I do refresh data, it refreshes - run's EOD and sticks and makes DOB tomorrow again -- If I leave it in there they can at least run for the day - but cant get reports on current day from BOH - have to view from terminal. I hop in and 'fix' it post EOD and before they get to work each morning. moving the directories around and editing aloha.ini's......obviously doing this everyday is not a viable solution for either of us.

Any idea where/how this second EOD run is getting triggered or what my lack of experience is missing in some file somewhere that is telling it that it's tomorrow ? I've used the GUI to set system DOB date, manually done it, and tried everything I could find even a vague mention of within this list...

Any suggestions you might have will be MUCH appreciated,

 

[rdubrey4]

Make sure under events that the EOD event is set to 2800 for 4am. Weird Aloha thing. Make sure the time and time zones are correct everywhere. Hope that helps.

Rob

 

[Shatner]

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

 

[posknowitall]

Make sure there is a done30 and a gnddbf30xxx in each dated subdirectory. Be sure you change the date in newdata and refresh. Sometimes you can see what is happening. Be sure your MASTER term has the correct date in the aloha.ini. Make sure you have a dated subdirectory for each date up to the current date.
Delete downtime.ini from each terminal shut them all down and restart one terminal at a time. Sounds like system is confused.

 

[alohaakamai3]

The most common cause of this is that the date/time is wrong in windows on the whatever terminal is master. Check to make sure the Windows date/time is write on the terminals, as someone else suggested.

I've run into the EOD Event being wrong too. Customer tried to change it to 5am, but instead did 5pm. As he is kind of computer illiterate and not the type to mess with things, I never suspected that this would have been altered, and spent a lot of time trying "long shots" until I finally ran out of options and checked it.

 

[joseph2007]

verify in aloha\data\aloha.ini the DOB its the correct (format yyyy mm dd)

 

[RosemarysBaby]

Shatner
Why not post back and let forum know your current status. Problem fixed, not? The date problem you're having is probably easy to troubleshoot and isolate. The above posts probably nailed it. Update pleeze, as I've had this same date problem thing in the past and I'm curious.