Aloha Stored Value GC program requires Enterprise tech to "make it work" on any reinstall 1

[eburks]

Is anyone who uses aloha stored value able to reinstall Aloha on a terminal and have the stored value gift cards work without someone from Aloha Enterprise remoting in and doing their magic waving of hands.

The terminal I replaced yesterday did exactly what I have experienced when we used Aloha Stored Value GC. Aloha runs fine and the VBO program installed itself like usual but Gift Cards would not function till Enterprise support remoted in. The manager who called Enterprise said the phone tech told her it should set itself up after a terminal re-install and it looks like it does but it never works till they do their thing.

It's not a big issue and their support is part of the Gift Card package but it has always meant some time without Card function on any terminal swap or software reinstall.

 

[dauphin2]

I think it used to be something like this, not sure if it's the same procedure or not for newer versions and again I've never actually done this.

1. Stop Aloha on the terminal

2. Make sure variable MASTERCAPABLE=TRUE and not FALSE

3. Run "%IBERDIR%\Aloha\bin\vboinst2.exe"

4. Run "%IBERDIR%\vbo\bin_11.1.03.134\gctool -sellableseries"

"bin_11.1.03.134" being the current version installed. Newer versions of Ecards use "SVTerminalInstall.msi".

 

[AlohaRoss]

Calling Enterprise is a free call. 800 792-5642 option 2, then 1
I have had them do many reinstalls after either replacing FOH or BOH. They usually will handle in less than 4 hours from start of call. You need the key number and have cfc installed so they can remote in. They can provide you a link

AlohaRoss

http://www.needalohahelp.com

 

[eburks]

Thanks, dauphin2 I will try that sometime this week when I reinstall another term and post back

As I said, it is free for Enterpise to remote in and do their thing because it is part of the Aloha GC package. But I do my work between 10pm and 6am and it would be nice to go to sleep knowing all was functioning. It is an imposition on many managers to have them do the final legwork on this and If I have to do it I get woke up early or have to stay up waaay past my usual sleep time. I install terminals using SetupTrm.exe and maybe it doesn't do something other install tools do. I am certain the fix is running a simple gctool command and that one may be it.

 

[sheerdyn]

I believe AlohaRoss meant to say CMC not CFC.

 

[eburks]

Success! For the first time in 8 years I successfully reinstalled a Terminal AND got Aloha Ecard to work after the install with no other intervention. ...TWICE... YMMV but this was the simple procedure.

Make sure variable MASTERCAPABLE=TRUE and not FALSE

The terminal install takes care of adding the VBO software with no problem and always has. Let it do it's thing and have the terminal at the floating logo.

If it is a reinstall you may have more than one version of gctool.exe, on a new install it should be the only copy
on server. In aloha\vbo\folder find the folder with the newest version of gctool.exe and run gctool.exe -reseedterm term4

In my case on an older version the file was in the bin_11.1.03.134 folder

A full path command for this is %iberdir%\vbo\bin_11.1.03.134\gctool.exe -reseedterm term4

Substitute for term4 whatever the terminal is you have installed or reinstalled

My BOH was Windows 7 Pro 32bit and an elevated command prompt was not needed in my situation
You could run this from an elevated command prompt if there was a problem

Open an elevated command prompt (find cmd, right click on it and select run as administrator)
in the command window run %iberdir%\vbo\bin_11.1.03.134\gctool.exe -reseedterm term4
or your equivalent

You shoud see " a reseed of 'term4' has been started "

That was all it took. For good measure you could also stop and start the service on the master terminal a few minutes after you are done (I don't know how long the reseed takes I did not see much packet activity with adapter status 5 minutes later) by going to the master terminal. Gctool is in the same subfolder of VBO on the terminals. Navigate or use proper path syntax to run gctool.exe -stop then run gctool.exe -start