Error 18456 Severity 14 State 38. Login Failed For User
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 sql error 18456 severity 14 state 38 Us Learn more about Stack Overflow the company Business Learn more about hiring
Error 18456 Severity 14 State 38. Sql Server 2008 R2
developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is
Error 18456 Severity 14 State 38 Nt Authority System
a question and answer site for database professionals 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
Error 18456 Severity 14 State 11
it works: Anybody can ask a question Anybody can answer The 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 error 18456 severity 14 state 11 nt authority anonymous logon command in MS Access 2012 to exec a stored proc in our SQL server 2008R2 database, but 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'r
SQL Server experts to answer whatever question you can come up with. Our new login valid but database unavailable (or login not permissioned) SQL Server Forums are live! Come on over! We've restricted the sql error 18456 severity 14 state 5 ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members sql error 17054 severity 16 state 1 | 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 http://dba.stackexchange.com/questions/90445/login-failed-for-user-error-18456-severity-14-state-38 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 http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=121202 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.
Server Login Failures By Pinal DaveWhen asked about common errors encountered in a SQL Server environment, http://logicalread.solarwinds.com/errors-sql-server-login-failures-pd01/ you might expect to hear about high CPU issues, but in reality, these are rare and few. In fact, many DBAs report connectivity issues with SQL Server as among the most frequently http://sql-articles.com/articles/troubleshooting/troubleshooting-login-failed-error-18456/ encountered errors. These errors can further be classified into two sub-categories: Login request not reaching SQL Server. Login request reaching SQL Server and then failing. Let's look at each of error 18456 these scenarios in this article. Scenario 1: Login 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 error 18456 severity that SQL Server is configured to allow remote connections 1 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 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 authentic
= 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 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 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, 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.