Weird EDC Problem

[djazz35]

Hi all,

We are having a really strange Aloha EDC issue. As soon as you swipe a credit card for a bill (VISA/MC/AMEX) it spits the receipt out immediately saying not authorized. It never even hits the BOH/EDC and you don't see the transaction in the EDC windows or log.

However, we figured out how to get it straighted out temporarily...

To get things back to normal and working we have to turn off all POS terminals, then shutdown the BOH server. Then boot the server and wait for everything to load, boot the master POS terminal, then the other 2 terminals. Everything works great all day! Then once we settle the MC/VISA & AMEX at night...everything goes back to the original issue above.

If we repeat that procedure, everything works for the entire day until we settle. So for now the manager comes in the morning and does that process above before the restaurant opens. It's become a pain for her.

Anyone ever heard of this?? Very strange. Thanks in advance for any suggestions & help!

 

[alohaakamai3]

Here's the big question:

You're saying that when a certain terminal is the MASTER, EDC works.

If the manager comes in the next day, and it's not working... is that same terminal the master, or has a different terminal become master after the end of day.

I ask because it could be a configuration issue (in particular, the ibercfg.bat) that could be causing the problem.

Your response to this will give us a starting point.

 

[djazz35]

Hi,

Thank you for your response. I'm not too familiar with Aloha yet. I'm an IT guy but this is my first time working with Aloha POS systems so I'll do my best to answer. I'm learning quickly...

Once they notice it's not working in the morning they shut everything down with the routine above. We also noticed if this one "master" terminal is not yet booted up or turned on, EDC doesn't work at all...even if BOH is up & running with the EDC service and application window and the other 2 stations are up & running ok. Everything else works but the CC shoots out immediately blank or saying not approved. But as soon as we turn on the "master" terminal then EDC CC processing works.

I thought the BOH server was supposed to manage everything? I looked around on some other threads and noticed something about a SPOOLING file might be stuck?

I'll be taking a ride to the restaurant tomorrow so I'll get some definite answers when I poke around in the system. I'll see what the "ibercfg.bat" lists as well. I'm starting to get familiar with how it all works and their configuration.

Thanks again

 

[alohaakamai3]

I will over simplify this a little, but it kinda goes like this:


The "master" in Aloha is really nothing more than first computer to see the file server when it boots up. In most standard restaurant installations, ANY computer can be the "master".

The terminals will more or less communicate "through" the master, then to back of office PC.

This is important in your situation because the EDC path in the ibercfg.bat (which is just a batch file that runs either via autoexec or from a short cut in the startup menu) is defined in this file.

So say you have 3 terminals, Term1, Term2, and Term3.

Term1 has the proper path to when the EDC folder lies in the ibercfg in the form of SET EDCPATH=\\alohaboh\bootdr\edc. When this terminal is master (the first terminal to see the back office for whatever reason), then everything runs fine.

However, say for whatever reason-the computers reboot for end of day procedures, and TERM2 becomes the "master". This should not be a problem- but say the ibercfg.bat on Term2 on your system has an EDC path of SET EDCPATH=\\DJAZZ35\bootdrv\edc.

Now you've got a problem, because when this terminal is master, it doesn't have the right directory for EDC. This will usually cause the terminals to automatically spool, as you mentioned(if auto spooling is enabled), and not send them to the back office for true authorizations.

Of course, this is just one of many possible explanations as to what could be happening-but that's where I'd start.

Post your findings, and we'll get it fixed.

 

[rdubrey]

Quick fix if the ibercfg ends up being the problem is just copy the ibercfg from the terminal that works to the rest of the terminals. You will have to edit the file and make sure the SET TERM= variable is set to the correct terminal number but doing it this way is quick and dirty with no chance for typos. That is if one of the terminals has the correct one and that is the problem.

Also you could delete the ibercfg shortcut in startup, delete the Aloha folder, and re-run TERMINSTALL and it should correct things. I think that the fact that one terminal seems to work is a good sign here.

I am thinking if it were a permissions issue you could test that pretty quick by turning off the master terminal and see if the system will come up without that terminal being on. Shares might be messed up.

Rob