Error 18456 Severity 14 State 38 Mirroring
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 error 18456 severity 14 state 38 nt authority system Us Learn more about Stack Overflow the company Business Learn more about hiring error 18456 severity 14 state 38 sql 2008 r2 developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange sql server error 18456 severity 14 state 38 is 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 38 Login Failed
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 up vote 12 down vote favorite 4 Message that SQL Server Log File Viewer shows: Login failed for user [User] Error: 18456, Severity: 14, State 38 What it actually means: Failed to open the error 18456 severity 14 state 11 explicitly specified database My Question: Is there a list somewhere of all the variations of the 18456 errors (Login failed), for each combination of severity and state, with the helpful description text? I've had a Google but can't find anything other than specific combinations. sql-server errors logins share|improve this question asked Nov 30 '12 at 16:30 Pete Oakey 2841210 add a comment| 2 Answers 2 active oldest votes up vote 11 down vote State codes and their meaning. 1 'Account is locked out' 2 'User id is not valid' 3-4 'Undocumented' 5 'User id is not valid' 6 'Undocumented' 7 'The login being used is disabled' 8 'Incorrect password' 9 'Invalid password' 10 'Related to a SQL login being bound to Windows domain password policy enforcement. See KB925744.' 11-12 'Login valid but server access failed' 16 'Login valid, but not permissioned to use the target database' 18 'Password expired' 27 'Initial database could not be found' 38 'Login valid but database unavailable (or login not permissioned)' More detailed information is available in Aaron Bertrand's blog. share|improve this answer edited Dec 1 '12 at 13:27 answered Nov 30 '12 at 16:33 Pete Oakey 2841210 5 A LOT more det
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: SQL 2k8 R2 Mirroring : Unable to access Mirror after succesful initial test and failover with error failed error 18456 severity 14 state 11 nt authority anonymous logon to open the explicitly specified database SQL Server > Database Mirroring Question 0
Error 18456 Severity 14 State 5
Sign in to vote Hello there, I would need your advice, if possible. I have used an application setup
Error 18456 Severity 14 State 5 Login Failed For User
for creating 2 database on SQL 2k8 R2 Ent sp2. One of them uses TDE, DB_A. Also, this part of the setup creates a local group GROUP1 on 2k8 server that has as http://dba.stackexchange.com/questions/29613/login-failed-for-user-error-18456-severity-14-state-38 members Network Service and the computer where will be setup the application which will access the database, COMP1. So, member DOM\COMP1. This group is used to access and modify the database as per read/write. The second part of the setup is ran on another server (COMP1) and will install the application (IIS) that will write keys to tables on DB_A. I have mirrored it with witness (Express https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9dbe740d-7c4f-4b45-bf57-e3fa62a23e7c/sql-2k8-r2-mirroring-unable-to-access-mirror-after-succesful-initial-test-and-failover-with-error?forum=sqldatabasemirroring 2k8 R2 sp3 advanced) and mirroring was fine (exporting certificate, keys etc.) Then, to be able to generate the same logins, I have manually created a local group, GROUP2 on 2k8 and put the members same Network Service and COMP1, even PRINCIPLE. The rest of the logins were the same. To keep the same logins and because the mirrored database doesn't allow to be accessed, I had failover the mirror and create the logins as per initially on Principle. I have also used the export logins procedure described by MS. As MS site says, if the first logon to the principle will succeed, the application cache will be updated with the mirror address and after that, if the failover will occur, application will be capable to switch automatically and the client will be able to use the name of failover partner(database). So, I run the client successfully and the databases were updated. At this point, I supposed the internal cache was ok, updated with mirror name. Then, I failover the databases. When the application tried to connect again I had the error: "Login failed for user DOM\COMP1: Reason Failed to open the explicitly specified database (CLIENT 10.1...)" on the i
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » http://www.sqlservercentral.com/Forums/Topic1064879-1549-1.aspx SQL Server 2008 » SQL Server 2008 High Availability » Database mirroring login failure Database mirroring login failure Rate Topic Display Mode Topic Options Author Message chandan_jha18chandan_jha18 Posted Wednesday, https://community.spiceworks.com/topic/462996-need-help-finding-the-permissions-issue-in-this-sql-connection February 16, 2011 5:35 AM SSC-Addicted Group: General Forum Members Last Login: Thursday, October 6, 2016 4:35 AM Points: 485, Visits: 2,128 I have configured database mirroring between two error 18456 servers at a distance 40 miles away from each other.Server specifications: SQL Server 2008,Standard Edition 64-bitThis is same for principal,mirror and witness. The configuration is high-safety with automatic failoverInitially we tested our .net application(web application) on both the principal and mirror and made sure that the login is not orphaned.Things run fine generally.But sometimes on the mirror server,I see error 18456 severity login failed attempts:Login failed for user 'd0main\user'. Reason: Failed to open the explicitly specified database. [CLIENT: xx.xx.x.x] Message Error: 18456, Severity: 14, State: 38.This error appears 3-4 times a day but not more than that.My question to the experts is:If the principal is alive so why the application tries to connect to mirror.The default time-out for a .net webpage is 30 seconds,so is it possible that the application tries to connect principal and after 30 seconds even if principal is alive,it assumes that it is dead and thus tries to open a connection to mirror where it fails.Please help me with this problem. Post #1064879 Satish NagarajaSatish Nagaraja Posted Tuesday, February 22, 2011 5:01 AM SSC-Enthusiastic Group: General Forum Members Last Login: Friday, April 15, 2016 1:55 AM Points: 172, Visits: 308 Is this domain user part of SYSADMIN or Local Administrator group of mirror server ? Verify if this user is part of WITNESS\PRINCIPAL not added to MirrorCheersSat Cheer Satish Post #1067513 chandan_jha18chandan_jha18 Posted Tuesday, February 22, 2011 7:33 AM SSC-Addicted Group: Gener
only takes a few minutes. Join Now We run The Financial Edge, from Blackbaud, as our accounting package. The latest install package uses MS SQL 2008 R2 SP2 and we've been running it on a Server 2003 box. I recently installed Server 2003 in a VM and installed the FE package from scratch. Shut down the original FE services, copied over the single database and .ldf file and attached it in the new server. The only real pain point (annoyance, really) is that you have to reinstall the client software from the new server for it connect to that server. I've done this twice before (moving to a new machine) and it's always worked fine. And this time it works fine - if you have domain admin privileges. When regular user launches the shortcut they get a pair of errors, first a box that says BB140810 is just a generic check-list of user name rules, SQL versions, IP addressing, DNS problems, etc. Standard network connectivity stuff. Then when you click Ok: So here it is. If I put the users into the Domain Admins group they connect immediately. Otherwise they get this error. Bear in mind, they don't get this error when logging into the app. This occurs when the shortcut is launched - they never see a login window. I've compared folder permissions, registry key permissions, Component Services COM Security, any little thing I can think of. Blackbaud tech support has been very nice, but zero help. Any one have any other ideas where to look? Reply Subscribe View Best Answer RELATED TOPICS: SQL Connection from PHP Remove SQL Instance   18 Replies Chipotle OP GlenW Mar 25, 2014 at 2:58 UTC I would take a look at this http://blogs.msdn.com/b/selvar/archive/2007/11/10/odbc-tracing.aspx In addition I would also run a SQL Trace (Profiler) on the server and see if a connection is being made. If it is then that should offer further clues. EDIT: What is the default database of the login set to? 0 Datil OP Mike4003 Mar 25, 2014 at 3:10 UTC GlenW wrote:EDIT: What is the default database of the login set to?I don't even know h