Ms Sql Error 18456 Severity 14 State 16
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the error 18456 severity 14 state 38. sql server 2008 r2 workings and policies of this site About Us Learn more about Stack sql error 18456 severity 14 state 5 Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions error 18456 severity 14 state 8 Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join error 18456 severity 14 state 40 them; it only takes a minute: Sign up SQL Server 2005 getting Error: 18456, Severity: 14, State: 16. in log up vote 1 down vote favorite SQL Server 2005 SP4 Standard Edition 32-bit. One to a few times during the work day, seemingly at random, I am getting a log entry of "Login failed for user 'OurDomain\mfreeman'. [CLIENT: 192.168.0.48]".
Error: 18456, Severity: 14, State: 6
This is paired with a log entry of "Error: 18456, Severity: 14, State: 16." at the same time. This is my own login (which has the sysadmin role in the instance), and it is coming from my workstation. I captured an example of this with Profiler and found that it is for the master database (which is online and not having any troubles -- I can run queries against it in SSMS just fine) and is coming from an ApplicationName of ".Net SqlClient" (which could be anything). I am not getting any visible errors in any applcations (such as VS2012 with SSDT and Report Builder) or SSMS add-ins that I am using (ApexSQL Complete, SSMS Tools, Dell Spotlight Essentials). Is there any way to find out more specifically what might be attempting the access or why it might be failing? sql-server sql-server-2005 login share|improve this question asked Dec 19 '13 at 16:05 Mark Freeman 66911234 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote State 16 means that the defaul
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow
Error 18456 Severity 14 State 11
the company Business Learn more about hiring developers or posting ads with us Database Administrators error 18456 severity 14 state 58 Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who error 18456 severity 14 state 5 login failed for user wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers http://stackoverflow.com/questions/20686293/sql-server-2005-getting-error-18456-severity-14-state-16-in-log are voted up and rise to the top Login failed for user - Error 18456 - Severity 14, State 38 up vote 12 down vote favorite 4 Message that SQL Server Log File Viewer shows: 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 http://dba.stackexchange.com/questions/29613/login-failed-for-user-error-18456-severity-14-state-38 failed), for each combination of severity and state, with the helpful description text? I've had a Google but can't find anything other than specific combinations. sql-server errors logins share|improve this question asked Nov 30 '12 at 16:30 Pete Oakey 2841210 add a comment| 2 Answers 2 active oldest votes up vote 11 down vote State codes and their meaning. 1 'Account is locked out' 2 'User id is not valid' 3-4 'Undocumented' 5 'User id is not valid' 6 'Undocumented' 7 'The login being used is disabled' 8 'Incorrect password' 9 'Invalid password' 10 'Related to a SQL login being bound to Windows domain password policy enforcement. See KB925744.' 11-12 'Login valid but server access failed' 16 'Login valid, but not permissioned to use the target database' 18 'Password expired' 27 'Initial database could not be found' 38 'Login valid but database unavailable (or login not permissioned)' More detailed information is available in Aaron Bertrand's blog. share|improve this answer edited Dec 1 '12 at 13:27 answered Nov 30 '12 at 16:33 Pete Oakey 2841210 5 A LOT more details on these states (and several more states covered) in my blog post from last year: sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/… –Aaron Bertrand♦ Nov 30 '12 at 17:04 add a comment| up vote 0 down vote Here is what I found when I res
of Plan Explorer and a performance monitoring and event management platform for the Microsoft Data Platform and VMware. He has been blogging here http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx at sqlblog.com since 2006, focusing on manageability, performance, and new features, and also blogs at blogs.sentryone.com and SQLPerformance.com; has been a Microsoft MVP since 1997; tweets as @AaronBertrand; and speaks frequently at major conferences, user group meetings, and SQL Saturday events worldwide. Troubleshooting Error 18456 I think we've all dealt with error 18456, whether it be an application unable to access SQL Server, credentials changing over time, or error 18456 a user who can't type a password correctly. 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). In a few cases, some additional information is included, but for the most part several of these conditions appear the same error 18456 severity to the end user. 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. I helped our support team just today solve a client's 18456 issues - once we tracked down the error log and saw that it was state 16, it was easy to determine that their login had been set up with a default database that had been detached long ago. In SQL Server 2012, there is a new feature called "contained databases" - I've blogged about it here and here. With this feature comes a new layer of security that may creep onto your radar if you use this functionality: contained user authentication failures. There are a variety of things that can go wrong here. If you connect with a contained user but forget to specify a database name, SQL Server will attempt to authorize you as a SQL login, and you will fail with state 5 (if there is no SQL login with that name) or state 8 (if there is also a SQL login with the same name and the password doesn't match). There