![sql error 18456 state 1 sql error 18456 state 1](http://sql-articles.com/images/media/articles/error_18456_5.jpg)
The way I was able to find my old sa password was using docker history -no-trunc microsoft/mssql-server-linux and scrolling up hoping to find the last docker run command that had the SAPASSWORD set. Unfortunately I did not have my original sa password used when mounting volume. 11:14:18.440 Logon Login failed for user 'leks'. The solution provided was not an option for me as I needed the database files.
![sql error 18456 state 1 sql error 18456 state 1](https://s3.us-west-1.wasabisys.com/loginports/img/login-failed-for-user-sa-sql-server-2012-1.jpg)
So see the error log file for the STATE of this error 18456 from the default pathĬ:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOGĪnd the entry for this login failed error in the error log would be something like this
In this case, the true state of the 18456 error is reported in the SQL Server Error Log file When a connection attempt is rejected because of an authentication failure that involves a bad password or user name, a message similar to the following is returned to the client: 'Login failed for userDate/Time spid7s Skipping the default startup of database DatabaseName because the database belongs to an availability group (Group ID: GroupID ). To increase security, the error message that is returned to the client deliberately hides the nature of the authentication error by always setting the state of the 18456 error to 1.īy default, auditing of failed logins is enabled. About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features Press Copyright Contact us Creators. Date/Time spid7s Error: 35262, Severity: 17, State: 1. However, you always receive this "Logon Error: 18456" error message that has a state set to 1 in the client application.