![]() In order to figure out what is really going wrong, you need to have alternative access to the SQL Server and inspect the log for the true state in the error message. In a few cases, some additional information is included, but for the most part several of these conditions appear the same to the end user. The trick to troubleshooting this error number is that the error message returned to the client or application trying to connect is intentionally vague (the error message is similar for most errors, and the state is always 1). ![]() ![]() I think we've all dealt with error 18456, whether it be an application unable to access SQL Server, credentials changing over time, or a user who can't type a password correctly. Updated in July 2020 with a few new states
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |