We have several Aloha servers / BOH machines which have our software running on them.
In many cases, during the Aloha EOD process, the services are being stopped (we can see this in the logs of the application), and then about 6 or 8 minutes later, it starts up one of our services.
The other service, which has an EXE named "WServiceAloha", and the service is named "TFAloha", is not started back up.
Would the EOD being stopping our services for some reason? Any ideas what would be stopping the software?
Doesn't seem to be an issue on all Aloha systems, and no other POS seems to have this issue with killing our software.
Thanks!
--
Anthony
In many cases, during the Aloha EOD process, the services are being stopped (we can see this in the logs of the application), and then about 6 or 8 minutes later, it starts up one of our services.
The other service, which has an EXE named "WServiceAloha", and the service is named "TFAloha", is not started back up.
Would the EOD being stopping our services for some reason? Any ideas what would be stopping the software?
Doesn't seem to be an issue on all Aloha systems, and no other POS seems to have this issue with killing our software.
Thanks!
--
Anthony