Aloha Database Generation error and System Redundancy Error

[qsrsf]

1. When I run my FOH and it connects to my BOH server and I am still getting the Database Generation error, Please upgrade database. (The DEBOUT file says 'Check version error. Could not open DBF Version file').

2. However when I force my FOH to become the file server the database loads fine and I get to the employee ID pad. After I put in the employee ID number I get an error that says 'System Redundancy Limit has been Exceeded, restore your file server to continue'.

 

[AkamaiAloha]

I've seen this error before too, and don't remember exactly what I did to fix it. But I think you hit upon a common thread here, which seems to be that the info on the front of house is (for some reason) not the same as the info you've got on the back of house. That would explain the database upgrade error, and also the fact that your front of house thinks it's been in redundant mode for more than 21 days (I think that's the limit).

A configuration error like this could be difficult to find, and I am not sure what your level of experience with Aloha is--so I won't go into too much detail on possible solutions just yet.

Here's what I would try:

The Aloha (could also be Aloha QS) folder on the front of house should generally have the following directories:

Bin, newbin, data, tmp, recipe, bmp (there can also be EDC or Scripts, but don't worry about those)

Delete everything in ALL of the directories on the FOH, but leave the folder structure in tact.

From the back of house, copy the Iber.exe (again for some reason, I am thinking you're doing QS--could be iberqs.exe)
to the Bin directory.

Make sure the the root drive on the FOH terminal is shared as BOOTDRV, allowing users full control.

Reboot the terminal.

This will do two things: 1) If it updates like it should, this ensures proper Aloha communication parameters between the two systems. 2) It guarantees that the info is pulled directly from the fileserver, as it looks at that very moment.

See what happens when you do that. You could also do this using the Terminal Install utlitiy, if you're familiar with that.


What OS is on the front of house and back of house?

What version of Aloha are you working with?

I really think this is just a simple configuration issue that's causing this to happen.

 

[qsrsf]

Solved it, Turned out to be a simple file permission error on the server, but rather than point you in the right direction Aloha tells you your database is the wrong generation!