Re: SQL Service stops and restarts - no failover occures.
From: Geoff N. Hiten (SRDBA_at_Careerbuilder.com)
Date: 11/20/04
- Next message: Danny: "Re: Installing SQL to a SAN"
- Previous message: Chris: "SQL Service stops and restarts - no failover occures."
- In reply to: Chris: "SQL Service stops and restarts - no failover occures."
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 19 Nov 2004 20:16:53 -0500
That is a cluster service failure detection. CheckQueryProcessorAlive is
the long name for the cluster IsAlive function. The restart on the same
node is due to two factors. First, no underlying resources went offline.
Second, the existing host node is likely the first node in the preferred
nodes list.
For some reason, your SQL server isn't responding to the query. Most times
when I have seen this (your cause may be different) it is due to an earlier
Access Violation error that blew something within SQL. The original failure
may be several hours earlier. Look through the SQL logs directory to find
the last minidump before the crash. Check that time in the host node
application event logs to see what went boom. You may be able to match that
up with an existing KB article and appropriate hotfix.
-- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org "Chris" <Chris@discussions.microsoft.com> wrote in message news:A0EE8124-1873-480A-B0E9-F690C14F0738@microsoft.com... > > Win2003 SQL2000 Active/Active > > On node1 SQL service shuts down and immediately restarts. In the cluster log > on node1 we found the following below at exact time of service stop/start. > Why would a failover not have occured? > > Why is CheckQueryProcessorAlive prefixed with ERR SQL Server..., this must > not be part of the cluster service checking node if IsAlive, correct? What is > this? > > Thanks in advance for any insight... > > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; > message = [Microsoft][ODBC SQL Server Driver]Timeout expired > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] OnlineThread: QP is not online. > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; > message = [Microsoft][ODBC SQL Server Driver]Communication link failure > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; > message = [Microsoft][ODBC SQL Server Driver]Communication link failure > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; > message = [Microsoft][ODBC SQL Server Driver]Communication link failure > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; > message = [Microsoft][ODBC SQL Server Driver]Communication link failure > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed > 000009e8.00000f70::2004/11/19-16:09:33.840 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; > message = [Microsoft][ODBC SQL Server Driver]Communication link failure > 00000518.000009fc::2004/11/19-16:09:52.972 INFO [FM] NotifyCallBackRoutine: > enqueuing event > 00000518.00000794::2004/11/19-16:09:52.987 INFO [CP] CppResourceNotify for > resource SQL Server (IHSCDATA) > 00000518.00000794::2004/11/19-16:09:53.003 INFO [CP] CppRundownCheckpoints > removing RNB for Software\Microsoft\Microsoft SQL Server\IHSCDATA\Setup > 00000518.00000794::2004/11/19-16:09:53.003 INFO [CP] CppRundownCheckpoints > removing RNB for Software\Microsoft\Microsoft SQL Server\IHSCDATA\SQLServerSCP > 00000518.00000794::2004/11/19-16:09:53.003 INFO [CP] CppRundownCheckpoints > removing RNB for Software\Microsoft\Microsoft SQL Server\IHSCDATA\PROVIDERS > 00000518.00000794::2004/11/19-16:09:53.003 INFO [CP] CppRundownCheckpoints > removing RNB for Software\Microsoft\Microsoft SQL Server\IHSCDATA\MSSQLSERVER > 00000518.00000794::2004/11/19-16:09:53.003 INFO [CP] CppRundownCheckpoints > removing RNB for Software\Microsoft\Microsoft SQL Server\IHSCDATA\Cluster > 00000518.00000794::2004/11/19-16:09:53.003 INFO [CP] CppRundownCheckpoints > removing RNB for Software\Microsoft\Microsoft SQL > Server\IHSCDATA\SQLserverAgent > 00000518.00000794::2004/11/19-16:09:53.003 INFO [CP] CppRundownCheckpoints > removing RNB for Software\Microsoft\Microsoft SQL Server\IHSCDATA\Replication > 00000518.00000794::2004/11/19-16:09:53.003 INFO [CP] CppRundownCheckpoints > removing empty group > 00000518.000007a8::2004/11/19-16:09:53.018 WARN [FM] > FmpHandleResourceTransition: Resource Name = > 115b224b-0925-498b-a5a8-7d2c988e8964 [SQL Server (IHSCDATA)] old state=2 new > state=4 > 00000518.000007a8::2004/11/19-16:09:53.018 INFO [GUM] GumSendUpdate: queuing > update type 0 context 8 > 00000518.000007a8::2004/11/19-16:09:53.018 INFO [GUM] GumSendUpdate: > Dispatching seq 30031 type 0 context 8 to node 1 > 00000518.000007a8::2004/11/19-16:09:53.018 INFO [GUM] GumSendUpdate: > completed update seq 30031 type 0 context 8 > 00000518.000007a8::2004/11/19-16:09:53.018 INFO [FM] > FmpPropagateResourceState: resource 115b224b-0925-498b-a5a8-7d2c988e8964 > failed event. > 00000518.000007a8::2004/11/19-16:09:53.018 INFO [FM] > FmpHandleResourceFailure: taking resource > 115b224b-0925-498b-a5a8-7d2c988e8964 and dependents offline > 00000518.000007a8::2004/11/19-16:09:53.018 INFO [FM] TerminateResource: > df5746e5-0710-4e39-a33d-7c148c2d5e8f depends on > 115b224b-0925-498b-a5a8-7d2c988e8964. Terminating first > 000009e8.00000f70::2004/11/19-16:09:54.519 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] ODBC sqldriverconnect failed > 000009e8.00000f70::2004/11/19-16:09:54.535 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error > = b; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network > error. Check your network documentation. > 000009e8.00000f70::2004/11/19-16:09:54.535 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] ODBC sqldriverconnect failed > 000009e8.00000f70::2004/11/19-16:09:54.535 ERR SQL Server <SQL Server > (IHSCDATA)>: [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error > = 102; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen > (PreLoginHandshake()).
- Next message: Danny: "Re: Installing SQL to a SAN"
- Previous message: Chris: "SQL Service stops and restarts - no failover occures."
- In reply to: Chris: "SQL Service stops and restarts - no failover occures."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|