Terminal data synchronization error

[sugarguy]

Only on one terminal gives me error booting up saying "data synchronization failed, please check debout for errors." I checked the debout and posted it here... any help quickly thanks!

Jun 17, 15:37:31, [1608], [INFO],,"+++++++++++++++++++++++++++++++++++++++++++++++++++"
Jun 17, 15:37:31, [1608], [INFO],," OS, CPU AND MEMORY INFORMATION"
Jun 17, 15:37:31, [1608], [INFO],,"+++++++++++++++++++++++++++++++++++++++++++++++++++"
Jun 17, 15:37:31, [1608], [INFO],,"OS = Operating system is Windows XP (BuildNumber 2600, Platform 2, Version 5.1, Service Pack 2)"
Jun 17, 15:37:31, [1608], [INFO],,"CPU TYPE = Intel(R) Celeron(TM) CPU 1200MHz"
Jun 17, 15:37:31, [1608], [INFO],,"CPU SPEED = 1202 MHz"
Jun 17, 15:37:31, [1608], [INFO],,"TOTAL PHYSICAL MEMORY = 266846208 Bytes"
Jun 17, 15:37:31, [1608], [INFO],,"+++++++++++++++++++++++++++++++++++++++++++++++++++"
Jun 17, 15:37:31, [1608], [INFO],," OS, CPU AND MEMORY INFORMATION"
Jun 17, 15:37:31, [1608], [INFO],,"+++++++++++++++++++++++++++++++++++++++++++++++++++"
Jun 17, 15:37:31, [1608], [INFO],,"LoadIberStrings() - Loaded version 6.1.17.0, IBERSTR.DLL"
Jun 17, 15:37:31, [1608], [INFO],,"Begin initializing network..."
Jun 17, 15:37:31, [1608], [INFO],,"Initializing network..."
Jun 17, 15:37:31, [1608], [INFO],,"Node = 1 String = 'B'"
Jun 17, 15:37:31, [1608], [INFO],,"NBInit()-> Before NBAddName()-> StationName = "IBERB ""
Jun 17, 15:37:34, [1608], [INFO],,"NBInit()-> After NBAddName()-> StationNumber = 2"
Jun 17, 15:37:34, [1608], [INFO],,"NBInit()-> Before NBAddGroupName()-> SessionName = "IBERLINK""
Jun 17, 15:37:37, [1608], [INFO],,"NBInit()-> After NBAddGroupName()-> SessionNumber = 3"
Jun 17, 15:37:37, [1608], [INFO],,"Station number 2, session 3"
Jun 17, 15:37:37, [1608], [INFO],,"Network initialization complete."
Jun 17, 15:37:37, [1608], [INFO],,"Done initializing network."
Jun 17, 15:37:37, [1608], [INFO],,"Determining Master And Fileserver"
Jun 17, 15:37:37, [1608], [INFO],,"Local DOB is 6/17/2009 in C:\Aloha\DATA\ALOHA.INI (06 17 2009)"
Jun 17, 15:37:37, [1608], [INFO],,"AotoMakeFileserver: FALSE"
Jun 17, 15:37:38, [1608], [INFO],,"Creating terminal status for 3"
Jun 17, 15:37:38, [1608], [INFO],,"Terminal 3 asserts 3 is master"
Jun 17, 15:37:38, [1608], [INFO],,"Master terminal is 3. Now determining fileserver..."
Jun 17, 15:37:38, [1608], [INFO],,"Master Terminal 3 asserts fileserver is 'ALOHABOH'"
Jun 17, 15:37:38, [1608], [INFO],,"Attempting to connect to server 'ALOHABOH'..."
Jun 17, 15:37:38, [1608], [INFO],,"Successfully connected Z: to \\ALOHABOH\BOOTDRV"
Jun 17, 15:37:38, [1608], [INFO],,"Found fileserver. Updating DOWNTIME.INI..."
Jun 17, 15:37:38, [1608], [INFO],,"Delete MultiSync flag 'C:\Aloha\DATA\MSYNC'"
Jun 17, 15:37:38, [1608], [INFO],,"Beginning synchronize data..."
Jun 17, 15:37:38, [1608], [INFO],,"Iberdir: Z:\Aloha Localdir: C:\Aloha Target: C:\Aloha\DATA"
Jun 17, 15:37:39, [1608], [INFO],,"Creating terminal status for 4"
Jun 17, 15:37:41, [1608], [INFO],,"SYNC: Copied Z:\Aloha\DATA\PRT1.LOG to C:\Aloha\DATA\PRT1.LOG"
Jun 17, 15:37:41, [1608], [INFO],,"FileCopy failed on from: Z:\Aloha\DATA\SUB.CDX to: C:\Aloha\DATA\SUB.CDX...last error returned 1392"
Jun 17, 15:37:41, [1608], [INFO],,"SYNC: Copy failed Z:\Aloha\DATA\SUB.CDX to C:\Aloha\DATA\SUB.CDX (GetLastError = 183)"
Jun 17, 15:37:41, [1608], [INFO],,"Synchronize file Z:\Aloha\DATA\SUB.CDX to C:\Aloha\DATA\SUB.CDX failed, error 2"
Jun 17, 15:37:41, [1608], [INFO],,"SYNC: Copied Z:\Aloha\DATA\SUR.CDX to C:\Aloha\DATA\SUR.CDX"
Jun 17, 15:37:42, [1608], [INFO],,"Beginning synchronize recovery 20090617_*.CKD from C:\Aloha\DATA to Z:\Aloha\DATA..."
Jun 17, 15:37:42, [1608], [INFO],,"End synchronize recovery (total 0 files)..."
Jun 17, 15:37:42, [1608], [INFO],,"Beginning synchronize recovery 20090617_*.CKP from C:\Aloha\DATA to Z:\Aloha\DATA..."
Jun 17, 15:37:42, [1608], [INFO],,"End synchronize recovery (total 0 files)..."
Jun 17, 15:37:42, [1608], [INFO],,"Beginning synchronize BMP..."
Jun 17, 15:37:48, [1608], [STATUS],,"Synchronization of files failed - free disk space on drive C: -1237254144

 

[sugarguy]

Problem solved! I figured it out, turns out the file sub.cdx had to be deleted on the terminal. I couldn't delete it from the main terminal via the network for some reason. It said cannot delete file or folder because it is corrupted or unreadable so I went to the terminal itself and connected a keyboard and tried to delete it again, it deleted and I restarted the computer and it worked. The DOB though is one day ahead of the system date.

 

[coorsman]

You can change the dob in aloha manager under maintenance-system-stores settings or edit the aloha.ini file in newdata and search for dob then refresh the system. If you have a dated sub for the the previous day be sure to rename it so your system will do an end of day.

 

[sugarguy]

Well I went under store settings and changed the date, but now the system event to trigger an end of day at 5:00AM does not fire up at the time, I have to force an end of day in order to do that. The date then goes back ahead one day. Any suggestions? I didn't understand the dated sub being renamed...

 

[sugarguy]

There is a date sub for today, 06/24/2009, should I delete it? or what do I rename it to?

 

[coorsman]

re-naming a folder in windows. Using windows explorer navigate to the aloha directory and look for the dated sub directory you need to remove. You can delete it but it's better to rename it. Highlight the directory you need to get rid of. You can use the properties button located between the alt and ctrl key on the right side of the keyboard then select rename and change it to BAD20090623 or whatever the date is.

 

[alohaakamai3]

Obviously I don't have all the information, but based on my previous experience, it sounds like you have some data corruption issues going on and these problems are going to continue. Files not being able to be deleted, EOD issues, events not firing when they should- could be a disk read/write issues like when a hard drive starts to go bad, or it could be some corrupt Aloha data.

I would consider taking a dated sub before these issues started and copying everything in it (minus the Aloha.ini, the trans.log, those are the main ones you don't want)and copying it to newdata, and refresh the system. Just be aware any menu stuff or employees you've added will revert back to what they were on that date.

No guarantees that this will work, but it's easy enough to do and worth a shot.

The downside is- CDX files are not necessary with Aloha and you should not have had issues deleting due it from the back office to a sharing violation or any other reason- that's what makes me thing you make be experiencing something else like a drive failure.

 

[sugarguy]

I renamed the folder but no luck. The force end day just creates the folder again. Also the event for end of day doesn't fire when I want to at 05:00. The business day starts at 18:00 and ends 02:00 the next day. I have to do a force end day to get the dates to sync because they are a day behind. When I do the end day, it goes ahead 2 days so Im back to a day ahead. In order for everything to work, I have to change the day back under system settings.

 

[alohaakamai3]

Another thought- not sure if you tried what I suggested above- but if your time is wrong on the master terminal on the front of house, I have seen a similar situation.

The BIOS lost it's settings, and it would make windows time off when the computer rebooted nightly. This can cause other issues as well (Trans.log corrupt at position 0, for one), but make sure the time on the master terminal is correct (check all the terminals to be safe).

 

[sugarguy]

ok I did what you suggested early by copying those files to the new data and refreshing it. The days don't skip now when doing end of day. One question though, why doesnt system events fire when the system and DOB and not the same? They have to be the same for it to work. This business is a night club and sales go over midnight to the next day, but the business date is for the previous. How can we fix that?

 

[alohaakamai3]

I'm confused as to what you're asking or the problem you're having.

You're asking why system events don't fire once the day changes over from midnight and the system date and DOB are no longer the same? Like when the clock strikes midnight on System Date: 07/15/09 and then goes to 07/16/09 but is really still Wednesday night?

They still should fire. Are you checked to use a 36-hour clock in Aloha?

 

[sugarguy]

Well I don't know where the option for the 36-hour clock is in Aloha, but I figured it out by putting 29:00 instead of 05:00 to get events to fire for that nite. I guess its checked to use a 36-hour clock. Thanks for all the help Alohaakamai3 and coormans!

 

[posrescue]

surgarguy,
You are correct that 29:00 means 5am in Aloha. There is no option to turn off the extended clock in Aloha. This "extended clock" is to enforce that the Day Of Business extends to it's end and not end at the change of the Windows system date. If the "End of Day" is set to run at 5am it will run before the business day has even started unless you open really early. Of course then it would run during business but that gets more into a 24hr business which can be left to another thread.

Events will only run correctly if the DOB and the System date are in sync. The only time this will look to not be in sync is after midnight during the current DOB however that is normal and correct. The DOB must never be ahead of the Windows system date. Aloha fires events based on the Windows system date and time. If the DOB is ahead of the system date events will not fire.