Ms Sql 2008 Error 18456 Severity 14 State 38
Contents |
SQL Server experts to answer whatever question you can come up with. Our new
Error 18456 Severity 14 State 38 Sql 2008 R2
SQL Server Forums are live! Come on over! We've restricted the error 18456 severity 14 state 38 nt authority system ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members 'login valid but database unavailable (or login not permissioned)' | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums SQL Server 2008 Forums Other SQL Server 2008
Sql Error 17054 Severity 16 State 1
Topics error: 18456, severity: 14, state: 38 Reply to Topic Printer Friendly Author Topic LawnMowerPros Starting 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
Error 18456 Severity 14 State 1
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 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.Con
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 sql server error 18456 severity 14 state 58 the error can mean different reasons for the failure. One of the error States is
Error 17187 Severity 16 State 1
38, which was added with SQL Server 2008, means the database being accessed cannot be found or does not exist. Unfortunately the sql error 18456 severity 14 state 5 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 error message. Solution A few days ago I was looking http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=121202 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 '
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) 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: 38 SharePoint https://social.technet.microsoft.com/Forums/sharepoint/en-US/fe709703-9def-46fb-8455-8f76d0b7578d/login-failed-error-18456-severity-14-state-38?forum=sharepointadminprevious > SharePoint 2010 - Setup, Upgrade, Administration and Operations Question 0 Sign in to vote I've done as much searching on the web as I can to try to http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx 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 R2. The error from error 18456 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 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 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 the other contained databases in case you match there - I hope you agree that this is a good thing). If you don't specify a database in your connection string, then it won't s