If correct password is supplied for disabled login then client would get below error (18470) Notice that state 7 would come if account is disabled and incorrect password is supplied. Reason: An error occurred while evaluating the password. 05:41:30.390 Logon Login failed for user ‘DisabledLogin’.
State 7: Account disabled AND incorrect password.
Reason: Could not find a login matching the name provided. 05:35:48.850 Logon Login failed for user ‘InvalidLogin’. Here is the quick cheat sheet which I have saved. In those days, we used to keep a track of all states and their meanings but thankfully, I don’t need it any more. Notice that reason was not shown in earlier version of SQL in ERRORLOG. 04:37:07.910 Logon Login failed for user ‘sa’. It is important to note that in earlier version of SQL Server (before SQL 2008), the error message was something like below. Reason: Password did not match that for the login provided. Here is what we would see in ERRORLOG is failed login auditing (option 1 and 3 in above image) is enabled. You can verify them by Right Click on Server node > Properties > Security and check In this case, the true state of the 18456 error is reported in the SQL Server Errorlog file. By default, auditing of failed logins is enabled. The very first thing which I always ask is look at ERRORLOG and find error at exact same time. SQL Server deliberately hides the nature of the authentication error and gives State 1. This error doesn’t tell “exact” reason about login failed for user. If we click on more details, we would see this Here is what client would see in all situations (I have done it from SSMS) First, we need to understand that due to security reasons, SQL Server doesn’t send more information about this error message to client. In this blog, I am going to share few possible causes of the error and their solution. “Login failed for user” is one of the most common error which everyone might have seen at least once.
0 kommentar(er)
