FOH EDC System Error - BOH able to process

[pkuy930]

I need some help.

I'm running ALOHA TS v5.3.31 with the corresponding EDC.

Currently all FOH terminals cannot process credit card payments as a "System Error" but I can run card on the BOH server using the authorize function.

This just suddenly happened, no changes happened to the BOH server or the FOH terminals. I have restarded EDC, ALOHA TS, the server, the terminals, the router/modem, switch -- EVERYTHING!

Nothing has worked.

HELP! And thank you.

 

[dauphin2]

Check for a file called "SPOOLING" in the Aloha\EDC folder on the master terminal and delete it.

 

[pkuy930]

I could not find a "spooling file".

However, this only happens when terminal 1 goes into Master. Is there a way to prevent that? Or better yet, fix it?

Thanks in advanced again.

 

[dauphin2]

Sounds like you have a permissions issue then. Either with TERM1 accessing the BOOTDRV share on your server or an issue with the user EDCSVR is logging in with on the server. You could edit the ibercfg.bat file on TERM1 and change MASTERCAPABLE and SERVERCAPABLE to FALSE instead of TRUE so that it won't become master as a temporary bandaid.

 

[360fish]

to follow up on what Dauphin2 said this does sound like a permissions error - usually it's caused by the logon for the EDC service not matching the logon for the front of house terminal.

Check your EDC service logon - start: run: type 'services.msc': double click the EDC service: logon tab. ensure the user name and password used by the service matches the user name and password used by the FOH to log into windows and the user name and password used to logon ctrsvr (not sure the exact name, it's the main aloha service).

If these are not synced you have problems recovering from spooldown.

 

[pkuy930]

...aaaaand it did it again.

I did find a spooling file on Term1 this time and deleted that.

I went to set the MASTERCAPABLE and SERVICECABLE to FALSE and I get an error message reading:
"There is another terminal on the network with the same terminal number or there is aother instance of Ctlsvr.exe on the network broadcasting the same TERMSTR."

?

360fish,
How would I make sure they are the same password. The Log On for EdcSvr and Ctlsvr have is set to to "Local System account - Allow service to interact with desktop"

I really do appreciate all the help as my call to TexasPOS has yet to be returned -- since last Thursday.

 

[360fish]

OK 1) same termstr - you need to check the ibercfg.bat file on each FOH term and see if the termstr= and term= values match the FOH computer name. For example, your FOH term2 should have a computer name of "term2" and in the ibercfg.bat it should say termstr=term and term=2. this is just from memeory and i'm multitasking but check here for a decent quick-start style overview or search these forums. coorsman and dauphin are good users to search for posts.

http://www.scribd.com/doc/54812290/Aloha-Troubleshooting-and-Support

2) the FOH terms must log in to windows with a user account - the default is user: aloha pass: hello but hopefully they're not still using that. The aloha server should have a user account with password identical to the FOH and EDC and Ctrsvr services should log on using that user name and password.

That's a general overview I can't write a step-by-step for you now.

 

[pkuy930]

Thank you for that link.

It took me a couple days to read and understand it, but that gave me a lot of insight into the system.

I'm not really sure what I did, but whatever it was worked and the issue has yet to come back.

Thanks again!