Aloha terminal not recoqnizing BOH as FILESERVER 2

[sas1589]

Monday morning the BOH computer (SERVER) restarted on its own, next thing, the two front terminals failed to recoqnize the BOH computer as its server. I've tried unplugging EVERYTHING, plugging one terminal back in, turning on the hub, and turning on the BOH computer. .. Nothing.

I've tried deleteing the Downtime.ini file from the terminals.

There is def. a connection between the BOH and FOH as i can still access FOH through Aloha Manager, and VZW viewer. So i dont believe there is a problem with any of the cables.

The termninal would attempt to find the FILESERVER only to give the message "aloha takeout server unavailable at this time" and attempts to connect to a new file server, failing everytime. I had no choice but to put the terminals on Reduntecy mode.

and now the video kitchen screen are blue; the port numbers and ip & subnet adds. are correct, so i'm thinking those are connected.

any help would be appeciated


From the DEBOUT file..
Jun 14, 15:39:45,, [STATUS],,""
Jun 14, 15:39:45,, [STATUS],,"................................................................"
Jun 14, 15:39:45,, [STATUS],,"EDC (Client) v6.2.22.1373 started...(local debout)"
Jun 14, 15:39:45,, [INFO],," Connecting to Edc DCOM server..."
Jun 14, 15:39:45,, [INFO],,"Edc Client connected to Edc DCOM server."
Jun 14, 15:39:45,, [INFO],,"LoadIberStrings() - Loaded version 6.2.22.0, D:\AlohaQS\bin\IBERSTR.DLL"
Jun 15, 10:33:31,, [STATUS],,""
Jun 15, 10:33:31,, [STATUS],,"................................................................"
Jun 15, 10:33:31,, [STATUS],,"EDC (Client) v6.2.22.1373 started...(local debout)"

 

[alohahello]

what is on your startup on your alohaboh? if you do have the newer version you will have some type of program in your start up. also did you clear out the contents in your tmp folder on the alohaboh like DTSMAN suggested?

 

[IberRoot]

alohahello: DTSMAN suggested he delete contents of tmp folder on terminal, not server. But I would expect there to be nocomm's (printers that failed communication) in server tmp folder for failed printer auto reroute.

 

[sas1589]

Got it. Wet into mscinfig. Kds was unchecked for startup, any idea why or HOW that would happen, I'm the only one who uses the big computer and I know I didn't change any settings.

 

[alohahello]

usually you have to remove it from the startup in msconfig or delete the icon from the actual start up folder. maybe someone was on it a while back and you just happen to reboot at a later time.