Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Aloha 6.7, redundancy exceeded

Status
Not open for further replies.

AlohaAK

IS-IT--Management
Dec 2, 2014
1
I cannot get the terminals out of redundancy mode. This setup has worked for over a year, no fileserver failure that I am aware of, and my users wouldn't know how to "make fileserver" off the terminals..there are no dated subs on any of the terminals either.

I looked at the downtime.ini, they all show the same master, and the same file server. I can read/write from the terminals to server, and server to terminals. Lana is set to 0 on both.

Ctlsvr is started, but it appears it doesn't properly start front of house. I can start front of house, but it has no effect (terminals come up either way).

Anyone ever seen this, need to get these terminals back up and running!?
 
Are you running as the adminisitrator on the terminal, not a account that has admin privledges?
 
Check the SERVER and TERMSTR environment variables on the terminals and server. SERVER should be set to the fileserver's name, TERMSTR should be the part of the terminals' names before the number, so if they're called TERM1, TERM2, etc., then it's TERM. If they're POS1, POS2, etc., then it's POS. Restart ctlsvr after making any changes on the server (or, ideally, reboot it), and reboot the FOH after any changes there.
 
You have probably either resolved this or shot yourself at this point, but I wanted to post this for future searches:

I had the same issue. The FOH would not let users log in and brought up error "System redundancy limit has been exceeded!..."

The resolution is on each POS displaying redundancy message, that aren’t in redundancy - remove the data (not the registry key itself) from the string called VALUE SHELL on the terminals having the issue.
The key is located at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer

I Edited the string on each POS, and following a reboot, I successfully logged on without the redundancy error displaying.

Again this is ONLY for when the FOH is not in redundancy, but you receive the error message "System redundancy limit has been exceeded! Restore your fileserver to continue or contact your service provider for assistance."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top