Error 18456 Severity 14 State 38 Sql Server 2012
Contents |
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come on over! error 18456 severity 14 state 38. sql server 2008 r2 We've restricted the ability to create new threads on these forums. SQL Server
Sql Server 2012 Error 18456 Severity 14 State 1
Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password:
Sql Server Error 18456 Severity 14 State 5
Save Password Forgot your Password? All Forums SQL Server 2008 Forums Other SQL Server 2008 Topics error: 18456, severity: 14, state: 38 Reply to Topic Printer Friendly Author Topic LawnMowerPros Starting
Error 18456 Severity 14 State 11 Sql 2008 R2
Member USA 9 Posts Posted-03/06/2009: 23:06:31 I'm using SQL Server Express 2008 and I keep seeing this error (error: 18456, severity: 14, state: 38) in my log files. The error repeats many, many, many times and then the database goes into recovery mode. Can someone tell me what the error means?ThanksH and H Lawncare Equipmenthttp://www.LawnMowerPros.com guptam Posting Yak Master Canada 161 Posts error 18456 severity 14 state 38 nt authority system Posted-03/06/2009: 23:25:40 State 38 means user doesn't have access to database it is trying to connect to.-- Mohit K. GuptaB.Sc. CS, Minor JapaneseMCITP: Database AdministratorMCTS: SQL Server 2005http://sqllearnings.blogspot.com/ LawnMowerPros Starting Member USA 9 Posts Posted-03/06/2009: 23:33:40 Thank you Mohit. I'm accessing the server using Classic ASP, what should I set the permission level to?Thanks Again.H and H Lawncare Equipmenthttp://www.LawnMowerPros.com guptam Posting Yak Master Canada 161 Posts Posted-03/07/2009: 02:46:54 What is your connection string? In your Connection string what ever database you have there user must have access to be able to at least read in that database. Thanks.-- Mohit K. GuptaB.Sc. CS, Minor JapaneseMCITP: Database AdministratorMCTS: SQL Server 2005http://sqllearnings.blogspot.com/ LawnMowerPros Starting Member USA 9 Posts Posted-03/07/2009: 18:04:50 My connection string is:Dim objConnSet objConn = Server.CreateObject("ADODB.Connection")objConn.ConnectionString = "Provider=SQLOLEDB;server=SERVER;database=DATABASE;uid=USERNAME;pwd=PASSWORD;"objConn.OpenI need read, write, delete. In the SQL Server Mangement screen I actually have permissions set to sysadmin. So I'm confused why I'd be getting the State 38 error.Thank you for your help.H and H Lawncare Equipmenthttp://www.LawnMowerPros.com guptam Posting Yak Master Canada 161 Posts Posted-03/07/2009: 18:29:25 You
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Login Failed Error: 18456, Severity: 14 State: sql server 2012 error 18456 windows authentication 38 SharePoint > SharePoint 2010 - Setup, Upgrade, Administration and Operations error 18456 sql server 2012 solucion Question 0 Sign in to vote I've done as much searching on the web as I can error 18456 severity 14 state 11 nt authority anonymous logon to try to find a solution to this error, however it seems that my particular case is a bit more unique. We are running SharePoint 2010 with SQL 2008 http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=121202 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:
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 https://justaprogrammer.net/2012/12/09/a-misleading-sql-error-message-error-18456-severity-14-state-38/ took me a while to troubleshoot the error. The client's internal system administrator (who http://www.ssistalk.com/2011/05/06/quick-tip-error-18456-severity-14-state-38/ 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 error 18456 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 error 18456 severity 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
to see if a record exists Dynamic connection for file system task Ads Quick Tip: Error: 18456, Severity: 14, State: 38. SQL Server, SQL Server 2008 May 062011 When trying to investigate the SQL error, "Error: 18456, Severity: 14, State: 38." it can be frustrating when not a single log on the system will tell you what the actual problem is. In the case of state 38 (16 or 27 prior to SQL 2008) this error means the database specified in the client connection does not exist, or is offline. In a large shop with many various clients it can be hard to find out the source of the connection, so you're option is to use the tools at your disposal. The SQL Error Log does not help much at all. Here's what's in the SQL Error log: 2011-05-06 09:06:17.28 Logon Error: 18456, Severity: 14, State: 38. 2011-05-06 09:06:17.28 Logon Login failed for user ‘DOMAIN\ssrs.service'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.147] The Windows Application log is not much help either. Login failed for user ‘DOMAIN\ssrs.service'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.147] In other words, useless for troubleshooting. The way to obtain the database name the client is trying to connect to is to use SQL Server Profiler. To set up SQL Server Profiler, connect to the SQL instance where the error is occuring and then track the following events: Errors and Warnings: User Error Message Security Audit: Audit Login Failed For these two events, make sure you capture at least the following columns: ApplicationName, HostName, LoginName, SPID (required), StartTime, TextData (where the message text will be), Severity, State, ClientProcessID, and Error. Then run the trace. You'll see the following data under the "User Error Message" event when the login failure occurs: Ca