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

Aloha Manager - Cant login ( Exceeded number of login attempts )

Status
Not open for further replies.

kaballon

Technical User
May 17, 2016
2
US
Hello,

In my restaurant, we have the ALOHA pos system, and I'm trying to print the employee's timecard when this issue came up. After trying to login couple of times it says "You have exceeded the allowed number of login attempts. This user account has been disabled. You must contact the system administration and have your password reset.

Now I called the previous manager, and he told me the restaurant canceled aloha support from the POS company they bought it from.

Now previous manager told me there are other numbers that was used to login before, but he forgot them as well. Is there a way we can pull up the user # ? or any other ideas ?

Thank you
 
In this situation, i've made a backup of the emp.dbf in the /newdata folder. Using a program called DBF Navigator, i've edited the database file to change my user to an admin, and remove the hashed password. This allowed me to log back in as an admin and set a new password.


Close Aloha Manager
Open the emp.dbf
Find your user
Edit the "SECLEVEL" to match a known admin.
Remove the "BOHLASTPWD".
Remove the "BOHHASHPW".
Save and exit
Re-open Aloha Manager
Try to login. You should not have a password.
 
Let me add a little bit more to MenuLinkman
find the user in question
Check for column BOHPASSWRD. if there are any characters there delete them. save and close
restart aloha manger. if you are asked to change password do it and all is good again.

Option 2

open emp.dbf with dbf navagotor
scroll to far right until you find SECLEVEL. Sort from high to low. 1 of those numbers has the highest security. Change any of the zeros below it to that number. In my example 200 is the highest security level I use. so change
emp_fix_dqrrdf.jpg

Now scroll back to far left. You will see what employee number you changed. save and close

Now open aloha manager
log in with number just promoted via dbfnavigotor, no password needed.
it will prompt you to change password
Now go into emplyee maintenence and clear bph password for employee who was locked out.
Log out of aloha
log back in with formally locked number. no password needed. You will be prompted to change
And now you are back in and have 2 numbers with full boh rights

AlohaRoss
3rd Party support
 
yep. If there is something there you can clear the password. IF there is nothing there, then you must promote someone else. Simple hack for old Aloha Manager. New Aloha manager is something much harder.

AlohaRoss
3rd Party support
 
A momentary power loss to my system the other day has caused Aloha BOH (old Aloha Manager, 2014) to behave strangely. I can sign in to Aloha EDC, yet I cannot sign in to Aloha Manager with same id/password combination. At this point, my account has been disabled by Aloha Manager for access to Aloha Manager and must be reset. Despite following the recommendations above to reset my account or create another admin account via modification to the EMP.DBF file in the NEWDATA folder, Aloha Manager continues to see my account as disabled due to excessive invalid login attempts, and is 'Unable to complete the login process because the Username, Password or Security Role could not be verified...' for other admin accounts created. The behavior suggests that Aloha Manager is not accessing the EMP.DBF file before issuing the 'Unable to complete the login process' message, insofar as an 'incorrect password' message is never produced.

Thanks in advance.
 
Oh this is an easy fix. Same file emp.dbf there is a field called "NCFLOGON" If your max login attempts is say 4. You will see a 4 in the column and row where this employee is locked. Change it to 0 save the file and you shouldn't have a problem logging in.
 
Thanks very much for the thought - unfortunately, nothing has changed as a result of making this change to the EMP.DBF file in the NEWDATA folder. NCFLOGON has been reset to '0'. BOHLASTPWD = '0' and BOHHASHPW = ' '. Aloha Manager continues to see my account as disabled due to excessive invalid login attempts. and is 'Unable to complete the login process because the Username, Password or Security Role could not be verified...' for other admin accounts created.

The behavior suggests that Aloha Manager is not accessing the EMP.DBF file before issuing the 'Unable to complete the login process' message, insofar as an 'incorrect password' message is never produced.

Thanks
 
Delete what is in the NCFLOGON, BOHLASTPWD, LASTCHPSWD, and the BOHPASSWRD fields for the employee that can't login in the EMP.DBF using a free DBF editor such as DBFPlus. This file is located in the Aloha(qs or ts)\NEWDATA folder. After clearing these fields login using no password and Aloha Manager will ask you to create a new password for yourself. You can do this all the way up to 6.7
 
I have edited the EMP.DBF file in the NEWDATA folder, zeroing out the numeric fields (NCFLOGON, BOHLASTPWD, LASTCHPSWD) and deleted the contents of the text field (BOHPASSWRD). However, the result is the same as previously - Aloha Manager continues to see my account as disabled due to excessive invalid login attempts.

Interestingly, if I rename the EMP.DBF file so Aloha Manager can't find it, the result is the same - Aloha Manager continues to see my account as disabled due to excessive invalid login attempts. This leads me to believe that Aloha Manager may not be accessing this file for login authentication.

thx
 
check what boh secuirty level you have via emp.dbf. find other user with 0 currently. change to match your level. save
now log in with that number. it will promt for new password on first log in. once in you can find your number and choose clear boh password. log out and log back in as you

AlohaRoss
3rd Party support
 
Modified another user's security level in ALOHA/NEWDATA/EMP.DBF. Aloha Manager is 'Unable to complete the login process because the Username, Password or Security Role could not be verified...' for other admin accounts created.

It is significant that Aloha EDC is accessible via normal login, appears to function normally and definitely uses ALOHA/NEWDATA/EMP.DBF for its authentication: the field values for NCFLOGON, BOHLASTPWD, LASTCHPSWD and BOHPASSWRD change in keeping with modifications made through use of Aloha EDC.

It is significant that Aloha Manager rejects the same accounts just accessed via Aloha EDC as disabled due to excessive invalid login attempts, and that it 'cannot complete the login process because the Username, Password or Security Role could not be verified...' for other admin accounts created.

I think in light of this behavior, it seems that Aloha Manager is not accessing ALOHA/NEWDATA/EMP.DBF, but rather a prior imprint of this file.

thx

 
I'd prefer not to repair the damage rather than replace the framework.

thx
 
I am just wondering why you wouldn't move up to New Aloha Manager. There are security concerns with old aloha manager.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top