Spooling a couple of times a day, everyday

[MitchMann]

I am creating a forum to see if anyone has a solution to my on-going issue. We are a Aloha Reseller and we have a client who goes into spooling a couple of times a day, everyday. We monitor their internet closely and it never goes down. They are on EDC Version 7.0.9.4 which is the same version that most of our clients use and they do not have near as many issues. They are not behind any firewall and they use AVG for Anti-Virus.

Suggestions would be greatly appreciated!

Thanks,
Mitch

 

[kposnet]

What's the platform?

 

[MisterAloha]

Have you inspected debout.edc in %iberdir%\tmp to see what is happening with the software at the time of the outage? When in doubt, debout. That's my motto!

 

[360fish]

Start with the debout.edc as MisterAloha said. Here is some rather generic info on spooling issues but more information is needed for your specific problem.

In my experience spooling problems are related to network connectivity (DHCP media sense, bad cabling, bad switches, too many switches, bad routing, etc.) or login account info (edc services not running under the same account the FOH is).

Here is some info from Alo/Rad/NCR on Causes of EDC spooling
1) The EDC file server is off the network. The FOH automatically enters spooling mode when this occurs. Spooling starts the first time the master terminal unsuccessfully attempts to poll the EDC file server, which occurs approximately every 15 seconds.

2) EDC is not started on the EDC server. The FOH will automatically enter spooling mode if EDC does not respond. The timeout for this is set by the WAITFOREDCRENAME=n entry in the ALOHA.INI file, where n is the number of seconds to wait. It is advisable to not set this time lower than 30 seconds. The default value is 30.

3) You can configure EDC Server to ping a user configured internet IP address on a regular basis in order to assure connectivity for internet-based authorizations. If EDC Server does not receive a response within a configurable number of seconds, then EDC Server will disable POS processing (this will be seen on the EDC user interface), which will, in turn, leave .REQ files from the FOH unanswered. The unanswered .REQ files will ultimately cause the FOH to start spooling files. EDC Server will continue to ping the address, and once it receives a response, it will re-enable POS processing, which will process any spooled credit card files on the terminals and any new requests.

​