Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

justadoode (IS/IT--Management) (OP)
13 Jan 07 16:10
POS GURUS: I have built a new server for my restaurant and installed the Aloha POS by using the discs from my local dealer. Everything seemed to have gone well, except whenever I reboot or I try to access the Aloha Manager, I receive "CLTSVR Security key not found" error message. I have read all of your posts and have tried to follow all of your instructions to the letter. All of the old info and profiles and everything have come over, but I STILL get that error message and am VERY frustrated. Can anyone PLEASE advise?  Thank you in advance.
justadoode (IS/IT--Management) (OP)
14 Jan 07 11:39
Oh, another bit of info is the Aloha POS system at the restaurant is 5.045 and the OS on the new server is XP. I read on here that they are not compatible and just wanted to verify this really is the case.  The key is installed on the back of the pc and is not fried, so I know that's not the issue.  I just want to make triple sure before I format the server and install Windows 2000 Professional. Thanks again.
DTSMAN (TechnicalUser)
14 Jan 07 16:18
Is it a parallel key. Make sure the port is enabled in bios. You may also need to download an updated HASP driver for the key. Make sure the user that cltsvr is register under has administrative privelages.

Bo  

Remember,
If the women don't find you handsome,
they should at least find you handy.
   (Red Green)

bigblok403 (TechnicalUser)
15 Jan 07 8:48
I also suggest reinstalling new HASP drivers. Windows XP and Aloha 5.0 work just fine together if it is setup correctly.
justadoode (IS/IT--Management) (OP)
15 Jan 07 22:22
Well, I researched all of the postings and saw the following-
"Here's your issue:

Windows Me and Windows 2000 require Aloha application software versions 5.017 or higher.

Windows XP requires Aloha application software versions 5.211 or higher.

Windows Server 2003 requires Aloha application software
versions 5.2.7.105 and higher."

So I totally formatted and installed W2K Pro instead of XP, which I would have MUCH rather have preferred to have XP.  Also, what is a HASP driver or HASP? I have no idea what that is or what to do with it or how to update install HASP drivers.  Any ideas?
Helpful Member!  alohaakamai3 (IS/IT--Management)
16 Jan 07 3:28
You're going through what I learned a long time ago through trial and error. Aloha version of 5.0x and XP do not always play nice. Some 5.0x keys I've gotten work with XP, and some I haven't. I can't find any rhyme or reason to it. I think it may have something to do with the hardware in key itself (I've probably tried it 10 different times with 10 different keys).

As it stands right now, we more or less have a standing policy that customers who have 5.0x software will get Windows 2000 when it comes time to replace their server (and since most of them haven't upgraded the Aloha version, they're generally don't care what OS is on there, as long it works). Like you, I prefered to use XP, mainly because it's easier to install in terms of drivers. The reality is that there is not much difference functionally once the server is built, whether it's XP or 2k. In fact, I sort of like the fact that 2k is less user friendly, because there is less of chance of user trying to install iPod software, use MSN Messenger, or connect their handheld device.

I know most Aloha dealers preach the same thing I do-it's a file server for your POS system, so let it do just that. If you want to run other 3rd party apps, better to get a Dell for $500 than take a chance on mucking up a machine that's central to your business. So with that logic in mind, it really doesn't matter what OS is on your PC--2k will be just fine.

If you're really a glutton for punishment, you can download the Alladin HASP drivers the other people metioned in the post. Just google "Alladin Hasp driver download" and you'll get results for such links. Since you already have the OS installed, it's worth a shot (it did work for me once!)

Hope this helps. Best of luck!
justadoode (IS/IT--Management) (OP)
16 Jan 07 17:19
Thank you all for the info, it was very helpful. The back of house came up with no more error messages once I switched the OS to 2000 Pro. However, now I have a new issue. All of the terminals up front sit on "looking for file server". In the back, I have finally broken down and copied EVERYTHING under the Aloha folder from the old server to the new one to see if this will fix the problem. I'm now just attempting to make the new server identical to the old one. I have tried to unregister and register the Iber_52844.bat to see if this helps anything, but no good.  I originally followed the instructions I found on this site posted by RokStar. This is what was said:
Install the Aloha CD on the new PC, with services.(check)
Using the number of terminals correctly, etc.(check)
Copy from the old HDD only these folders:
All Dated Subs (for your history)
BMP
NEWDATA
PROFILES (all Check)

into the new Aloha Directory on the New PC.

Run the database upgrade utility (\aloha\bin\dbconfig.exe)
(I did this, but got a couple of error messages, like couldn't connect with sql, then did it again and it said it didn't need to be upgraded)
Refresh data.

Now you also need to make sure that your environment variables are the same as they were on the old PC. (I'm assuming they mean in the Aloha.ini file? That's where I checked)
Especially:
NUMTERMS
SERVER
IBERROOT
IBERDIR
TERMSTR

They should also match the variables that each terminal is using in their IBERCFG.BAT files. (What is meant by 'they'?)

The server should also use the same Computer Name as the old Computer.(Check) This can involve some tricks if you are copying the files from the old PC over a network. (not recommended for a noob.)

Also, blok's suggestions:
Make sure it is the same hard drive letter, (check) path, etc. You will need to register services (what services, how do I register and which files?)and certain files. Also need to share drive as BOOTDRV with full permissions.(check)
But you don't need to register dll's again, because the CD load will do that.

So I have a couple of things that I didn't understand 100% but I feel I'm very close to it. Can anyone spare a little time and help me out, please?!! I really need to get this done.  Thanks!!
alohaakamai3 (IS/IT--Management)
16 Jan 07 17:39


1) Make sure all your computers can communicate in windows (terminals can see each other and the back of house, which means protocols are properly setup, etc).

2) Make sure the front of house computers can actually access the aloha directory on the back of house in windows. (in other words, make they have permission to navigate to this directoy).

3) Make sure the front of house computers are logging on with an account name and password (usually blank), that is the same as an account with the same name and password on the back of house (I would give it admin privillages for now, just to rule out permission issues).

4) I've seen goofy situations with windows xp on FOH and certain back office configurations where if a drive was not mapped in windows to the alohaboh\bootdrv, the stations would not come up. Just to rule it out, I would make sure there is a drive letter mapped to this directory.

If all of this still fails to yield anything, there is a good chance it's related to the lana #, which you'll need a utility to change. I won't go into all of that now, since the other stuff is easy enough to check.

Try that firsty, and then post your results.
justadoode (IS/IT--Management) (OP)
16 Jan 07 17:47
Wait, let me get this right... I created the new computer identical to the old one except that instead of having the same password, I just left it blank. You think that might be it? You think to access the back of house, the front pc's are wanting to use the old username and password? That might make sense. Let me give that a real quick shot. I will make the password for this computer the same as the old one.  OH, one other thing real quick, I have installed aloha, but the menu's are no longer accessible? When I open the Aloha Manager, under maintenence, I choose menu and the options for Menu's and Submenus is not there. I can see all of the other stuff, but not that. Any ideas?
alohaakamai3 (IS/IT--Management)
16 Jan 07 18:15
Without a doubt, you're terminals need to have permission to be access the that Aloha directory on the back of house. I have seen condtions where the GUEST account expired on the back of house after 30 days, and that's what the terminals happened to be logging on as. In effect, it denied them access, even though the bootdrv was shared with full access.

So, definitely-- even though it still logic seems like it should work anway, make sure there is an account on the back with the same user name and password the FOH terminals are using, and give it admin access for now.

Everything I've listed here is related to networking and permissions. I can pretty much guarantee you that your problem is somehow related to that.

As far as the menu disappearing thing, I haven't seen that before. I would try to get the FOH to come up first (as long as you're not getting error messages on the back), and that might shed some light your other problems.
justadoode (IS/IT--Management) (OP)
16 Jan 07 19:19
Thank you so much! You were 1,000,000% right. It was a permissions issue that was cleared with the correct set up. All that I have left is just trying to find out why I no longer have the option to view menus in the Aloha manager in the Back of the house. I'm worried that if I try to reinstall, I might mess something up.
alohaakamai3 (IS/IT--Management)
16 Jan 07 20:03
Glad to hear it!

Reinstalling it shouldn't mess anything up, really. I've seen on rare occassions where it *could* alter the lana number, but I haven't seen this in a while. And besides, even if it does create another problem, the systems not going to be much use to you if you cant get to the Menu section. You're going to have to fix it at some point.

Try logging in the BOH as a different user (that was manager or general manager) under the old server, and see if you have the same problem.

Are your front of house terminals up and running?

justadoode (IS/IT--Management) (OP)
16 Jan 07 22:21
The FOH Terminals are up and running, although I haven't been able to figure out the permissions issue on the ONE terminal with Windows 95. The other 5 terminals are all on Windows 2000 Pro and all can access the BOH.  Since it started getting busy, I reconnected the old server and the system came up as normal. I have to figure out why the menus option doesn't come up on the new server and why the permissions don't allow the one Windows 95 terminal to access Aloha when the new server is hooked up. I would install 2000 on that terminal, but it's old and I'm not sure if the terminal could handle 2000 pro. Tomorrow, I guess I will try re-installing Aloha again and see if the menus option comes up, unless you have a better suggestion. You're much better at this than me. Also, any suggestions on the permissions issue between 2000pro and 95? Thanks so much!
alohaakamai3 (IS/IT--Management)
16 Jan 07 23:37
The only other thing I could think of is that some screwy thing got changed in Aloha's BOH security settings that denied the account your using the ability to do anything to the Menu section (thats why I suggested logging in with another users account or by using the Super User password). It's a long shot (and a random guess), but I couldnt explain how this might have happened, and have not seen anything like that.

If that doesn't yield anything, I'd reinstall Aloha.

As far as the Win95 thing is concerned, again check all the same stuff (that it's logging on as the same user name and password, along with the other stuff I've mentioned). Also, for the default gateway on the win95 machine, put in the server's IP address.

Lastly, go into windows on that machine and try to access the BOH bootdrv\aloha directory, and let us know what happens.
justadoode (IS/IT--Management) (OP)
19 Jan 07 13:04
Well I logged in with several different accounts and even re-installed Aloha. No dice. I cannot access the menus and submenus from the Back of the House. I asked the local dealer for some assistance and they said they'd have to have me bring the server in and re-install Aloha and that would cost me $650. (plus tax). What a rip off. I'm not sure how this is controlled or how to access it. With the Super User and password, I've logged in the back of house and set all of the security levels to allow me everything and I STILL can't see the menus and submenus. If I take a look at a specific item, I can see the modifier screen from the option to change modifiers, so I know the menus are in there somewhere, but I can't toggle them on. Can anyone help with this? It's the ONLY thing not working. Argh.

Thanks!
bigblok403 (TechnicalUser)
19 Jan 07 15:34
Sounds like your database is corrupt somewhere. Doing a database upgrade (DBConfig.exe in the BIN folder) or Rebuild the Index files (delete .tdx and .cdx files in NEWDATA folder, start Aloha Manager to rebuild) might help.
justadoode (IS/IT--Management) (OP)
19 Jan 07 16:01
when running the database upgrade, I get dbf file upgrade not required, then I get the error message "data source does not exist....run with create db parameter".  I then deleted *.tdx and *.cdx and tried to run aloha manager and it won't come up at all.  I was supposed to delete all of those files right?
bigblok403 (TechnicalUser)
19 Jan 07 16:22
It sounds like your parameters are wrong somewhere. Make sure these are checked DBF files only, Attended, Debug, Force version upgrade, and the directories for input/output should be  example C:\aloha\NEWDATA.
.tdx and .cdx files are only index files which should be recreated when Aloha Manager is started, if not then maybe your environmental variables are incorrect on your server.
bigblok403 (TechnicalUser)
19 Jan 07 16:28
I saw in one of your other posts you were getting SQL errors when doing a dbf upgrade. Is the old database built on SQL. If not then make sure Create DBF files is NOT checked.
justadoode (IS/IT--Management) (OP)
19 Jan 07 16:34
I checked the options you said and the upgrade went off with no error messages. I started the aloha manager and still no menus or submenus. I went back into DOS and deleted *.cdx and *.tdx out of the c:\aloha\newdata directory. I restarted the computer and ran the aloha manager again and still no menu or submenu. *sigh. Any more thoughts? I'm willing to try anything right about now.
bigblok403 (TechnicalUser)
19 Jan 07 16:37
Is they option for menus and submenus greyed out, or just not available to select?
justadoode (IS/IT--Management) (OP)
19 Jan 07 16:47
It's not available to select at all.  I had copied all of the submenus under Aloha from my old server (which is still up and running) and on the old server, I can see the menus and sub menus but not on the new server. I just don't get it and I'm about to just bring out a hammer and a bottle of Tequila.
bigblok403 (TechnicalUser)
19 Jan 07 16:50
Found this Document ->

If ALOHAMGR.EXE (Aloha Manager) is missing drop-down menus or drop-down menu options, verify that the CTL4X.DLL, MNT4X.DLL, and USERTOOL.DLL applications are registered.  The easiest way to verify successful registration is to manually register them, and verify that they return a successful response.  Refer to document AKBID1019 for more information on manually registering and un-registering the ALOHA┬« application software.

  The following .DLL files affect the following drop-down menus:

CTL4X.DLL - Functions, Reports, Utilities
MNT4X.DLL - Maintenance
USERTOOL.DLL - Tools

Register them one by one by copying the line in the Iber_52844.bat file and pasting them in dos. Make sure they register ok.
bigblok403 (TechnicalUser)
19 Jan 07 16:54
You could also completely delete the security level .dbf files. It will just create a new blank ones when you start Aloha Manager up.
justadoode (IS/IT--Management) (OP)
20 Jan 07 11:36
I have a real quick question. I copied those lines out of the 'register_iber_52844.bat' file and pasted them in dos and hit enter and nothing happened, except it it returned back to the c prompt. Should something have confirmed a succesful register?  I called the local dealer and asked them if we could work out a deal to get the menus toggled on. The owner said sho would still charge me the full $650 and to add insult to injury, she said "That's what you get for trying to build your own server."  I cannot believe the audacity this woman has for me just trying to save a total of $1600 plus tax to build and configure my own server. Anyway, should I have gotten something telling me I successfully registered these .dll's?
justadoode (IS/IT--Management) (OP)
20 Jan 07 12:06
I don't know, I'm getting discouraged. After registering those three dll's and rebooting countless times, the Alohamgr program just stalls now. I start it and it asks for my user ID and password. I put in the super user values and it just stays locked there. I check the task manager and it says not responding. I have rebooted and still no fix. By the way, also, where do I find the security .dbf files that you suggested I delete? I don't know if they are under the newdata folder and I don't know the names.  Thank you again.
bigblok403 (TechnicalUser)
22 Jan 07 8:28
Start Aloha Manager and paste the last couple paragraphs from these 2 files here - DEBOUT.TXT and DEBOUT.svr. They are located in Aloha\TMP. These are 2 files that show info about Aloha Manager and Control Server problems.
alohaakamai3 (IS/IT--Management)
22 Jan 07 12:02
Also, one cool feature of Aloha is that each day of sales history is like a "snap shot" of that particular day. So, if you think you have data base corruption, you can always go back a few days before your problems started, and post of the contents of that day into your Data/Newdata directories. (a few files you don't want to transfer for over, mainly the trans.log is the only one you need to worry about)

I'd probably go this route before I'd start removing individual files within the databse and trying to get it to work. Go back to when it DID work, and try using that data.

Just my humble opinion.
justadoode (IS/IT--Management) (OP)
22 Jan 07 12:04
I see.  I brought the computer home to fix it, but I guess since I don't have the security key attached to the back, it creates problems. Here's what I have:
DEBOUT.svr
Jan 20, 12:06:34 CTLSVR: Started CtlServiceThread... version 5.045
Jan 20, 12:06:34 CTLSVR 5.045 is running on workstation ALOHABOH1
Jan 20, 12:06:34 CTLSVR: IBERDIR is C:\Aloha
Jan 20, 12:06:34 CTLSVR: Is NOT running in SQLMODE.
Jan 20, 12:06:34 CTLSVR: bRobust = TRUE
Jan 20, 12:06:56 CTLSVR: Security key not found
Jan 20, 12:12:33 CTLSVR: Start background processing...
Jan 20, 12:12:33
Jan 20, 12:12:33 CTLSVR: CtlServiceThread Terminated.

DEBOUT.TXT
Jan 20, 11:09:37  ............................................................
Jan 20, 11:09:37  AlohaMgr starting... version 5.045
Jan 20, 11:09:37        MODE SETTINGS
Jan 20, 11:09:37  ***** Version: 5.045
Jan 20, 11:09:37  ***** Workstation: ALOHABOH1
Jan 20, 11:09:37  ***** QuickService Only
Jan 20, 11:09:37  ***** Site Id: 1
Jan 20, 11:09:37  >>>>>>>>>>  ********** DBUP2.EXE For Generation 2 Ver 5.045 **********  <<<<<<<<<<

Jan 20, 11:09:37  Running in Debug Mode
Jan 20, 11:09:37  Iberdir is C:\Aloha
Jan 20, 11:09:37  Will Rebuild DBF CDX Files If Necessary
Jan 20, 11:09:37  Running in Attended Mode
Jan 20, 11:09:37  Current DBF File(s) Location C:\Aloha\NEWDATA
Jan 20, 11:09:37  Upgraded DBF File(s) Location C:\Aloha\NEWDATA
Jan 20, 11:09:37  Upgrading Both DBF Files and the Relational Database.
Jan 20, 11:09:37  Running For Non Enterprise Site.
Jan 20, 11:09:37  Read INI File C:\Aloha\DATA\ALOHA.INI
Jan 20, 11:09:37  Created the Table Depot
Jan 20, 11:09:37  Rebuilding DBF CDX Files If Necessary...
Jan 20, 11:09:37  Building CDX File For DBF File ACC
Jan 20, 11:09:38  Building CDX File For DBF File AMNU
Jan 20, 11:09:38  Building CDX File For DBF File AMNUD
Jan 20, 11:09:38  Building CDX File For DBF File BTN
Jan 20, 11:09:38  Building CDX File For DBF File CashCard
Jan 20, 11:09:38  Building CDX File For DBF File CAT
Jan 20, 11:09:38  Building CDX File For DBF File CEVNT
Jan 20, 11:09:38  Building CDX File For DBF File CEVNTSUB
Jan 20, 11:09:39  Building CDX File For DBF File CIT
Jan 20, 11:09:39  Building CDX File For DBF File CMG
Jan 20, 11:09:39  Building CDX File For DBF File CMP
Jan 20, 11:09:39  Building CDX File For DBF File CTK
Jan 20, 11:09:39  Building CDX File For DBF File DNK
Jan 20, 11:09:39  Building CDX File For DBF File DsplyBrd
Jan 20, 11:09:39  Building CDX File For DBF File DWR
Jan 20, 11:09:39  Building CDX File For DBF File EMP
Jan 20, 11:09:40  Building CDX File For DBF File EMPI9
Jan 20, 11:09:40  Building CDX File For DBF File EXC
Jan 20, 11:09:40  Building CDX File For DBF File FIXPRICE
Jan 20, 11:09:40  Building CDX File For DBF File FLEXTAX
Jan 20, 11:09:40  Building CDX File For DBF File GCI
Jan 20, 11:09:40  Building CDX File For DBF File GIF
Jan 20, 11:09:40  Building CDX File For DBF File HSE
Jan 20, 11:09:40  Building CDX File For DBF File ITM
Jan 20, 11:09:41  Building CDX File For DBF File ITMGRP
Jan 20, 11:09:41  Building CDX File For DBF File ITMGRPL
Jan 20, 11:09:41  Building CDX File For DBF File JOB
Jan 20, 11:09:41  Building CDX File For DBF File JRV
Jan 20, 11:09:41  Building CDX File For DBF File LAB
Jan 20, 11:09:41  Building CDX File For DBF File LABEL
Jan 20, 11:09:41  Building CDX File For DBF File MEMB
Jan 20, 11:09:41  Building CDX File For DBF File MNU
Jan 20, 11:09:42  Building CDX File For DBF File MOD
Jan 20, 11:09:42  Building CDX File For DBF File MSG
Jan 20, 11:09:42  Building CDX File For DBF File MULTCURR
Jan 20, 11:09:42  Building CDX File For DBF File NOSALER
Jan 20, 11:09:42  Building CDX File For DBF File OCC
Jan 20, 11:09:42  Building CDX File For DBF File OCT
Jan 20, 11:09:42  Building CDX File For DBF File ODR
Jan 20, 11:09:43  Building CDX File For DBF File PC
Jan 20, 11:09:43  Building CDX File For DBF File PCID
Jan 20, 11:09:43  Building CDX File For DBF File PCPD
Jan 20, 11:09:43  Building CDX File For DBF File PCPLD
Jan 20, 11:09:43  Building CDX File For DBF File PET
Jan 20, 11:09:44  Building CDX File For DBF File PNL
Jan 20, 11:09:44  Building CDX File For DBF File Poll
Jan 20, 11:09:44  Building CDX File For DBF File PollEvnt
Jan 20, 11:09:44  Building CDX File For DBF File PollSubs
Jan 20, 11:09:44  Building CDX File For DBF File PRD
Jan 20, 11:09:44  Building CDX File For DBF File PRF
Jan 20, 11:09:44  Building CDX File For DBF File PRG
Jan 20, 11:09:44  Building CDX File For DBF File PRL
Jan 20, 11:09:44  Building CDX File For DBF File PRO
Jan 20, 11:09:45  Building CDX File For DBF File PRT
Jan 20, 11:09:45  Building CDX File For DBF File QTYPRICE
Jan 20, 11:09:45  Building CDX File For DBF File QUE
Jan 20, 11:09:45  Building CDX File For DBF File RCP
Jan 20, 11:09:45  Building CDX File For DBF File REG
Jan 20, 11:09:45  Building CDX File For DBF File REV
Jan 20, 11:09:45  Building CDX File For DBF File RSN
Jan 20, 11:09:46  Building CDX File For DBF File RTL
Jan 20, 11:09:46  Building CDX File For DBF File SCALE
Jan 20, 11:09:46  Building CDX File For DBF File SCR
Jan 20, 11:09:46  Building CDX File For DBF File SECLVL
Jan 20, 11:09:46  Building CDX File For DBF File SECLVLDT
Jan 20, 11:09:46  Building CDX File For DBF File SMCRD
Jan 20, 11:09:46  Building CDX File For DBF File SMG
Jan 20, 11:09:46  Building CDX File For DBF File SQLRPT
Jan 20, 11:09:47  Building CDX File For DBF File SQLRPTPM
Jan 20, 11:09:47  Building CDX File For DBF File STO
Jan 20, 11:09:47  Building CDX File For DBF File STREDIT
Jan 20, 11:09:47  Building CDX File For DBF File STRGRP
Jan 20, 11:09:47  Building CDX File For DBF File STRGRPM
Jan 20, 11:09:47  Building CDX File For DBF File SUB
Jan 20, 11:09:47  Building CDX File For DBF File SUR
Jan 20, 11:09:47  Building CDX File For DBF File Survey
Jan 20, 11:09:48  Building CDX File For DBF File TAB
Jan 20, 11:09:48  Building CDX File For DBF File TABDEF
Jan 20, 11:09:48  Building CDX File For DBF File TARE
Jan 20, 11:09:48  Building CDX File For DBF File TAX
Jan 20, 11:09:48  Building CDX File For DBF File TDR
Jan 20, 11:09:48  Building CDX File For DBF File TRK
Jan 20, 11:09:48  Building CDX File For DBF File TRM
Jan 20, 11:09:48  Building CDX File For DBF File VAL
Jan 20, 11:09:49  Building CDX File For DBF File VER
Jan 20, 11:09:49  Building CDX File For DBF File VGP
Jan 20, 11:09:49  Building CDX File For DBF File VID
Jan 20, 11:09:49  Building CDX File For DBF File VOL
Jan 20, 11:09:49  Building CDX File For DBF File ZAP
Jan 20, 11:09:49  CheckCDX: 89 Index Files Were Built
Jan 20, 11:09:49  DBF CDX Files Rebuilt Successfully.
Jan 20, 11:09:49  CAlohaMgrApp::RequestCtlSvr() called...
Jan 20, 11:09:49  WaitForCtlSvrStartupComplete()...
Jan 20, 11:09:49  ACtlSvrConnect: (thread) - Begin Run()
Jan 20, 11:10:13  ACtlSvrConnect: (ICtlSvrCom::AreYouAlive failed (0x4))
Jan 20, 11:10:13  ACtlSvrConnect: Connection to CtlSvr lost Prompting for reconnect...
Jan 20, 11:10:15  ACtlSvrConnect: Lost connection to CtlSvr.  User did not choose to reconnect.
Jan 20, 11:10:17  CBOHSecurity::SecuritySetup() - nonSQLMode - successful return
Jan 20, 11:10:22  AlohaMgr Login: TCR TCR
Jan 20, 11:10:22  CTL4X.DLL initializing... version 5.045
Jan 20, 11:10:22  CAlohaMgrApp::RequestCtlSvr() called...
Jan 20, 11:10:22  ACtlSvrConnect: (ICtlSvrCom::AreYouAlive failed (0x0))
Jan 20, 11:10:22  ACtlSvrConnect: Connection to CtlSvr lost Prompting for reconnect...
Jan 20, 11:10:22  RequestCtlSvrReconnect: Waiting to reconnect CtlSvr...
Jan 20, 12:06:21  CTL4X.DLL initializing... version 5.045
Jan 20, 12:06:21  CTL4X.DLL exiting...
Jan 20, 12:06:21  USERTOOL.DLL initializing... version 5.045
Jan 20, 12:06:21  USERTOOL.DLL exiting...
Jan 20, 12:06:21  Returning from /UnregServer on EdcSvr
Jan 20, 12:06:24  CTL4X.DLL initializing... version 5.045
Jan 20, 12:06:25  CTL4X.DLL exiting...
Jan 20, 12:06:26  USERTOOL.DLL initializing... version 5.045
Jan 20, 12:06:26  USERTOOL.DLL exiting...
Jan 20, 12:06:26  Database Versions and Generation are Current.
Jan 20, 12:06:27  Returning from /Service on EdcSvr
Jan 20, 12:06:34  
Jan 20, 12:06:34  ............................................................
Jan 20, 12:06:34  AlohaMgr starting... version 5.045
Jan 20, 12:06:34        MODE SETTINGS
Jan 20, 12:06:34  ***** Version: 5.045
Jan 20, 12:06:34  ***** Workstation: ALOHABOH1
Jan 20, 12:06:34  ***** QuickService Only
Jan 20, 12:06:34  ***** Site Id: 1
Jan 20, 12:06:34  >>>>>>>>>>  ********** DBUP2.EXE For Generation 2 Ver 5.045 **********  <<<<<<<<<<

Jan 20, 12:06:34  Running in Debug Mode
Jan 20, 12:06:34  Iberdir is C:\Aloha
Jan 20, 12:06:34  Will Rebuild DBF CDX Files If Necessary
Jan 20, 12:06:34  Running in Attended Mode
Jan 20, 12:06:34  Current DBF File(s) Location C:\Aloha\NEWDATA
Jan 20, 12:06:34  Upgraded DBF File(s) Location C:\Aloha\NEWDATA
Jan 20, 12:06:34  Upgrading Both DBF Files and the Relational Database.
Jan 20, 12:06:34  Running For Non Enterprise Site.
Jan 20, 12:06:34  Read INI File C:\Aloha\DATA\ALOHA.INI
Jan 20, 12:06:34  Created the Table Depot
Jan 20, 12:06:34  Rebuilding DBF CDX Files If Necessary...
Jan 20, 12:06:34  CheckCDX: 0 Index Files Were Built
Jan 20, 12:06:34  DBF CDX Files Rebuilt Successfully.
Jan 20, 12:06:34  CAlohaMgrApp::RequestCtlSvr() called...
Jan 20, 12:06:34  WaitForCtlSvrStartupComplete()...
Jan 20, 12:06:34  ACtlSvrConnect: (thread) - Begin Run()
Jan 20, 12:07:35  ACtlSvrConnect: (ICtlSvrCom::AreYouAlive failed (0x3))
Jan 20, 12:07:35  ACtlSvrConnect: Connection to CtlSvr lost Prompting for reconnect...
Jan 20, 12:12:35  ACtlSvrConnect: Lost connection to CtlSvr.  User did not choose to reconnect.
Jan 20, 12:14:50  CBOHSecurity::SecuritySetup() - nonSQLMode - successful return
Jan 20, 12:14:55  AlohaMgr Login: TCR TCR
Jan 20, 12:14:55  CTL4X.DLL initializing... version 5.045
Jan 20, 12:14:55  CAlohaMgrApp::RequestCtlSvr() called...
Jan 20, 12:14:55  ACtlSvrConnect: (ICtlSvrCom::AreYouAlive failed (0x0))
Jan 20, 12:14:55  ACtlSvrConnect: Connection to CtlSvr lost Prompting for reconnect...
Jan 20, 12:14:55  RequestCtlSvrReconnect: Waiting to reconnect CtlSvr...
bigblok403 (TechnicalUser)
22 Jan 07 15:00
I can see that MNT4X.Dll and ALOHASEC.EXE are not initializing at all, but I'm not sure if that's because you don't have the key on or these files were different in this version. This could easily be what's causing the issues. Change the Aloha Manager shortcut to include the remote switch.

Example "C:\Aloha\BIN\AlohaMgr.exe /remote" and see if you still have the same problems.

Also try these at a dos prompt ->

C:\WINDOWS\system32\Regsvr32.exe C:\Aloha\bin\Mnt4x.DLL
C:\Aloha\bin\ALOHASEC.EXE /regserver
C:\Aloha\bin\AlohaMgr.EXE /regserver

It should say successful after each one
justadoode (IS/IT--Management) (OP)
22 Jan 07 16:47
Ok, I did that and including the remote switch bypasses the stalling which is great. Thank you.  I then ran each one of the command lines in DOS and it said each was successful, but I still don't have the menu or submenu options.  To be safe, I went back through and registered the CTL4X.DLL,MNT4X.DLL, and USERTOOL.DLL files using the same command you gave me. The only difference is that I changed the path to read C:\WINNT\system32\Regsvr32.exe C:\Aloha\bin\Mnt4x.DLL (I changed WINDOWS to WINNT because this is Windows 2000 Pro).  At any rate, still no menus or submenus.  They didn't pop up when I had the security key. Could it be they are not initializing because they aren't the same version? The version my local dealer gave me on CD is 5.029 and mine is 5.045. They said as long as the bin files are updated, that wouldn't matter. (these dll's are located in the bin folder) I have another cd they burned for me that has the 5.045 bin folder and I over wrote the existing bin files with that one. Should I go into my Aloha and overwrite the new bin files from the cd with MY CURRENT BIN files that are on the old existing server?
bigblok403 (TechnicalUser)
22 Jan 07 16:54
I would remove the whole Aloha folder on the server, reinstall without putting in your restaurant database using the new cd and the default database, and see if you can access the menus now. If you can, then it is a problem with the database without a doubt.
alohaakamai3 (IS/IT--Management)
22 Jan 07 17:02
Doode: Did you see my earlier post?

>>>One cool features of Aloha is that each day of sales history is like a "snap shot" of that particular day. So, if you think you have data base corruption, you can always go back a few days before your problems started, and paste all of the contents of that day into your Data/Newdata directories. (a few files you don't want to transfer for over, mainly the trans.log is the only one you need to worry about. You'll have to change the date Aloha, too. But I would definitely use the older Aloha.ini). But because this server is not yet in use, none of this is that critical.

I'd probably go this route before I'd start removing individual files within the databse and trying to get it to work. Go back to when it DID work, and try using that data.<<<<<

If database corruption is the problem, this will help.

Generally speaking, if there is a version problem, you'll get an error message saying "Database Version Not Current" when you log in. I do agree it makes for a smoother installation you do have the same version, but I've not see it where menu options just dissapeared. So I am not convinced that because it's a older version, is why you're having issues.

Using older data from a week or so before the install or any problems occured, is not that hard really, and an easy way to rule out problems with your current database. I'd do that first.


justadoode (IS/IT--Management) (OP)
2 Feb 07 23:08
I just wanted to let you guys know the problem was the stupidest thing in the world.  It turns out that I installed Quick Service for Aloha instead of Table Service.  Quick service is for fast food places and uses tablets instead of menus, so that's why the menus and submenus were missing.  Thank you all so much for your help. You guys are as sharp as they get.  Now I know where to go to really get expert advice.  Thanks again!!

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close