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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Need some help on Aloha file server problem, ver 5.3.21

Status
Not open for further replies.

fcam00

Technical User
Dec 9, 2009
21
US
Hope someone can shed some light for me here.

There are few error messages/problems I want to correct, but need some help here.
I'm running a Files Server with windows 2000, two terminals running XP embedded. Aloha version 5.3.21

Problem #1:
Every time I start Aloha Manager in BOH, there is a DOS screen pop up with this message below:

Running in Attended Mode
Upgrading DBF Files Only
Current DBF File(s) Location D:\Ahoha\NEWDATA
Upgraded DBF File(s) Location D:\Aloha\NEWDATA
Upgrading DBF Files Only
Running for non Enterprise site
Read INI file D:\Aloha\NEWDATA\ALOHA.INI

how do I get rid of those errors.

Problem #2:
About 3-4 weeks ago (when the daylight-saving chanced), my system acting wear.
During the first weeks or so after the daylight-saving chanced, Terminal1 doesn't look like it syn with BOL. In morning when I log in, terminals would show 1 day behind.

Right now, in the morning when I log in terminals, the date is syn with BOH ok, but hours are not.
I use keyboard went to each terminal and manually changed the clock for each terminal correctly to current time. BUT, when I restart the terminals the hours move back to 1 hour behind again (BOH showing 2:30, Terminals would show 1:30).

Right now I have to manually set lunch event to dinner menu daily, because Terminal showing 1 hour off.

Also, I think system doesn't post at EOD.

I think that possible I have similar issue described in this thread, am I not?

Thank you for your time to read this, and any respond is greatly appreciated.
 
Problem 1#
When aloha manager is first opened it is normal to see the little command box. It reads your database files and aloha.ini.

Problem 2#
If your system is always 1 day behind every morning then your system is not preforming an end of day correctly. Since the terminals are still up then it leads me to believe it is not even trying to end of day. Go to the debouts and see what it is doing. and post them here.
 
Thanks for your quick respond alohahello.
Sorry for this ignorance question, but where do I find debout?
Thanks
 
Aloha\TMp directory. There you will find a debout for almost everything aloha does.
 
I found the directory, but I have to step out for the day.
I will post the debout file tomorrow. Do you want the file ending with .EOD right?
I use wordpad to open, but don't have a jump drive with me at the moment.
Thank you for your time alohahello.
Great forum.
 
On the terminal at the bottom, is the DOB - date of business correct and the system time and date behind or what. Aloha has a patch for DST and a link can be found here on the tech site.
 
Quote: Aloha\TMp directory. There you will find a debout for almost everything aloha does.

I think this morning the system actually posting ok, I'm not expert so please scan through this report and inform me it ok.
Apr 22, 04:00:00 [208] EOD invoked
Apr 22, 04:00:00 [208] EOD invoked A
Apr 22, 04:00:00 [208] Starting EOD...
Apr 22, 04:00:00 [208] Created EOD marker file
Apr 22, 04:00:00 [208] Created EOD Marker File Z:\Aloha\DATA\UPDATE.STR
Apr 22, 04:00:01 [208] EOD Marker File Renamed by CtlSvr
Apr 22, 04:00:02 [208] Checkpoint PRT: result 1
Apr 22, 04:00:02 [208] Closing open sales...
Apr 22, 04:00:02 [208] lookup_stat_periodtype: period 1 tips id 1 not in list
Apr 22, 04:00:02 [208] lookup_stat_periodtype: period 2 tips id 1 not in list
Apr 22, 04:00:02 [208] EXCEPTION: DOB: 4/21/2010 Emp 218 (xxx KAN) did not check out. Cash owed: xxx.00
Apr 22, 04:00:02 [208] lookup_stat_periodtype: period 1 tips id 1 not in list
Apr 22, 04:00:02 [208] lookup_stat_periodtype: period 2 tips id 1 not in list
Apr 22, 04:00:03 [208] EXCEPTION: DOB: 4/21/2010 Emp 1111 (xxx TRAN) did not check out. Cash owed: xxx.81
Apr 22, 04:00:03 [208] lookup_stat_periodtype: period 1 tips id 1 not in list
Apr 22, 04:00:03 [208] lookup_stat_periodtype: period 2 tips id 1 not in list
Apr 22, 04:00:03 [208] EXCEPTION: DOB: 4/21/2010 Emp 1975 (xxx VUONG) did not check out. Cash owed: xxx.30
Apr 22, 04:00:03 [208] lookup_stat_periodtype: period 1 tips id 1 not in list
Apr 22, 04:00:03 [208] lookup_stat_periodtype: period 2 tips id 1 not in list
Apr 22, 04:00:03 [208] EXCEPTION: DOB: 4/21/2010 Emp 2222 (xxx Haidir) did not check out. Cash owed: xxx.28
Apr 22, 04:00:03 [208] lookup_stat_periodtype: period 1 tender id 11 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 1 tender id 12 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 1 tender id 13 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 1 tender id 14 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 1 tender id 15 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 1 tender id 16 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 1 tender id 19 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 1 tender id 20 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 2 tender id 11 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 2 tender id 12 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 2 tender id 13 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 2 tender id 14 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 2 tender id 15 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 2 tender id 16 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 2 tender id 19 not in list
Apr 22, 04:00:04 [208] lookup_stat_periodtype: period 2 tender id 20 not in list
Apr 22, 04:00:04 [208] EXCEPTION: DOB: 4/21/2010 Emp xxx (xxx TRAN) did not check out. Cash owed: xxx.00
Apr 22, 04:00:04 [208] Clocking out remaining employees...
Apr 22, 04:00:04 [208] EXCEPTION: DOB: 4/21/2010 Emp 218 (JEAB KAN) clocked in at 10:19 and did not clock out
Apr 22, 04:00:04 [208] EXCEPTION: Clocked employee out automatically
Apr 22, 04:00:04 [208] EXCEPTION: DOB: 4/21/2010 Emp 1111 (xxx TRAN) clocked in at 10:45 and did not clock out
Apr 22, 04:00:04 [208] EXCEPTION: Clocked employee out automatically
Apr 22, 04:00:04 [208] EXCEPTION: DOB: 4/21/2010 Emp 1975 (xxx VUONG) clocked in at 11:37 and did not clock out
Apr 22, 04:00:04 [208] EXCEPTION: Clocked employee out automatically
Apr 22, 04:00:05 [208] EXCEPTION: DOB: 4/21/2010 Emp 2222 (xxx Haidir) clocked in at 10:40 and did not clock out
Apr 22, 04:00:05 [208] EXCEPTION: Clocked employee out automatically
Apr 22, 04:00:05 [208] EXCEPTION: DOB: 4/21/2010 Emp xxx (xxx TRAN) clocked in at 10:27 and did not clock out
Apr 22, 04:00:05 [208] EXCEPTION: Clocked employee out automatically
Apr 22, 04:00:05 [208] Logging EOD message...
Apr 22, 04:00:05 [208] Creating Z:\Aloha\DATA\PRT1.LOG...
Apr 22, 04:00:05 [208] Bringing down remaining terminals...
Apr 22, 04:00:07 [208] AUTO EOD...
Apr 22, 04:00:35 [208] Commence rolling directory...
Apr 22, 04:00:35 [208] Creating subdirectory Z:\Aloha\20100421
Apr 22, 04:00:35 [208] Checkpoint A: result 1
Apr 22, 04:00:35 [208] Checkpoint A1: result 1
Apr 22, 04:00:35 [208] Checkpoint A2: result 1
Apr 22, 04:00:37 [208] Checkpoint B: result 1
Apr 22, 04:00:39 [208] Checkpoint C: result 1
Apr 22, 04:00:39 [208] Checkpoint C2: result 1
Apr 22, 04:00:40 [208] Checkpoint D: result 1
Apr 22, 04:00:40 [208] Checkpoint E: result 1
Apr 22, 04:00:40 [208] Checkpoint E3: result 1
Apr 22, 04:00:40 [208] Checkpoint E4: result 1
Apr 22, 04:00:40 [208] Checkpoint E5: result 1
Apr 22, 04:00:40 [208] Checkpoint E7: result 1
Apr 22, 04:00:40 [208] Checkpoint E8: result 1
Apr 22, 04:00:40 [208] Checkpoint E9: result 1
Apr 22, 04:00:40 [208] Checkpoint G: result 1
Apr 22, 04:00:40 [208] Checkpoint H: result 1
Apr 22, 04:00:40 [208] Checkpoint I: result 1
Apr 22, 04:00:40 [208] Checkpoint I2: result 1
Apr 22, 04:00:40 [208] Checkpoint I3: result 1
Apr 22, 04:00:40 [208] Checkpoint I4: result 1
Apr 22, 04:00:40 [208] Checkpoint I5: result 1
Apr 22, 04:00:40 [208] Checkpoint Jerrett: result 1
Apr 22, 04:00:40 [208] Updating house account information...
Apr 22, 04:00:40 [208] Updating employee passwords...
Apr 22, 04:00:41 [208] Incrementing DOB...
Apr 22, 04:00:41 [208] Checkpoint K: result 1
Apr 22, 04:00:41 [208] NEWDATA Copy Test: robust 1 IsLocalTerminalBOH 0 IsFileserverBOH 1
Apr 22, 04:00:43 [208] Checkpoint L: result 1
Apr 22, 04:00:45 [208] Checkpoint M: result 1
Apr 22, 04:00:45 [208] Checkpoint N: result 1
Apr 22, 04:00:45 [208] Checkpoint O: result 1
Apr 22, 04:00:45 [208] Checkpoint P: result 1
Apr 22, 04:00:45 [208] Updating adjtime files...
Apr 22, 04:01:12 [208] Done updating adjtimex files...
Apr 22, 04:01:12 [208] Updating gndowage files...
Apr 22, 04:01:29 [208] Done updating gndowage files...
Apr 22, 04:01:29 [208] Deleting EOD marker file...
Apr 22, 04:01:29 [208] Exiting program after EOD...
Apr 22, 04:01:29 [208] net shutdown!
Apr 22, 04:01:29 [208] HANGUP: return code 08
Apr 22, 04:01:29 [208] Canceling datagrams...
Apr 22, 04:01:29 [208] Canceling datagrams second time...
Apr 22, 04:01:29 [208] Dropping names...
Apr 22, 04:01:36 [208] Net shutdown complete
Apr 22, 04:01:45 [208] Operating system is Windows XP (BuildNumber 2600, Platform 2, Version 5.1)
Apr 22, 04:01:45 [208] Exiting WindowsNT...
 
Quote:
On the terminal at the bottom, is the DOB - date of business correct and the system time and date behind or what. Aloha has a patch for DST and a link can be found here on the tech site.


Here are what I've got.

In the bottom of POS screen, DOB and SysDate are correct (4/22). But I went to Aloha Manager in BOH it shows Day of Business is 04/21/2010. Previously, this is the first step I would take was update BOH Day of Business to current, and refresh the system. However, after refreshed, FOH's time will mess up again. So, today I didn't update the date BOH, waiting for your insight.

Secondly, I checked the time on both terminals, they showed 1 hour behind, so I hook up a keyboard and changed the terminal system clock to correct/current time (at the bottom right of screen, double click on the time, and changed it to current).
I noticed that as soon as I click done, terminal briefly search for file server (I see a red border around the POS screen for about 1 second or so), but then system clock changed back to 1 hour behind again. Very odd.
What's your thought on where should I check/correct.
Thank you for your time.
 
yes it definitely ran an end of day. Check year terminals and see what zone you are in. If im not mistaken the aloha dst patch would put you around lima or some other country. in that case you would most likely need the patch.
 
I check the system clock, timezone for all of the machines, and all of them are setting the timezone for Eastern Tim (US & Canada), which is correct.

This morning, first thing I check in Store Setting Maintenance, under System tab I just realized that Day of business was 04/21/2010. All of the terminals out front are showing DOB and SysDate are 04/23/2010 (as soon as you touch the screen, they showing in bottom of the screen), although time is still 1 hour off.
I then have customer come in so I forced to quickly correct the DOB in BOH to today (23rd), refresh data, so everything can be function normally at the moment.

I went to check in debouts files (this is after I corrected the DOB)and doesn't look like system posting EOD last night, am I wrong.
Here's the script:
Apr 23, 10:41:31 [184] EOD invoked
Apr 23, 10:41:31 [184] End of Day already completed (found Z:\Aloha\20100421\DONE30)
Apr 23, 10:41:31 [184] Did you have the Maintenance program running during EOD?
Apr 23, 10:41:31 [184] You may need to increment your DOB. Contact tech support.
Apr 23, 10:41:31 [184] End of Day will not run until problem is resolved.
Apr 23, 10:41:33 [184] LISTEN: CONNECTED TO NODE 2! (1)
Apr 23, 10:46:34 [184] RECEIVE failure: node 2 code 0A command 95
Apr 23, 10:46:34 [184] Found STOP file, exiting...
Apr 23, 10:46:34 [184] net shutdown!
Apr 23, 10:46:34 [184] Canceling datagrams...
Apr 23, 10:46:34 [184] Canceling datagrams second time...
Apr 23, 10:46:34 [184] Dropping names...
Apr 23, 10:46:40 [184] Net shutdown complete
Apr 23, 10:46:49 [184] Operating system is Windows XP (BuildNumber 2600, Platform 2, Version 5.1)
Apr 23, 10:46:49 [184] Exiting WindowsNT...

Where should I trouble shoot from this point.
Greatly appreciated any instruction/tips/insights.

 
There's must be some kind of script in the terminal that make overwrite the system clock.
Here's what I did.
Use a keyboard hooking to 1 of terminal. Hit the Windows key to get out of POS screen. Double click on the time in bottom right to bring up Date and Time properties.
At current, POS time show 11:35, system clock of the terminal showing 11:35. Actual time suppose to be 12:35pm.
I manually update the time to 12:35 in Date and Time properties, as soon as I hit apply, POS screen blank for a moment with red border around the screen (disconnect to server I think) time chanced to current, BUT it only last about 3-4 second, system clock switch back to 1 hour earlier again.
I think there's some script in msconfig that prevent the time change or something.
Here's what I have in msconfig (terminal)
WinVNC.................... check
DisableWriteCach...........check
IBERCFG.BAT................check
 
I think I got the timing error outta way.
First of, I should start working from the master terminal rather than the terminal #2.

Secondly, I uncheck the automatically daytime saving, in that way both terminals allow me to set time correct time.

Let see after tonight if the system post at EOD ok.

Thanks for all responds
 
I saw this same problem last week at one of my sites. After doing a timezone adjust at one of our sites the aloha.ini file got doubled. Check the \newdata\aloha.ini file with a text editor - run find and look for DOB= I bet there's 2 DOB's in there. Copy an aloha.ini file from a day that you know is good and edit the DOB= "current date" statement.





 
Coorsman, thanks for your tip.
If tomorrow, after system posted, and problem reoccurs, I know where to look for.
Thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top