You might look into a corresponding entry in log as: 00:12:00.34 Logon Error: 18456, Severity: 14, State: 8. So to investigate further you need to look at relevant SQL Server instance error log too for more information on Severity & state of this error. By default the Operating System error will show 'State' as 1 regardless of nature of the issues in authenticating the login. Ok now what, by looking at the error message you feel like this is non-descriptive to understand the Level & state. Obviously if the necessary prvileges are not been set then you need to fix that issue by granting relevant privileges for that user login.Īlthought if that user has relevant grants on database & server if the Server encounters any credential issues for that login then it will prevent in granting the authentication back to SQL Server, the client will get the following error message: Msg 18456, Level 14, State 1, Server, Line 1 First task you might check is to see whether that user has relevant privileges on that SQL Server instance and relevant database too, thats good. Under "Server Authentication" choose the "SQL Server and Windows Authentication mode" radio option.īy default login failed error message is nothing but a client user connection has been refused by the server due to mismatch of login credentials.
In the "Server Properties" window click on "Security" in the list of pages on the left.
In the Object Explorer, right click on the server and click on "Properties".You need to enable SQL Server Authentication:
0 kommentar(er)
