Error 18456 Severity 14 State 38 Login Failed
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 error 18456 severity 14 state 38 nt authority system the company Business Learn more about hiring developers or posting ads with us Database error 18456 severity 14 state 38 sql 2008 r2 Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals sql server error 18456 severity 14 state 38 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 Anybody can answer The
Error 18456 Severity 14 State 11
best answers are voted up and rise to the top Login failed for user - Error: 18456, Severity: 14, State: 38 [duplicate] up vote 0 down vote favorite This question already has an answer here: Login failed for user - Error 18456 - Severity 14, State 38 2 answers I am trying to run and ADODB command in MS Access 2012 to exec a stored proc in our SQL server 2008R2 database, but error 18456 severity 14 state 11 nt authority anonymous logon I keep getting error 38 and SQL profiler shows the following: Error: 18456, Severity: 14, State: 38. 2015-01-28 12:59:27.34 Logon Login failed for user 'NordenDevel'. Reason: Failed to open the explicitly specified database. [CLIENT: 82.71.5.169] This user (NordenDevel) login works on this database (NordenWeb) in SQL Server Management Studio and in Visual Studio, so the database is working fine and I do not see how it could be a permission issue. Can anyone suggest what I could do to find out what's wrong? Many thanks, YAOWSC sql-server-2008-r2 security logins share|improve this question edited Jan 29 '15 at 15:27 marc_s 5,41632743 asked Jan 28 '15 at 18:42 YAOWSC 111 marked as duplicate by Shawn Melton, Philᵀᴹ, RolandoMySQLDBA, Paul White♦, dezso Jan 29 '15 at 6:01 This question was marked as an exact duplicate of an existing question. 1 Check that login's default database - I bet it's not NordenWeb. Or, somehow, Access is specifying a different database. –Aaron Bertrand♦ Jan 28 '15 at 18:44 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote As mentioned by Aaron, you're login 'say' X would be pointing to a different database rather than NordenWeb, when it throws error with state 38: You need to check the login for any other mapped databases. To find correct
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, login valid but database unavailable (or login not permissioned) different State numbers associated with the error can mean different reasons for the failure.
Sql Error 18456 Severity 14 State 5
One of the error States is 38, which was added with SQL Server 2008, means the database being accessed cannot
Error: 18456, Severity: 14, State: 8.
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 determine which database is causing the http://dba.stackexchange.com/questions/90445/login-failed-for-user-error-18456-severity-14-state-38 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 '
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error: 18456, Severity: 14, State: 38. Login failed for user '****'. Reason: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/a2af6e15-3d3c-4be7-8f4f-1c616bf74d7c/error-18456-severity-14-state-38-login-failed-for-user-reason-failed-to-open-the?forum=sqldataaccess Failed to open the explicitly specified database. SQL Server > SQL Server Data Access Question 0 Sign in to vote Is it Possible to Obtain that Database Name which was specified explicitly on this login failure? Just want to know about that database name. Is it possible? Curious... PGupta Friday, April 18, 2014 9:30 AM Reply | Quote Answers 0 Sign in to error 18456 vote You need to trace the server using SQL Server Profiler Trace. Refer http://mssqltalks.wordpress.com/2013/02/25/how-to-audit-login-to-my-sql-server-both-failed-and-successful/ It seems like the the error that you are refering is from SQL serverlog. Regards, RSingh Edited by Ch. Rajen Singh Friday, April 18, 2014 11:10 AM Marked as answer by Fanny LiuMicrosoft contingent staff, Moderator Monday, April 28, 2014 9:35 AM Friday, April 18, 2014 11:05 AM Reply | error 18456 severity Quote 0 Sign in to vote Yes, it is from the sql server log. Profiler trace will tell about the events which ocured during trace run. But I want to know that is it possible to know about the database for which login has failed already? perhaps I am not vague. PGupta Try the below link, it would help you to identify the database: http://www.mssqltips.com/sqlservertip/2581/sql-server-error-18456-finding-the-missing-databases/ Proposed as answer by Prashanth Jayaram Friday, April 18, 2014 2:54 PM Marked as answer by Fanny LiuMicrosoft contingent staff, Moderator Monday, April 28, 2014 9:35 AM Friday, April 18, 2014 12:20 PM Reply | Quote All replies 0 Sign in to vote You need to trace the server using SQL Server Profiler Trace. Refer http://mssqltalks.wordpress.com/2013/02/25/how-to-audit-login-to-my-sql-server-both-failed-and-successful/ It seems like the the error that you are refering is from SQL serverlog. Regards, RSingh Edited by Ch. Rajen Singh Friday, April 18, 2014 11:10 AM Marked as answer by Fanny LiuMicrosoft contingent staff, Moderator Monday, April 28, 2014 9:35 AM Friday, April 18, 2014 11:05 AM Reply | Quote 0 Sign in to vote Yes, it is from the sql server log. Profiler trace wi