Micros E7 on WS4 "Communitions errors"

[skventura]

I have been helping a new store manager with his Micros System problems. It has a PC and a Server and a Counter. The PC is an XP system and the terminals are WS4 running Windows CE. Twice I have had it happen that Server 1 shows itself as active, but the PC and counter as inactive. When you look at the workstations from the counter or the PC, however, it shows only Server 1 as inactive. So, I was able to get Server 1 reactivated. Then, Counter 1 said that it couldn't communicate with the kitchen printer. Last night, the business date would not update because it said "Communication problem with Server 1" after we incremented the business date, the PC was fine. Then server 1 said "cannot communicate with Counter 1" All the workstations appear active and the network shows active too. All network cables are in place with no frayed edges. The rounter is only 3 months old. Any ideas?

 

[Moregelen]

Lack of frayed edges doesn't mean much. Check their pairs with a pair tester.

Try doing a 'retrieve all' on the workstations off of the server. It might just be some things have managed to get out of sync, so retrieving everything might help.

Just because your switch and router are new doesn't mean it can't be going bad. I would probably check first that the network is stable and everything is talking; E7 is finicky about how it communicates. If something goes down, the other workstations will basically 'attack' it, setting it to inactive. Its a real pain if the workstation just went down temporarily but ended up getting set to inactive while it was down.

 

[skventura]

Thanks for your help. I just learned that he has U-verse instead of DSL and the router they gave him is not very reliable. We are going to put the LAN on a Linksys Router and see if that helps.

 

[skventura]

Good work Moregelen! You were right on the money! It was the network connection next to Server 1. I was suspicious of it because it was hanging down and the connection was exposed. Evidently during a remodel of the restaurant, the terminal was moved, but they did not have enough Ethernet cable. So, they opened the network box and pulled out the connector and stretched it across the counter. It worked fine for a while, but at some point, one of the internal wires broke and that is what was causing intermittent communication errors. I spoke to a nice technician at Micros and he told me that communication problems are actually Network problems 90% of the time. It is rare that the terminal's ethernet port fails.

 

[Moregelen]

*shakes head*

It really is hard to find a good low voltage electrician. I've gotten so sick of having to crawl around having to run and repair wires because they cut corners.