I recently had a hard drive failure and had to reload Win2000 Server. Copied all the data for Aloha back on the system and re-registered the services and registry. Everytime I try to open Aloha Manager I recieve the following error: "The Aloha POS License Agreement is either missing or corrupt. Please contact Customer Service for assistance." Then the login screen comes up and I put the login information and then get the following error: "Security setup failed. Aloha Manager cannot log users in without a valid path to an Aloha data directory." Please help! Thanks in advance.
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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
PLEASE HELP!! Aloha Manager Error
- Thread starter tecky98
- Start date
bigblok403
Technical User
You're missing the ALOHA.LIC (License Agreement)or it's properties changed. It's a hidden file you can copy from the CD to the Aloha directory. Security error could be IBERDIR variable missing or incorrect. Also try using DBCONFIG to fix configuration files.
It means that it can't find or read the Aloha folder.
This could be, as bigblok said, an iberdir variable missing or incorrect. I think it could likely be a permissions error. Whatever username is ctlsvr running on, needs to have full access security and sharing on that drive. You may need to logon to windows as that user and see if that works.
Basically, try and straighten out your users on that machine. You have to run CTLSVR as a service using a specific user name and password in win2000.
I usually run ctlsvr as the User 'ALOHA', who would have administrative rights. Then register the service using that user/pass like this:
ctlsvr.exe /service /accountname .\ /password password
The errors you received are symptoms that occur in order after the app opens. First, it looks for a .lic file and didn't find it. No big deal, but you get the warning. Then it look for the emp.dbf to validate who can log in to the app. It didn't find it, or didn't have permission to open it, so it gave you another error. The app can't open without being able to look in the emp.dbf file and see who is allowed to use it.
If it can't find it, then check your environment variables, IBERDIR and IBERROOT and make sure they're correct.
If it can't read it, then check your permissions.
This could be, as bigblok said, an iberdir variable missing or incorrect. I think it could likely be a permissions error. Whatever username is ctlsvr running on, needs to have full access security and sharing on that drive. You may need to logon to windows as that user and see if that works.
Basically, try and straighten out your users on that machine. You have to run CTLSVR as a service using a specific user name and password in win2000.
I usually run ctlsvr as the User 'ALOHA', who would have administrative rights. Then register the service using that user/pass like this:
ctlsvr.exe /service /accountname .\ /password password
The errors you received are symptoms that occur in order after the app opens. First, it looks for a .lic file and didn't find it. No big deal, but you get the warning. Then it look for the emp.dbf to validate who can log in to the app. It didn't find it, or didn't have permission to open it, so it gave you another error. The app can't open without being able to look in the emp.dbf file and see who is allowed to use it.
If it can't find it, then check your environment variables, IBERDIR and IBERROOT and make sure they're correct.
If it can't read it, then check your permissions.
- Thread starter
- #4
Well I did find the problem, but now I have another issue. For some reason Aloha manager was looking for files on the C: drive rather than the D: where aloha is. So I copied the aloha folder on the D: to the C: and it worked. But thats not how it should be. Any ideas how to change it to locate the files on the D: instead of C:? Also I can't get the FOH to use the BOH as a server, it keeps mapping another FOH terminal as the server. Any ideas. Thank you so much for your time and help.
That is due to the environment variables.
Set them on the server to be:
IBERDIR=D:\aloha
IBERROOT=aloha
Make sure your aloha manager shortcut doesn't have any thing tacked on to the end. (It should be only: D:\aloha\bin\alohamgr.exe)
PS. from a command prompt, you can type SET to see what the variables are currently.
Set them on the server to be:
IBERDIR=D:\aloha
IBERROOT=aloha
Make sure your aloha manager shortcut doesn't have any thing tacked on to the end. (It should be only: D:\aloha\bin\alohamgr.exe)
PS. from a command prompt, you can type SET to see what the variables are currently.
- Thread starter
- #6
Thanks that helps alot... Any ideas how to get the terminals to transfer the data to the server when they were running redundant mode? We have about 8 terminals and they all are using terminal 3 as a server. Should the server be ALOHABOH on each terminal? Any ideas? Thanks I greatly appreciate it!
yes, another environment variable, but this time on the terminals.
SERVER=servername
After you can open the ALOHA folder on the server FROM a terminal, then in aloha manager, utilities, FILESERVER RECOVERY should modify your downtime.ini's and move the server to the fileserver where it belongs. If this doesn't happen, then you still have a permissions issue from the terminals, or the variables are still wrong.
Try mapping a drive (Z:\) on the terminal, to the \\servername\sharename[\i]\ALOHA\ folder and see if it asks you for a user\pass. if it does, then your permissions aren't right yet.
Hopefully, after you rebuilt the server, you named it the same as it was before. Then the terminals variables won't have to be changed. But if it is a different name, then make sure the terminals are setting the correct SERVER=servername.
Usually this is set from the ibercfg.bat file, or the autoexec.bat file, or they could just be set in windows.
SERVER=servername
After you can open the ALOHA folder on the server FROM a terminal, then in aloha manager, utilities, FILESERVER RECOVERY should modify your downtime.ini's and move the server to the fileserver where it belongs. If this doesn't happen, then you still have a permissions issue from the terminals, or the variables are still wrong.
Try mapping a drive (Z:\) on the terminal, to the \\servername\sharename[\i]\ALOHA\ folder and see if it asks you for a user\pass. if it does, then your permissions aren't right yet.
Hopefully, after you rebuilt the server, you named it the same as it was before. Then the terminals variables won't have to be changed. But if it is a different name, then make sure the terminals are setting the correct SERVER=servername.
Usually this is set from the ibercfg.bat file, or the autoexec.bat file, or they could just be set in windows.
- Thread starter
- #8
- Thread starter
- #9
fileserver recovery is under UTILITIES. You may not have access to it, depending on how you are logging in.
"Start FOH" should be greyed out. If it isn't, then "Stop FOH" should be greyed out.
If Start is black, go ahead and start FOH now. It shouldn't do anything yet, but then it will be ready when the terminals are.
Once you are able to map the Z drive, as stated above, from each terminal, without prompting for user/pass, and you still can't get to F/S Recovery, then:
Turn all of the terminals off, leaving the MASTER on.
Close aloha by killing process on iber.exe. (in task manager)
delete the file c:\aloha\downtime.ini on the MASTER.
Reboot MASTER. It should find the fileserver within 5 seconds. If not, you still have a problem.
(don't forget to ping the server from the terminals just to make sure you have connectivity!)
Also, to clarify and simplify, at this point, use the same user and password to run ctlsvr as the terminals use to login to windows. If you don't know how to run a service as a specific user, let me know.
"Start FOH" should be greyed out. If it isn't, then "Stop FOH" should be greyed out.
If Start is black, go ahead and start FOH now. It shouldn't do anything yet, but then it will be ready when the terminals are.
Once you are able to map the Z drive, as stated above, from each terminal, without prompting for user/pass, and you still can't get to F/S Recovery, then:
Turn all of the terminals off, leaving the MASTER on.
Close aloha by killing process on iber.exe. (in task manager)
delete the file c:\aloha\downtime.ini on the MASTER.
Reboot MASTER. It should find the fileserver within 5 seconds. If not, you still have a problem.
(don't forget to ping the server from the terminals just to make sure you have connectivity!)
Also, to clarify and simplify, at this point, use the same user and password to run ctlsvr as the terminals use to login to windows. If you don't know how to run a service as a specific user, let me know.
- Status