I recently had a BOH server crash (Windows NT service pack 5). I installed Aloha 5.3.1 on a new computer (Windows XP Professional Service pack 1). Everything seems to be running fine except for end of day process. FOH terminals lock up during process (status bar says processing end of day). Some days: from Data Manager, reports, I can see the appropriate previous day and sales show up. In this situation I delete the EOD file from Aloha\Data, copy a GRNDD.XXX and a DONE30 file into the previous day, restart CVR.EXE, restart FOH terminals and all is well. Other days: from Data Manager, report, I can see appropriate previous day but sales are zero, sales show up in current day. In this case, I remove the EOD file from Aloha\Data, change DOB to previous day, delete previous date folder, force end of day and restart FOH terminals then all is well. I have done grind.exe on all prior dates up to server crash date. I have done data base upgrade on all these dates as well. Yet, only one day since crash has the end of day process gone through automatically without a glitch. Please help!
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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Aloha end of day error 1
- Thread starter rrgrill
- Start date
AkamaiAloha
MIS
Good luck with this one. I've had my share of EOD problems with XP, and posted the problems on here for some of the knowledgable people, to no avail. Some people insist that these problems don't exist (no Adam, I am not picking on you 
), but I have seen them with that OS more than other. Chalk it up to hardware maybe? I don't know.
Because we have so many do-it-yourselfers joining the forum, I have to ask--what is your level experience with Aloha? I am assuming if you have it set up and at least working, you know some stuff. But did you follow the specs of the AKB? At least then, we have a starting point for your issue, for this often complicated and elusive EOD problem. (I have a similar situation with a site now, that has not been resolved).
Two quick things:
Did you disable write-behind caching on the Aloha drive (Bootdrv)? This is supposedly a culprit in some EOD problems, but before you get too excited, it didn't fix mine.
Look in your Debout.EOD and possibly post the results. Usually, it fails at some checkpoint, and you have some place to start.
Good luck!
), but I have seen them with that OS more than other. Chalk it up to hardware maybe? I don't know. Because we have so many do-it-yourselfers joining the forum, I have to ask--what is your level experience with Aloha? I am assuming if you have it set up and at least working, you know some stuff. But did you follow the specs of the AKB? At least then, we have a starting point for your issue, for this often complicated and elusive EOD problem. (I have a similar situation with a site now, that has not been resolved).
Two quick things:
Did you disable write-behind caching on the Aloha drive (Bootdrv)? This is supposedly a culprit in some EOD problems, but before you get too excited, it didn't fix mine.
Look in your Debout.EOD and possibly post the results. Usually, it fails at some checkpoint, and you have some place to start.
Good luck!
-
1
- #4
What OS are the terminals running? If running a non-secured operating system make sure the security in XP is set to allow full access to users with a blank password.
Be sure all drive sharing is set to full access and your users and passwords are all correctly set up. Try changing or deleting files on the fileserver from the master thru the network. Try the same on the master from the fileserver.
I recomend turning off restore points.
Check the debout!
Make sure you have NO files or folders in Aloha that are read only including the contents of bin.
Try a different master if needed.
Be sure all drive sharing is set to full access and your users and passwords are all correctly set up. Try changing or deleting files on the fileserver from the master thru the network. Try the same on the master from the fileserver.
I recomend turning off restore points.
Check the debout!
Make sure you have NO files or folders in Aloha that are read only including the contents of bin.
Try a different master if needed.
- Thread starter
- #6
- Status
Similar threads
- Locked
- Question