Error 18456 Severity 14 State 38 Msdn
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) 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 SQL Server > SQL Server Database
Error 18456 Severity 14 State 38 Nt Authority System
Engine Question 0 Sign in to vote Hi, I am using SQL error 18456 severity 14 state 38 sql 2008 r2 Server 2012. I find below messages popping up in my error log after every minute. Login Failed for user sql server error 18456 severity 14 state 38 "domain\abc": Reason failed to open the explicitly specified database AAZ [Client XXXXXX]. Error 18456 Severity 14 State 38. But this database AAZ does not exist. Even I start SQL Profiler, but
Error 18456 Severity 14 State 38 Login Failed
could not get any sufficient information on it. Pleas suggest. Regards Edited by biltz Wednesday, December 03, 2014 5:18 AM Wednesday, December 03, 2014 5:17 AM Reply | Quote Answers 0 Sign in to vote The database (AAZ) could be specified in the connection string, or selected in the Options > Connection Properties tab of the SSMS connection dialog, is no longer valid
Error 18456 Severity 14 State 11
or online (it might be set to AutoClose or the user may simply not have permission). or change the login's("domain\abc") default database using ALTER LOGIN http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx Proposed as answer by Michelle LiModerator Thursday, December 04, 2014 2:13 AM Marked as answer by Lydia ZhangMicrosoft contingent staff, Moderator Wednesday, December 10, 2014 1:33 AM Wednesday, December 03, 2014 7:17 AM Reply | Quote All replies 0 Sign in to vote The database (AAZ) could be specified in the connection string, or selected in the Options > Connection Properties tab of the SSMS connection dialog, is no longer valid or online (it might be set to AutoClose or the user may simply not have permission). or change the login's("domain\abc") default database using ALTER LOGIN http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx Proposed as answer by Michelle LiModerator Thursday, December 04, 2014 2:13 AM Marked as answer by Lydia ZhangMicrosoft contingent staff, Moderator Wednesday, December 10, 2014 1:33 AM Wednesday, December 03, 2014 7:17 AM Reply | Quote 0 Sign in to vote So what is the problem? That an application is not working? Or you are annoyed by these error messages? I assume it i
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » Backups » Error: 18456, Severity: 14, State: 38. Error: 18456, Severity: 14, State: error 18456 severity 14 state 11 nt authority anonymous logon 38. Rate Topic Display Mode Topic Options Author Message ravishankar.yedotiravishankar.yedoti Posted Tuesday, September 6, 2011
Error 18456 Severity 14 State 5
6:42 AM Grasshopper Group: General Forum Members Last Login: Thursday, July 2, 2015 1:10 AM Points: 20, Visits: 202 I am getting the error 18456 severity 14 state 5 login failed for user below error on sql 2008. can some one help me with this. This msg pops up every 1 min in the errorlog. Logon Error: 18456, Severity: 14, State: 38.Logon Login failed for user ''CORP\s-pspadmin'. Reason: Failed to open https://social.msdn.microsoft.com/Forums/sqlserver/en-US/62ad41f8-9563-4039-86e2-b1f2138f24ee/error-18456-severity-14-state-38?forum=sqldatabaseengine the explicitly specified databasebut this login has permissions and he is the owner of the database Post #1170331 Ninja's_RGR'usNinja's_RGR'us Posted Tuesday, September 6, 2011 6:48 AM SSC-Insane Group: General Forum Members Last Login: Wednesday, April 13, 2016 12:23 AM Points: 20,643, Visits: 9,671 Check if the user has access to master.It's most likely a monitoring app or service that doesn't specify the 3rd party db in the connection string and then does use db or select db.dbo.table. http://www.sqlservercentral.com/Forums/Topic1170331-357-1.aspx Post #1170342 Roy ErnestRoy Ernest Posted Tuesday, September 6, 2011 7:05 AM SSCrazy Group: General Forum Members Last Login: Tuesday, October 4, 2016 11:55 AM Points: 2,381, Visits: 6,849 Here is another case with the same Domain having the same problem. This is bad news. As per blog by MSDN, any error state higher than 18 might require help from CSS. Check this blog out. -Roy Post #1170360 ravishankar.yedotiravishankar.yedoti Posted Tuesday, September 6, 2011 10:16 AM Grasshopper Group: General Forum Members Last Login: Thursday, July 2, 2015 1:10 AM Points: 20, Visits: 202 how to check ... whether he has access to master or not by using sp_helplogins or what Post #1170573 ravishankar.yedotiravishankar.yedoti Posted Tuesday, September 6, 2011 10:20 AM Grasshopper Group: General Forum Members Last Login: Thursday, July 2, 2015 1:10 AM Points: 20, Visits: 202 ravishankar.yedoti (9/6/2011)I am getting the below error on sql 2008. can some one help me with this. The domain account is a sysadmin on the server. This msg pops up every 1 min in the errorlogLogon Error: 18456, Severity: 14, State: 38.Logon Login failed for user ''CORP\s-pspadmin'. Reason: Failed to open the explicitly specified databasehis login is exist and he is the owner of the db Post #1170575 Roy ErnestRoy Ernest Posted Tuesday, September 6, 2011 10:23 AM SSCrazy Group: General Forum Members Last Login: Tuesday, October 4, 2016 11:55
= 18456 Output: Login failed for user ‘%.*ls'.%.*ls%.*ls This is one of the infamous error message (and number) that most of the DBAs and developers have come across while working on SQL server. This message simply denotes that the client call was able to reach the http://sql-articles.com/articles/troubleshooting/troubleshooting-login-failed-error-18456/ SQL server and then an ACCESS was denied to the particular login for a reason. To figure out the exact reason, this error number 18456 with its STATE number is logged into the SQL server error log file, if SQL server was allowed or configured to capture the failed logins. Configuring SQL server for capturing login failures: By default, SQL server is configured to capture only failed logins but it can be changed to any of the options error 18456 as mentioned in this books online link http://technet.microsoft.com/en-us/library/ms188470.aspx Below figure shows these options to have login failed messages written into error log Accessing Error log: Now that, we know SQL server logs all login failed messages into its error log and windows event viewer but how do I access them? Windows event viewer: GO to start –> Run –> Eventvwr –> open up the application logs, and now we could see the login failed error message with computer name, error 18456 severity instance name, date and time and finally the reason for the login failed SQL Error log: SQL server error log can be viewed from multiple places If we have gained access or can gain access to SQL server with different logon credentials then always use sp_readerrorlog, xp_readerrorlog or use the GUI option of opening up Management node –> SQL server Logs –> View –> SQL server log. Same sample shown above looks like In a case where we cannot gain access to SQL server, then we may use the actual error log path and open the txt file physically from the file system. Use SQL server configuration manager to find the error log path and from there you could open the file. Get the value next to –e parameter and that gives the actual error log file location Typically the error log files are available in install directory for SQL server. SQL server 2005: C:\MSSQL\MSSQL.1\MSSQL\LOG\Errorlog SQL server 2008: C:\MSSQL\MSSQL10.instanceID\MSSQL\Log\Errorlog InstanceID - MSSQLSERVER for default instance and for named instance it’s the name of the instance STATES of 18456 State 1: This is a very generic error message that is sent to the client tools to deliberately hide the nature of the login failure issue. However, the SQL Server error log, a corresponding error contains an error state that maps to an authentication failure condition with its state number. State 2 and 5: This stat