Aloha crashes down to windows desktop

[USofAScott]

I have a system that is only 60 days since install.

It was up and running for about 5 weeks. then the Local NCR office upgrade to New Aloha Manager in preperation for Aloha Kitchen and Aloha Enterprise installed Mobile Pay and Insight. We also have Aloha Take Out installed.

Since they upgraded to NAM, the system is unstable. Randomly, terminals will throw a windows error box that says Aloha Table Service has stopped working. if you say ok, it drops to a windows desktop.

The local office is stumped. they removed (so they say Aloha Take out and Mobile Pay). However, on the terminals there is still debouts from ATG (a component of Take Out and Mobile Pay) so I dont think they really know how to remove.

Was wondering if anyone has seen this before.

Here is what i was going to try next. Take terminal down to windows. Delete the entire Bootdrv folder and then run WinInst61 again and reinstall the terminals. Does this sound like a plan?

Anyone, anyone?

 

[techinaz]

Do you have a debout you could post?

TechInAZ

 

[PosTech72]

I would def do just that. ATG is built into the new version of NAM. There are a lot of differences in the new software that is coming out.

Some quick questions:
What versions of POS, NAM, and ATO are you using?

I recently went to Techfest in Dallas with NCR and there are some major changes coming into play.

Uninstall and re-install NAM (the latest version)

reimport your data.

path to your terminals from your fileserver and rename the bootdrv to like oldbootdrv and re-do your term installs.

Install the latest version of ATO on the server first as a server install and then each terminal as terminal install.
*Helpful tips for ATO install*
set environmental variables on FOH terms and BOH fileserver
rotate or set site key with data protection tool on BOH fileserver
Run takeout setup helper on BOH Fileserver
Make sure you enable FOH COM for order confirmation and make sure that you enter the following under
"External Integrated Software Component under Maint>Business>Store>System Tab>Interfaces section

Radiant.Hospitality.AlohaToGo.Intercept.AlohaToGoIntercept

This is the equivilant of making the store active or not active in NAM as you would use a arrow to move it left or right in CFC.

Also what hardware are you using?

There are a lot of factors as to why your system can be acting up.
I will check back with reply.

I set up ATO, AGM, Menulink, CFC, NAM, Aloha Kitchen, Handhelds as well as program databases, train customers employees and do live support for new store openings. Feel free to ask me questions.

 

[USofAScott]

I went thru and did the terminal reinstalls last night and it is now stable.

I do not have NAM, ATO, Mobile or Kitchen running right now. Want to make sure that all is stable before adding anything to the mix.

running iber 6.7.60
NAM is 15.2.0.4816
ATO is currently not installed

 

[PosTech72]

If you are going to integrate ATO in the future you will need to install 13.1

I have found that 6.7.45 and above with ATO 13.1 is very stable.

Let me know if you need any setup help with that piece when it comes time.