Error 18456 Severity 14 State 38. Sql Server 2008 R2
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
Error 18456 Severity 14 State 38 Nt Authority System
Stack Overflow the company Business Learn more about hiring developers or posting ads with 'login valid but database unavailable (or login not permissioned)' us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site sql error 17054 severity 16 state 1 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 a question
Sql Error 18456 Severity 14 State 5
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 list somewhere of
Sql Server Error 18456 Severity 14 State 1
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_bertrand/archive/2011/01/14/… –Aaron Bertrand♦ Nov 30 '12 at 1
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 connection has failed, different State numbers associated with the error can mean different reasons error 18456 severity 14 state 38 sharepoint for the failure. One of the error States is 38, which was added with SQL Server
Error 17187 Severity 16 State 1
2008, means the database being accessed cannot be found or does not exist. Unfortunately the Error Log entry does not show what database it error 18456 severity 14 state 40 is, so in this tip we walk through how you can 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 http://dba.stackexchange.com/questions/29613/login-failed-for-user-error-18456-severity-14-state-38 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 '
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2008 » Security (SS2K8) » Error: 18456, Severity: 14, State:38 Error: http://www.sqlservercentral.com/Forums/Topic1345822-1526-1.aspx 18456, Severity: 14, State:38 Rate Topic Display Mode Topic Options Author Message adb2303adb2303 Posted Thursday, August 16, 2012 4:56 AM SSC Eights! Group: General Forum Members Last Login: Today @ 7:36 AM Points: 943, Visits: 2,815 Hi,I've just moved all my SQL Server 2005 databases to a SQL Server 2008 R2 server with the same domain. I am 100% confident that all databases are present and accounted for. I used sp_help_revlogin to error 18456 get the logins from 2005 server to the 2008 R2 server. All logins were created successfully. I then ran the following:ALTER USER [MYDOMAIN\MYACCOUNT] WITH LOGIN = [MYDOMAIN\MYACCOUNT]The problem is, I am getting the following error in the SQL Server Error log:Login failed for user 'MYDOMAIN\MYACCOUNT'. Reason: Failed to open the explicitly specified database [CLIENT:XX.XX.XX.XXX]Error: 18456, Severity: 14, State: 38I get this error even if I give the give the domain account sysadmin error 18456 severity privileges on this box (which it doesn't have normally). I query sys.dm_os_ring_buffers and I can see several RING_BUFFER_SECURITY_ERROR errors, with ErrorCode: 0x534, APIName: LookupAccountSID. This, as far as I know, is a problem resolving the login details against AD. Then why does the very same account work perfectly fine on the same server in all the databases that it's been permissioned for?Any help greatly appreciated.Andrew Post #1345822 adb2303adb2303 Posted Thursday, August 16, 2012 7:29 AM SSC Eights! Group: General Forum Members Last Login: Today @ 7:36 AM Points: 943, Visits: 2,815 sp_validatelogins doesn't return anything either Post #1345952 anthony.greenanthony.green Posted Thursday, August 16, 2012 7:31 AM SSCertifiable Group: General Forum Members Last Login: Thursday, September 1, 2016 2:56 AM Points: 5,969, Visits: 6,067 Run a trace for failed logins and see what database the failure is on.Then check to see if the DB exists or if the user has access to the DB. Want an answer fast? Try hereHow to post data/code for the best help - Jeff ModenWhen a question, really isn't a question - Jeff SmithNeed a string splitter, try this - Jeff ModenHow to post performance problems - Gail ShawCrossTabs-Part1 & Part2 - Jeff ModenSQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola HallengrenManaging Transaction Logs - Gail ShawTroubles