Changing security key info while open

[alohaakamai3]

Client has added terminals to their existing Aloha license and we have new key codes.

However, they have been open for business today, and I seem to remember something happening some years ago about that info being stored somewhere in the current trans.log for the day, and Aloha not liking it when the terms were rebooted. Does anyone know if changing the numbers cause a problem?

NOTE: This isn't a software upgrade of any kind, so there is no concern of that nature. Simply changing the key numbers here.

Thanks!

 

[jjr2144]

I remember this doing once during store hours and it took 2 hours to figure out the code received did not work.....I recommend doing after hours to prevent the store not to function while open

 

[alohaakamai3]

Thanks for the reply.

Correct, I had a similar experience, but since it's not something most people do too often (add licenses), and I have seen so many other types of problems over the years, they all jumble together

After I posted this, I noticed the restaurant was completely dead, so I backed up the data directory and gave it shot. At first I got floating logos on the two upstairs computers, but with a "Master down" message. And eventually, it turned into a "Wrong Security" on all the computers, as it's reading the transaction log. Pretty much just as I remembered it.

Fortunately, I was prepared and had the system up and going in a few minutes, even though it was still dead business-wise.

Tomorrow is another day.

 

[posrescue]

A manual grind with the swith to force a version upgrade is your dandy in this instance.