Error 18456 Severity 14 State 38 Login Failed For User

Login failed for user [User] Error: 18456, Severity: 14, State 38 What it actually means: Failed to open the explicitly specified database My Question: Is there a list somewhere of all the variations of the 18456 errors (Login failed), for each combination of severity and state, with the helpful description text?

Aug 12, 2018 · According to https://sqlblog.org/2011/01/14/troubleshooting-error-18456 state 38 is Cannot open database "<database>" requested by the login. The login failed. But we should not pay too much attention to this error at this moment. Instead we should look at the user name in the error message NT AUTHORITY\SYSTEM. If users are logging in with in their own SQL logins, you would …

Sep 19, 2017 · State 38 of Login failed, is logged when the account is having insufficient access to the database (SharePoint_Config). To fix it, we connected to SQL Server using SSMS and navigated to the Security > Logins > Right click on the account, and went to properties.

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share …

May 02, 2012 · Error: 18456, Severity:14, State: 58 means: 58 State 58 occurs when SQL Server is set to use Windows Authentication only, and a client attempts to log in using SQL Authentication.

"Msg 18456, Level 14, State 1, Server <computer_name>, Line 1" "Login failed for user '<user_name>'." Additional Error Information. To increase security, the error message that is returned to the client deliberately hides the nature of the authentication error. However, in the SQL Server error log, a corresponding error contains an error state that maps to an authentication failure condition. …

Sep 08, 2016 · Some errors are historic and have the most common root cause. Sometimes we really don’t know why they happen and I have seen clients go nuts to identify the real reason for the problem. In a recent email interaction with one customer – who was migrating from Oracle to SQL Server. He kept telling me that they were getting login errors from their Java application. And even when they used the ...

I looked at the SQL Server logins and saw that the account in question was a member of the sysadmin role, meaning it had unrestricted access to all the databases in the server.

Use the Windows login mode (it does not allow any password, and must be the current windows user). Otherwise, create the NT user as a login for security & database rights in SQL Server. If you are trying to do a Windows login with a different user name, you have to impersonate or run the program as that user.