Error 18456 Login Failed For User 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 sql server error 18456 login failed for user sqlstate 28000 company Business Learn more about hiring developers or posting ads with us Database Administrators Questions
Error 18456 Login Failed For User Sa
Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish login failed for user error 18456 sql server authentication 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 are
Login Failed For User Error 18456 Windows Authentication
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 I keep getting error login failed for user error 18456 sql server 2012 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 error you need to enable the trace
Server Login Failures By Pinal DaveWhen asked about common errors encountered in a SQL Server environment, you might expect to hear about high
Login Failed For User Error 18456 Sql Server 2014
CPU issues, but in reality, these are rare and few. In fact,
Login Failed For User Error 18456 Sql Server 2008 R2
many DBAs report connectivity issues with SQL Server as among the most frequently encountered errors. These errors can further be classified sql server error 18456 login failed for user 'nt authority system' into two sub-categories: Login request not reaching SQL Server. Login request reaching SQL Server and then failing. Let's look at each of these scenarios in this article. Scenario 1: Login http://dba.stackexchange.com/questions/90445/login-failed-for-user-error-18456-severity-14-state-38 request not reaching SQL Server A typical error received by a client might be: Transact-SQL A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections 1 A network-related or http://logicalread.solarwinds.com/errors-sql-server-login-failures-pd01/ instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections There can be multiple reasons for this error, including these, based on work I've done with clients and queries I've responded to in user forums: Using the incorrect instance name. The SQL Service is not running. Port not open. (Note that telnet is the best test possible to detect this). The SQL Browser Service not running. (This is needed to get port of named instances. IP, PortNumber - can be specified to identify this issue.) Incorrect DNS entry and request going to different machine. (Note that ping is the best test to find name and IP address mapping). Scenario 2: Login request reaching SQL Server and then failing This second scenario results from authentication or security related errors. The error message received by the client would as shown below: Transact-SQL Login failed for user 'username'. (Microsoft SQL Server, Er
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered 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 by: Error: 18456, Severity: 14, State: 38. Login failed for user '****'. Reason: Failed to open the explicitly specified database. SQL Server > SQL http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx 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? error 18456 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 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 login failed for 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 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
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 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 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 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 pa