Sage 50: You have entered an invalid User ID or Password
Sage 50 cannot match what you typed against the user list stored inside the company file, and a wrong password is only one cause.
When Sage 50 shows “You have entered an invalid User ID or Password.” it means the program could not match what you typed against the list of sign-ons stored inside the company file you opened. A mistyped password is only one possible cause. The same message appears when you are opening the wrong copy of the file, when the user list has reverted to an earlier state, or when the part of the file that holds user names and passwords has been damaged. Peachtree and Simply Accounting users see the identical wording.
Check the simple things first
Retype the user ID and password slowly. Passwords are case-sensitive, so check Caps Lock and Num Lock, and make sure no stray space was added in front of or behind either field. If more than one person has a sign-on in this company, try each one you know. A large share of rejections end here.
Confirm you are opening the right company file
User IDs and passwords are not stored in the Sage 50 program; they live inside each company file. If you have more than one company, or more than one copy of the same company on the computer or network, you may be signing in to a copy whose user list is not the one you expect. Two situations catch people out regularly:
- A file restored from a backup reverts to the user list as it stood on the day the backup was taken. A password changed after that date will be rejected even though it is correct for the live file.
- A file copied to a new computer keeps its original user list. If sign-ons were changed on the old machine after the copy was made, the copy will not accept the newer password.
Open the exact file you were using before the message appeared, or the most recent backup of it, and try again.
Try the administrator sign-on
Every company file has an administrator sign-on, created when the company was first set up, with full rights. If a regular user’s password is the problem, the administrator can reset it from within the program; the exact route depends on your version and edition of Sage 50. If the administrator password itself is the one that is lost or rejected, the options inside the program are limited and depend on how the file was configured.
When the credentials are right and still rejected
The user list and password data are part of the company file, and like the rest of the file they can be damaged by a power loss, a crash, or an update that was interrupted midway. When that happens, every sign-on is rejected, including the administrator’s, even though nothing was mistyped. Conversions and downgrades can have a similar effect: a file moved between editions can end up with a user list the destination edition will not accept. If you have just downgraded or converted a Sage 50 file and can no longer sign in, that is a strong clue.
What we can do
If the sign-ons are genuinely lost or the user list is damaged, this is not something to keep guessing at. Our engineers work directly on the company file: we confirm whether the user data is intact, recover or reset the sign-ons, and repair the underlying damage so the file opens normally again. Our password recovery service for accounting data files covers lost sign-ons, and our Sage 50 database repair service covers the case where the file itself is the problem.
Before anyone works on the file, make a fresh copy of it and set the original aside.
If the administrator sign-on is also being rejected and you are confident of the password, the file needs professional attention. Send it to us for a free evaluation and we will tell you exactly what is wrong and what a repair involves, with a free quote and no obligation.