![]() ![]() Stop now and call your DBA! If you don’t have a DBA, then call XTIVIA. Ensure the user is not required to change the password at the next logon. If it is possible to log in with an elevated account, verify the account name and change the password at this point. If it is possible to log in with an elevated account, ensure the user is a member of the instance level public role or they have the CONNECT privilege directly assigned to the login. Verify Login is enabledĮnsure the login is not disabled. Try a copy / paste or re-enter the password again. Is the password correct?Įrror: 18456 can result from a bad password. If the login is a SQL Login, is the login name spelled correctly? Verify the appropriate login name is being used. Sometimes, this can be overlooked and you end up attempting to connect to the wrong instance. SSQL Server Management Studio (SSMS) likes to keep the name of the last connected to instance as the default for the next time SSMS runs. Are you connecting to the correct instance? Error: 18456 shown as generated by the sa accountįollow the steps below to try and resolve the issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |