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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Aloha TS Version 5.2.8.224 Software

Status
Not open for further replies.

justadoode

IS-IT--Management
Jan 13, 2007
102
US
I have Aloha TS Version 5.2.8.224 and my system is having many troubles plus the FILE server is as old as a rubik's cube. I would like to get a new one and re-install my Aloha and although I have the key, I do not have the software disc and it's not on the Fileserver, either. I contacted my local reseller but she took the opportunity to try and sell me everything under the sun. Once she realized that I was not wanting to buy anything except the software, she said that she could not sell me such an old version due to PCI compliance laws. I know those laws mostly apply to level 1 merchants, which I'm not and I thoroughly understand the risks I face being on an older version of Aloha. With that being said, can anyone tell me where I could purchase or acquire install software for my version of Aloha? I could really use this help. Thank you in advance.
 
The CD usually just simplifies the install process by creating the directories, file sharing, registering the files/services, and setting the environmental variables. All of this can be done without the CD if you utilize your existing files. The exception would be you might need software located on the CD such as MS JET, Hasp Drivers, etc..
 
I have had the guy that builds my server GHOST my current drive and everything worked just fine..no need for CD
 
OK.. then maybe I'm barking up the wrong tree.. I have an issue that I posted on here where my tickets are being duplicated each time a tab is originated. In addition, my end of day won't run. Even if I click on force end of day or try to run it manually, it will not run and there's no setting that I can find to stop the tabs from being duplicated. I asked around and was told that I more than likely needed the install discs. I don't know if any of you POS gurus can provide any insight into this?
 
You bought and paid for the Aloha software, and the OS that is installed on any computers. You have the right to request, and you should get the originals CD's for both. This is simple. They did not provide what you paid for. PCI compliance is a non issue. Ask for it again nicely, if they refuse have your lawyer send them a letter. Can't begin to tell you how end users don't insist on the software media. Let this be a lesson.
 
Excellent point. I was thinking the same thing, but had not said it here.
 
Hard to say what's causing duplicate tabs, or EOD problems, but I wouldn't point so quickly to the lack of an install CD.

What happens when you try to run EOD? Have you any debouts from the master terminal?
 
Is the site a 24 hour operation, if so, delete the trans.log in data after all checks are closed and cashouts are closed.

Sounds like a corrupt dbase file.

1. Delete all *.cdx and *.tdx files in
Aloha\data and Aloha\newdata folders
Best if done in DOS
Press the Windows key + R and type in CMD or go to DOS
change dir to aloha\data
type in del .cdx and press enter

change dir to aloha\newdata
type in del .cdx and press enter
type in del .tdx and press enter
type in exit
2. open aloha manager in windows and do a refresh to the terminals.

(this can be done any time. Ctl service will rebuild the indexes and refreshing them will update them to the terminals.


 
Alternatively, copy and paste the text below into a batch file. Name it DBConfig.bat or reindex.bat or whatever you want as long as it ends in .bat. Double click to run.



REM This batch file runs dbconfig silently for Newdata and Data.
REM You can run it from anywhere and you will see four dos windows open and close.

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /DBFONLY /DEBUG /FORCEUPGRADE /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA
START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CDX /DEBUG /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA
START /WAIT %IBERDIR%\BIN\DBUP3.EXE /DBFONLY /DEBUG /FORCEUPGRADE /DBFINPUT %IBERDIR%\DATA /DBFOUTPUT %IBERDIR%\DATA
START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CDX /DEBUG /DBFINPUT %IBERDIR%\DATA /DBFOUTPUT %IBERDIR%\DATA

 
If EOD isn't running, is only 1 pos terminal stating it's a master or do you have multiple terminals stating they are master?

EOD is initiated by the Master terminal. If the Backoffice computer isn't communicating with the master terminal, the master terminal will do it's own limited eod.

Before we go down the path that EOD isn't running, do you have an EOD event configured?

The debout from the Master terminal will help tell us what is going on (Or not going on).


Unfortunately, the install discs won't help you here, and they aren't needed if you want to move the POS installation to another computer. It's very easy to do without the CD -probably easier. We can talk about this later.
 
I got the EOD to start running. Now all I have to conquer is the duplicate tabs. Any ideas?
 
I don't recall reading your post about tabs... I am guessing you are using Aloha tableservice. Can you walk me through the issue?
 
Yes. Basically, when a bartender takes a customer's credit card and swipes it to open a new tab, the Aloha system AUTOMATICALLY creates two tabs. One tab has some sort of 6 digit number assigned, along with the ordered drinks and a preauthorization for the credit card and the other tab has the customer's name, no preauthorization and the same drinks/ items. I don't know how to get it to stop doing this and I have looked at EVERYTHING I can think of. It makes it BRUTAL when we get busy. This is a very high volume place and we have a gazillion Aloha tickets opened cause they are duplicates. I've looked in every option under system settings, access levels and job codes and cannot figure out how to stop this. Thanks!
 
Never heard of the problem, but will offer a couple of comments with 10 years experience with this software.

First of which, Alohatech2 is correct, the situations in which I have seen just "re-installing aloha" make problems like this go away is on the rare side. *Sometimes* is does work, but most of the times it doesn't.

Bigblok is also correct, you don't technically need the CD for anything once you have the BIN executables. It can be a little messy to do it this way and you may have to tinker with it, but basically all the CD is doing is registering a bunch of files and services, and everything on the server is present to do that, as is.

Imaging it will sometimes work, but you will mostly definitely have to tinker with it, reload drivers, etc, since your hardware will likely be different, and in a lot of cases, it simply won't boot at all.
 
Yeah, I have a problem with aloha too. I did a fresh install of the 5.3.9 version on Win 2003. And now I can't login to Aloha Manager TS - it asks for a login and password, but I never set one up! Any suggestions? I've already tried the one that Radiant gave me, user = Aloha, pwrd = hello.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top