Error 19019 Cluster
Contents |
2008 to R2 tonight. We upgraded the inactive node to R2 SP2 and then went to failover the cluster so we could upgrade event id 19019 the mssqlserver service terminated unexpectedly the other node. But when we tried to failover it failed. The
Event Id 19019 Failover
only thing the critical events for the resource said was that it couldn't failover. So no help there. event id 19019 sql server 2008 r2 The only other error was in the event viewer and it said that the shared component upgrade failed… even though nothing in the upgrade process failed. There actually were other sqsrvres odbc sqldriverconnect failed sql 2008 errors in the event viewer but I'll let the link below cover those. The big important error was Error: 19019. I remembered something from a few yrs ago that involved a registry fix so I started looking at the registry. After opening regedit I went to the most logical place: HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL10_50.SQL2008 Once there I saw the Setup folder, which
[sqsrvres] Checkqueryprocessoralive: Sqlexecdirect Failed
seemed like a good place to start. Inside there I saw a key called SQLDataRoot and its value started with E:\ Well, I have a pretty standardized environment so I know the SQL root was supposed to be on D:. I changed the location to D:\ and the SQL Server resource came online instantly. So again, that registry key is: HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL10_50.SQL2008\Setup\SQLDataRoot This is not only an interesting fix, it’s also a testament to what having a highly standardized environment can do for you. I could have compared this entry with node1 to see if they matched, but it may not have even been flagged as an issue if we didn't always install SQL on D:\. So once I had the fix in place, I had something to search for, so I went to google to see if I could find anything about it out there. I came across this great blog post that even gives more detail on this error, so rather than try to reproduce the entire thing here, I’ll just point you to that post. http://blogs.msdn.com/b/jorgepc/archive/2010/10/14/onlinethread-sql-cluster-shared-data-upgrade-failed-error-installing-cumulative-update-in-sq
27, 20081 0 0 0 There are times where all the SQL Server knowledge in the world won't help us to find a solution to our cluster problem. The following post will show you how to use the Microsoft Windows cluster log file to find the root-cause of a common SQL Server issue (it does not matter what SQL Server version we use for the purpose of http://www.midnightdba.com/DBARant/cluster-upgrade-error-19019/ this post). In this case the customer called to Microsoft PSS due to a problem in which a SQL Server 2000 clustered instance was not starting up for an unknown reason. Looking at the customer Cluster Administrator, this was the situation of the SQL Server 2000 cluster group, called "SHILOH": https://blogs.msdn.microsoft.com/jorgepc/2008/07/27/using-windows-cluster-log-to-troubleshoot-sql-server-cluster-errors/ We tried to diagnose what was wrong using the SQL Server ERRORLOG file, but we could not find any useful information there. After a few seconds online, the SQL Server service was stopped by Service Control Manager for no apparent reason: 2008-07-27 17:28:04.51 server Copyright (C) 1988-2002 Microsoft Corporation. 2008-07-27 17:28:04.51 server All rights reserved. 2008-07-27 17:28:04.51 server Server Process ID is 304. 2008-07-27 17:28:04.51 server Logging SQL Server messages in file ‘S:\Program Files\Microsoft SQL Server\MSSQL$SHILOH\log\ERRORLOG'. 2008-07-27 17:28:04.53 server SQL Server is starting at priority class ‘normal'(1 CPU detected). 2008-07-27 17:28:04.55 server SQL Server configured for thread mode processing. 2008-07-27 17:28:04.56 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks. 2008-07-27 17:28:04.57 server Attempting to initialize Distributed Transaction Coordinator. 2008-07-27 17:28:18.76 spid3 Starting up database ‘master'. 2008-07-27 17:28:19.30 server Using ‘SSNETLIB.DLL' version ‘8.0.2039'. 2008-07-27 17:28:19.32 server SQL server listening on 192.168.0.60: 1131. 2008-07-27 17:28:19.32 spid3 Server name is
of one computer, and you use it to duplicate to another, you know the other machine is going to be good. You get http://jon.netdork.net/2010/09/18/sql-cluster-failure-and-name-changes to apply all your corporate policies, security software, anti-virus, group policies, etc etc, all in one single step. With this in mind, this is what we did with some SQL clusters http://sqlserverquestions.mssqltips.com/8746/how-to-fix-mssqlserver-event-id-19019/ we built 6 months ago. The cloning went well, and the servers were successfully built, SQL deployed, and clusters setup. All was good… Until recently. At first, I didn’t notice a problem, event id then we had a hiccup with something, I connected to the server using Remote Desktop Protocol (RDP), and started poking around, and found nothing unusual. A little baffled, I poked around some more, and some things didn’t seem right to me. Then it dawned on me, I was looking at the wrong server. Disconnecting, I tried again, and ended up back on the event id 19019 same box. For some reason, DNS was pointing to the wrong server. Quickly dropping the DNS record, and adding the other server back, all was good. A few days later, the DNS issue popped up again, doing some more poking around, I discovered that the host name on the server had stayed the same as the cloned machine. For some reason, the sysprep hadn’t properly changed the name. We decided to schedule some time to change the name at a later point in time, but for now, both boxes were stable. A few days ago, the second box, with the incorrect name crashed out, no apparent reason, the cluster service just reported issues, with no specific reason. As the services had started up on the other node correctly, we left it for the night, and decided to deal with it in the morning. Whilst poking around on it the following morning, and trying to fail the SQL services over, we were bombarded by errors in the event log… 3 of them in blocks, for every second it attempted to move over the services. Log Name: Application
SQL server (instance_name) failed Post an Answer Keep it clean and stay on the subject or we may delete your comment. Your email address is not published. Required fields are marked with an asterisk (*) *Name *Email Notify for updates Comments *** NOTE *** - If you want to include code from SQL Server Management Studio (SSMS) in your post, please copy the code from SSMS and paste the code into a text editor like NotePad before copying the code below to remove the SSMS formatting. *Enter Code Sponsor Information Follow Get Free SQL Tips Twitter LinkedIn Google+ Facebook Pinterest RSS Learning DBAs Developers BI Professionals Careers Q and A Today's Tip Resources Tutorials Webcasts Whitepapers Tools Search Tip Categories Search By TipID Authors Community First Timer? Pictures Contribute Events User Groups Author of the Year More Info Join About Copyright Privacy Disclaimer Feedback Advertise Copyright (c) 2006-2016 Edgewood Solutions, LLC All rights reserved Some names and products listed are the registered trademarks of their respective owners.