Aloha Redundancy Limit Exceeded

[scottm52]

Sigh, the ongoing saga continues......

Aloha System has been in redundancy (out of town system) for 21 days, now hitting exceeded limits and I can't be there til Late today to build out
a replacement server.

Anyone know how to exceed this limit? Setting? File Marker?

THX

 

[SirTekaLot]

Just a thought; have someone take a thumb drive and move over the previous days folders to the thumb drive and reboot.

 

[eburks]

Has anyone got any advice on this. It would be nice to know.

 

[coorsman]

change the date back a few days on the terminal will grant more time.
Other than that you would need to install the hasp drivers and attach the software key.


Cheers,
Coorsman

 

[scottm52]

The rest of the story......

The server (after upgrading) simply refused to talk FOH-->BOH (or the other way around). I could see and interact, copy/edit, anything on the entire network. But Aloha just didn't like it.

Finally just brought in a swapout server and reloaded Aloha from scratch and all went swimmingly well. Something in the upgrade seems to have "torqued" with the registry (I think). But, this was the last in a series of big upgrades so all is well now.

FYI, I figured out I could simply change the date back on the Master and the TERMS all came back up while I put the new server in. It recovered quite nicely.