ALOHA Terminal Memory Error

[JM20]

Hi Teks -

Our store is running Aloha 6.2.15...we have 16 terminals and every night when the End of Day runs, one particular terminal will generate the error: "End Program - Table Service (The system cannot end this program becasue it is waiting for a response from you)"

There's also a dialog box in front with:
"Table Service: iber.exe - Application Error (The instruction at "0x00aa52647" referenced memory at "0x01bf3b40". The memory could not be "read". Click on OK to terminate the program.

If I click on OK, Aloha will restart and everything is ok until the next End of Day runs.
It's just very annoying that every morning I come in I have to visit this one terminal and click "OK" to get the term back online.

Any ideas? Setting adjustment?

Thanks in advance for any help!

--Joe
PS - Happy New Year!

 

[coorsman]

Look at the debout (debug output) file for that terminal, it is located in the \aloha\tmp folder. It should end in the terminal number, can be opened in notepad: then scroll to the end. Check the last line for any error information.

 

[JM20]

Hi coorsman -

First, thanks for the info!

Ok...I took a look at the file you spoke of and here's what's listed at 04:00 (which is when the end of day runs and the system refreshes:
Would you mind taking a quick peek and see if anything jumps out at you?
I'll look at this file on another terminal and compare to see if anything looks out of sorts.

Dec 30, 22:00:00, [2660], [INFO],,"firing 22:00:00 SET BAR MENU 33"
Dec 30, 22:00:00, [2660], [INFO],,"firing 22:00:00 SET SERVER MENU 30"
Dec 31, 04:00:00, [2660], [INFO],,"AUTO EOD..."
Dec 31, 04:00:00, [2660], [INFO],,"firing 28:00:00 AUTO EOD"
Dec 31, 04:00:11, [2660], [INFO],,"EOD indicator file found, waiting for completion..."
Dec 31, 04:00:31, [2660], [STATUS],,"EOD file is now gone, exiting..."
Dec 31, 04:00:31, [2660], [STATUS],,"Exiting program 1..."
Dec 31, 04:00:31, [2660], [INFO],,"unloading InterceptAlohaPrinting handlers..."
Dec 31, 04:00:31, [2660], [INFO],,"** Shutdown pausing per OPOSSHUTDOWNWAIT variable in Aloha.ini (1) seconds."
Dec 31, 04:00:32, [2660], [INFO],,"Warning: Destroying thread for printer 22"
Dec 31, 04:00:32, [2660], [STATUS],,"Exiting program 2..."
Dec 31, 04:00:32, [2660], [STATUS],,"Exiting program 3..."
Dec 31, 04:00:32, [2660], [INFO],,"Main directory - C:\Aloha\\EGICACHE"
Dec 31, 04:00:32, [2660], [INFO],,"EGI Scheme C:\Aloha\\EGICACHE\Banana - 3 "
Dec 31, 04:00:32, [2660], [INFO],,"g_ReferencedEGIBitmapsKeys has 5 items"
Dec 31, 04:00:32, [2660], [INFO],,"EGI bitmap file created successfully!"
Dec 31, 04:00:32, [2660], [INFO],,"net shutdown!"
Dec 31, 04:00:32, [2660], [INFO],,"HANGUP: return code 08"
Dec 31, 04:00:32, [2660], [INFO],,"Canceling datagrams..."
Dec 31, 04:00:32, [2660], [INFO],,"Canceling datagrams second time..."
Dec 31, 04:00:32, [2660], [INFO],,"Dropping names..."
Dec 31, 04:00:38, [2660], [INFO],,"Net shutdown complete"
Dec 31, 04:00:38, [2660], [STATUS],,"Exiting program 4..."
Dec 31, 04:00:38, [2660], [INFO],,"Windows NT will log off instead of rebooting. We will not stop IBM 4695 touch-screen drivers."
Dec 31, 04:00:38, [2660], [INFO],,"Operating system is Windows XP (BuildNumber 2600, Platform 2, Version 5.1, Service Pack 2)"
Dec 31, 04:00:38, [2660], [INFO],,"Logging Off WindowsNT...

 

[JM20]

OK I compared this file to another terminal and one thing I should point out is that I do have a kitchen printer associated to the terminal in question.

I do see one error in the file "Warning: Destroying thread for printer 22" which we do sometimes turn off during the slow times.

So my question is...if that printer is off and assocaated to the terminal in question, could it be causing the end program error? Would seem weard to me, but I guess I could try leaving it on one night and see if the terminal refreshes successfully.

Any ideas or something else to look for a greatly appreciated!

Happy New Years!

--Joe

 

[alohatech2]

Try increasing OPOSSHUTODOWNWAIT in aloha.ini