Lightning = Need Help Configuring Aloha

[ryot]

Hi,

Let me start by saying thanks to anyone who can take a stab at the errors I'm getting. The system is in redundancy for only 1 more day. Which means that if I can't get this working pronto, we're gonna be using a lot of paper very soon. I'd like to save the trees

A lightning storm fried a computer that housed the Aloha system (even though it was plugged into an APC protector, ugh).

1. Plugging that hard drive into another computer determined that, on the surface, the files were unaffected by the surge.

2. I have attempted to run the alohamgr.exe from the original drive as well as from the local computer's C:\ after copying and pasting the \bootdrv\ directory.

a. I am running Aloha TableService 5.3.29

b. Attempting to run AlohaMgr.exe from c:\bootdrv\aloha\BIN\ gives errors:

"The Aloha POS License Agreement is either missing or corrupt. Please contact Customer Service for assistance."

then

"Failed to register station name, error 0x23"

and

"CtlSvr could not be started. Check to see that it is registered."

3. Aloha Manager > File > Login > enter UN and PW gives:

"Security setup failed. Aloha Manager cannot log users in without a valid path to an Aloha Directory."


4. Attempting to run ctlsvr /regserver from the command prompt gives:

"Iberdir not set"


5. Attempted to run "Register_Iber_65535_65535_65535_65535", a batch file in the \bootdrv\ directory gave the errors:

"Invalid Account Name assumed because of failure to get a SID for this user account. Enter a valid Account Name or select the Local System account."

...and then it brings up a window titled CtlSvr asking me to either "Register Under the Local System Account" or to "Register Under a Specific User Account". Unfortunately, the user and pass I used for a specific user account was not recognized, even with ".\" before it.


After perusing some forum posts and the "SuperSite Technical Manual", I discovered that Aloha likely requires a file called IBERCFG.BAT in \BIN\. I don't know what happened to it, but I remade it.

my ibercfg.bat files looks like:

SET IBERROOT=ALOHA
SET LOCALDIR=C:\BOOTDRV\ALOHA\BIN

Still, problems persists. If ANYONE has ANY insight WHATSOEVER, then I would be very very grateful.


Thanks,
Troy


P.S. Of course, I do not have the installation CD.

 

[coorsman]

1. sounds like your lana number for the aloha NIC card is not set to 0, check the posts for lanacfg.exe or check you computer hard drive for the file.

Run it using

lanacfg showlanapaths

you will see a list of available NIC cards and connections,

to set the NIC card you want to use for Aloha use the following. If the NIC card is set to 3 then:

lanacfg setlananumber 3 0

also the Aloha NIC connection has to be connected for Aloha to register.

You can register as a local user.

 

[ryot]

Sorry it took a while to respond, I had a friend with some experience come down and they were unable to make heads or tails either (outside of calling tech support).

lanacfg showed 3 possible paths: 2 network cards and a firewire. I chose the lana number associated with the correct network card, but still no change.

I also noticed that the ctlsvr service was stopped. Attempted to start it via services.msc and got the error:

"Failed to register station name, error 0x23"

I also recently created a new User named "Alohaboh" and gave it administrative rights because I thought it might be important what user we're using. Alas, no progress.

 

[ryot]

It's also worth noting that I am running Windows XP Pro and that these errors are occurring on my Back-of-House system.

When running ibercfg.bat on the front-of-house terminal, I get the error:

"Failed to register station name error 0xD.

 

[Circle9]

You could try setting up environment variables. I've attached a link to a PDF with the necessary environment variables below.

 

[99GuinnessLover]

If you are getting the License agreement error then you may need to check and be sure that you have bothe the LSE.flg and Aloha.lic files in your Aloha Directory. These are created when you Agree to the License agreement when ALoha is first installed.

If one or the other is not there i have seen this error occur.

You will need an Aloha.lic from the same version as you are currently working from.

 

[ryot]

Thanks for your help everyone!!

It's true that the environment variables needed to be established. The license issue was resolved upon a reinstall.

Now, having gotten pretty far, I'm still having trouble getting the FOH and BOH talking to each other.

I cannot ping the BOH from the FOH terminal (reverse is ok, oddly enough).

I also noticed that I cannot configure Netbios on my BOH server.

When I view the properties of the relevant NIC card, then the advanced tab, I get a message that says that the Windows Management Instrumentation (WMI) may be corrupted.

A quick google search unearthed:

http://www.nucleustechnologies.com/Repair-WMI-Services.php

and

http://windowsxp.mvps.org/repairwmi.htm

but I'm a little nervous about changing registry things. Has anyone else encountered this issue? Do I risk further problems if these tutorials are followed?

 

[schallowetz]

Sounds for me like the Aloha Server has the wrong IP.
Check the Networksettings on Your Server.
my Server was set on 192.168.0.200 255.255.255.0

Robert

 

[coorsman]

fixed it, thanks

 

[3rdgenmr2]

how did you fix it.....please post.

thanks

 

[coorsman]

they called me and i dialed in and did a terminal seup and install. need help?