Error 18456 Severity 14 State 38 Sharepoint
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 error 18456 severity 14 state 38 nt authority system about Stack Overflow the company Business Learn more about hiring developers or posting
Error 18456 Severity 14 State 38 Sql 2008 R2
ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and sql server error 18456 severity 14 state 38 answer site for database professionals who 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 error 18456 severity 14 state 38 login failed a question Anybody can answer The best answers 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
Error 18456 Severity 14 State 11
list somewhere of all the variations of the 18456 errors (Login 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_b
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums error 18456 severity 14 state 11 nt authority anonymous logon Asked by: Login Failed Error: 18456, Severity: 14 State: error 18456 severity 14 state 5 38 SharePoint > SharePoint 2010 - Setup, Upgrade, Administration and Operations Question 0 Sign in
Error 18456 Severity 14 State 5 Login Failed For User
to vote I've done as much searching on the web as I can to try to find a solution to this error, however it http://dba.stackexchange.com/questions/29613/login-failed-for-user-error-18456-severity-14-state-38 seems that my particular case is a bit more unique. We are running SharePoint 2010 with SQL 2008 R2. The error from the SQL log reports: 04/06/2012 09:39:54,Logon,Unknown,Login failed for user 'Domain\user1'. Reason: Failed to open the explicitly specified database. [CLIENT:
of Plan Explorer and a performance monitoring and event management platform for the Microsoft Data Platform and VMware. He has been blogging here at sqlblog.com since 2006, focusing on manageability, performance, and new http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx features, and also blogs at blogs.sentryone.com and SQLPerformance.com; has been a Microsoft MVP since 1997; tweets https://justaprogrammer.net/2012/12/09/a-misleading-sql-error-message-error-18456-severity-14-state-38/ 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 a user who can't type a password correctly. The trick to troubleshooting this error number is that the error message error 18456 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 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 error 18456 severity 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 is also a new state 65 which occurs if you have specified the correct username and contained database, but entered an incorrect password. The way that the authentication process works is, if SQL Server doesn't find your user in the contained database you specifies, it tries again at the server level, then gives up (it won't go check all
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 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. 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 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 January 2011 December 2010 October 2010 September 2010 August 2010 Jul