Error 138a Bringing Resource Online
Contents |
360 games PC games cluster resource failed 1069 Windows games Windows phone games Entertainment All Entertainment cluster resource sql server failed Movies & TV Music Business & Education Business Students & educators
Event Id 1069 Cluster Resource Sql Server Failed
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Sql Server Cluster Resource State Check Failed
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All [sqsrvres] onlinethread: resutilsstartresourceservice failed (status 435) Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
halt all my activities I get a call from Office stating that one of the SQL Server 2005 resource on a Windows 2003 Cluster was not coming online. I logged on to the server and
[sqagtres] Onlinethread: Resutilsstartresourceservice Failed (status 435)
checked the logs. The System Event Log did not have much information except for cluster resource 'sql server' of type 'sql server' in clustered role failed this error. I had posted about this error sometime back, when one of the DR instances was not coming starting. I did the cluster resource sql server could not be brought online not find any value in increasing the timeout value on this instance since there was hardly any activity on this instance and the resource utilization was minimum. The SQL Server Error Log had the following messages. Using https://support.microsoft.com/en-us/kb/883732 dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.
This is an informational message only. No user action is required.
Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC).
This is an informational message only. No user action is required.
Service control: stop before startup This error message was not much useful in finding out the root cause. Then I checked the Cluster http://www.sqldbadiaries.com/2011/01/25/sql-server-cluster-resource-doesnt-come-online-service-control-stop-before-startup/ Log (c:\windows\cluster\cluster.log) ERR SQL Server : [sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 5b4)
ERR SQL Server : [sqsrvres] OnlineThread: Error 5b4 bringing resource online. I had posted here on how to get meaningful information from the hexadecimal error codes in the Cluster Log. Error 5b4 means this operation returned because the timeout period expired. Since this error message was also related to timeout, it was not much useful. After a while I saw this error message in the System Event Log. Severity: 16 Error:2, OS: 2 [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2] This made it clear that the Cluster Manager was not able to connect to the SQL Server instance using Named pipes while trying to start it. Quickly checked if the Named Pipes protocol was disabled in SQL Server Configuration Manager. It was not. Then I started SQL Server from the command prompt using sqlservr.exe, there were no errors reported and all the databases came online. With the sqlservr.exe running in another window, I was able to connect to the SQL Server instance through SSMS using both the Instance Name and Pipes. This confirmed that there were no issues with SQL Server, only the Operating System was not able to connect to the Instance. By this time, this issue was al
November 2015 (4) October 2015 (1) August 2015 (1) June 2015 (1) May 2015 (2) February 2015 (1) January 2015 (2) December 2014 (1) http://www.haidongji.com/2006/12/13/troubleshoot-sql-server-cluster-and-clusterrecovery/ August 2014 (2) July 2014 (2) June 2014 (2) April 2014 (2) March 2014 (1) February 2014 (2) January 2014 (1) December 2013 (1) November 2013 (2) October 2013 (1) September https://www.experts-exchange.com/questions/24425173/SQL-server-and-SQL-agent-will-not-start-on-both-nodes-in-Active-to-Active-SQL-2005-SP3-x64-Enterprise-cluster-on-Windows-2008-x64-after-applying-KB958644.html 2013 (2) July 2013 (2) May 2013 (1) April 2013 (1) February 2013 (1) November 2012 (3) October 2012 (4) September 2012 (2) August 2012 (1) May 2012 (2) April 2012 cluster resource (1) March 2012 (6) February 2012 (6) January 2012 (1) December 2011 (2) November 2011 (2) September 2011 (1) August 2011 (1) July 2011 (2) June 2011 (4) May 2011 (4) April 2011 (7) March 2011 (6) February 2011 (4) January 2011 (6) December 2010 (7) October 2010 (10) September 2010 (8) August 2010 (2) July 2010 (2) June 2010 (2) May 2010 cluster resource sql (5) April 2010 (2) March 2010 (3) February 2010 (1) January 2010 (4) December 2009 (1) November 2009 (4) October 2009 (3) September 2009 (7) August 2009 (1) July 2009 (2) June 2009 (4) May 2009 (5) April 2009 (5) March 2009 (3) February 2009 (5) January 2009 (9) December 2008 (10) November 2008 (6) October 2008 (7) September 2008 (11) August 2008 (6) July 2008 (9) June 2008 (5) May 2008 (5) April 2008 (7) March 2008 (8) February 2008 (5) January 2008 (11) December 2007 (4) November 2007 (5) October 2007 (8) September 2007 (7) August 2007 (4) July 2007 (6) June 2007 (6) May 2007 (4) April 2007 (2) March 2007 (7) February 2007 (10) January 2007 (17) December 2006 (8) November 2006 (7) October 2006 (8) September 2006 (6) August 2006 (9) July 2006 (12) June 2006 (9) May 2006 (11) April 2006 (14) March 2006 (10) February 2006 (11) January 2006 (18) December 2005 (16) November 2005 (21) October 2005 (14) Recent CommentsHaidong Ji on Accessing modem status information with Netgear routerJie on Identify a proxy when automatic configuration script is use
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > SQL server and SQL agent will not start on both nodes in Active to Active SQL 2005 SP3 x64 Enterprise cluster on Windows 2008 x64 after applying KB958644 Want to Advertise Here? Solved SQL server and SQL agent will not start on both nodes in Active to Active SQL 2005 SP3 x64 Enterprise cluster on Windows 2008 x64 after applying KB958644 Posted on 2009-05-20 Windows OS Windows Server 2008 MS SQL Server 2005 3 Verified Solutions 9 Comments 2,083 Views Last Modified: 2013-11-29 Hello, Apologies if this has already been posted but I cannot find it anywhere. My SQL server and SQL agents will not start on both nodes in my Active / Active SQL 2005 SP3 x64 Enterprise cluster on Windows 2008 Enterprise SP1 x64 after applying KB958644 which is the conficker patch. This is the second time I have built the cluster and I tested it and it worked perfectly prior to applying the KB. Has anyone seen this issue before and do they have a fix? Basically not patching the 2 servers is a no go and I have already patched 2 separate clusters with KB958644 and they worked fine, those clusters were W2k3 R2 SP2 2 node with SQL 2005 SP2 and Windows 2008 Enterprise File and Print cluster with 5 nodes. Whats happening is all the services on both nodes come online except SQL server and sql agent. The are all connected to EMC2 sans via fibre channell cable on HP DL380 G5 with 32 gb RAM and 2 x Quad core 3 ghz CPUs. When I look in cluster event log I get