File Server Install Aloha

[chuckymafia]

So I am a POS Tech in need of help. I am used to a FS running shared data and then the other machines communicate to the FS. Installs are pretty easy and straight forward.
I have done OnePOS, PixelPoint, Digital Dinning and today I am with Aloha. I have the CD Image that I found here. I install TS and then I try and run Aloha Manager and BAM. Error about something with the station not set. So I read on here to to Lanacfg. I did that to fix this error and no help. I do have two NIC Cards so not sure if that matters. Secondly I get a CTRL Srv or Srvr error afterwards.

My question is : Can anyone please tell me or guide me on an install? I have worked with Aloha before, Helpdesk and this is the first time I attempt an Install and for what it seems. It is not as other POS Systems as this current machine has a user account for every terminal it seems.
I know how to move and modify the files for NEWdata to Data and so on. Yet I am stuck in the Install procedure as It asks me a lot of questions and I just hit yes to what I deemed necessary. Any help will be appreciated and I can always help out since I have Images and files for those Mentioned POS Programs and some Images for Radiant Registers. You help me, I help you.

PS: I did call my local dealer and offered them money to help me. It has been a Month. No reply. I don't really need this done as all I want to do is move to an SSD Drive. My current Raid configuration is too slow and I also want to learn how to do this for Fun.

Thanks

 

[SirTekaLot]

http://www.tek-tips.com/faqs.cfm?fid=7378

- lanacfg

http://www.tek-tips.com/faqs.cfm?fid=7418

- if installing on to Windows 7

If you didn't specify a username and password (the one you log in with) for the Ctrl and EDC services during the install; do so.

If you are not correctly specifying the correct NIC in lanacfg you will have issues.

Look in the NEWDATA and Data folders; locate the aloha.ini; make sure the your SEC keys are there

sec1=
sec2=
sec3=
sec4=
sec5=
sec6=

Just a few things to check

Zach

 

[chuckymafia]

Well today was a new Day and I went ahead and did an Entire Windows Reload and just ran the CD with defaults. Everything works now. Thanks for the tip on the User name and password thing, that may have been why it failed the first time as we did not have a password set. Yet I found an error in the debout prior to installing the new OS.

LoadIberStrings() - WARNING: Application version = 6.4.26.***, IberStr.dll version = pre 5.2.1.x.
Version difference may cause problems."

So I did an install and used a CD and even with a new install. I get the following :

LoadIberStrings() - WARNING: Application version = 6.4.39.2198, IberStr.dll version = pre 5.2.1.x.
Version difference may cause problems."

Why would a brand NEW Install cause this error ? I am using however an old DBF setup of files. Would that still cause this error ? I didn't think that this would have anything to do with DBF Files. Anyone know if this is a REAL error or just a Programmer issue that will not affect anything ?

I ask this because my customer says that their cash totals do not equal what Aloha Shows. Aloha shows less cash than what they end up with.

This is of course theoretical as I didn't see anything else in the bedout and of course ATT came in and MOVED my Cables Around.

Any help is appreciated. Yet so far. I have no issues with the Install. Thanks for the help

 

[SirTekaLot]

I see that warning all the time; It hasn't ever affected me. Someone like Coorsman might know better than me on that. As far as the cash just keep an eye out; 9 times out of 10 it's operator error. Also, changing things before running EOD has a way of screwing things up. Make your changes before anyone logs in; then leave it alone.

Zach

 

[eburks]

I can echo what SirTekaLot said about the iberstr.dll error; ignor it. I get it at my stores and have for years. As far as the cash goes make sure that in Tender Maintenance any payments that are not cash types are set properly.. ie. tracking, affects deposit, The closing procedure the store has developed for accounting will determine exactly how you should expect to set these. In general if it is not cash or check it should not affect deposit. It is even possible that they are set correctly but the accounting being used for closing is faulty..... or "different".

 

[SirTekaLot]

Totally forgot about that; good call!