Error 18456 Error State 38
Contents |
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 the error 18456 sql server company Business Learn more about hiring developers or posting ads with us Database Administrators Questions error 18456 severity 14 state 38 Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to error 18456 severity 14 state 38 nt authority system 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 are voted error 18456 severity 14 state 38 sql 2008 r2 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 failed), for each
Error 18456 State 1
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 resolved this error: I had created so
Related Tips: More > Error Logs Problem SQL Server Error Logs often show a message related to error 18456. Although it generally means a login attempt from a client
Error 18456 State 5
connection has failed, different State numbers associated with the error can mean different sql error 18456 state 28000 reasons for the failure. One of the error States is 38, which was added with SQL Server 2008, means the error 18456 severity 14 state 8 database being accessed cannot be found or does not exist. Unfortunately the Error Log entry does not show what database it is, so in this tip we walk through how you can http://dba.stackexchange.com/questions/29613/login-failed-for-user-error-18456-severity-14-state-38 determine which database is causing the error message. Solution A few days ago I was looking through the Error Log of a database server and noticed a large number of the same error messages that looked like the following: 2011-12-15 11:22:08.76 Logon Error: 18456, Severity: 14, State: 38. 2011-12-15 11:22:08.76 Logon Login failed for user '
I had to help a client out with an error that kept appearing in their event logs: Login failed for user ‘domain\user'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.25] It took me a while to troubleshoot the https://justaprogrammer.net/2012/12/09/a-misleading-sql-error-message-error-18456-severity-14-state-38/ error. The client's internal system administrator (who was quite sharp) only had to call me in in the first place because the error was a little misleading. See the first thing I did when I saw that was audit login failures. In the trace, the database was listed as master. The user had full access to master. However, I later learned that the user was switching from master to a non-existent database, which was triggering this error. error 18456 I figured this out thanks to Sadequl Hussain‘s article, SQL Server Error 18456: Finding the Missing Databases. Sadequl explains in detail the how and the why. However, the take home is you need to trace for User Error Message to get the message that tells you what database you are connecting to. This took me about an hour to solve. Honestly, it was a bit humbling of an experience. It took me an hour to figure out something error 18456 severity a full time senior DBA would probably be able to solve in 15 minutes. However, I'll probably be able to solve this error in 15 minutes myself go forward. Finally, the fact that it took me a while to find this one blog article that explained what the issue actually was proves how dependent I've become upon google. Tagged Microsoft SQL Server Post navigation The #MongoHelp twitter manifestoAnnouncing ILRepack-BuildTasks Search for: Recent Posts Giving back to #sqlfamily Microsoft, please open source sqlcmd, Sqlps, SMO, and LogParser The case for open sourcing the SQL Saturday Website Split testing using nginx proxy cache Creating a minimally viable Centos instance for SSH X11 Forwarding Tags#SQLAmtrak #sqlfamily .Net 2010 year in review Async Workflow Atlantis Interactive centos chocolatey command line console f# farmanager firing fsharpx git github HowTo javascript jQuery meta Microsoft Microsoft SQL Server mongodb MSBuild MySQL OLPC Open Source OSS path php PlaneDisaster.NET poshrunner PowerShell project euler ReactOS RedGate SQL SQL Saturday SQL Saturday 121 SVG System Administration Team Foundation Server Visual Studio WCF windows internals study group Archives March 2015 April 2014 November 2013 May 2013 January 2013 December 2012 November 2012 October 2012 September 2012 August 2012 July 2012 June 2012 April 2012 March 2012 February 2012 January 2012 December 2011 November 2011 October 2011 September 2011 August 2011 June 2011 May 2011 April 2011 March 2011 February 2011 Janu