CLTSVR: Security key not found (HELP) 1

[justadoode]

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]

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]

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]

I also suggest reinstalling new HASP drivers. Windows XP and Aloha 5.0 work just fine together if it is setup correctly.

 

[justadoode]

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?

 

[alohaakamai3]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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.