Every now and then (about once a week) our SQL server cluster
(active/passive) becomes unresponsive, and the following events are logged:
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Timeout expired
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] OnlineThread: QP is not online.
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
SQL server errorlog contains these errors:
2005-08-07 07:52:16 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:16 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:52:19 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:19 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:47 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:47 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:54:27 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:55:05 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:55:05 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [382] Logon to server '(local)' failed (JobManager)
During this time, connections are terminated and SQL server does not allow
legitimate accounts to log in. it last for a couple of minutes. The server is
clearly not overloaded, and it doesn't have any specific jobs or anything to
do at this time. I would like to exclude network problems too, because the
machine is otherwise responsive and fine. it's just the SQL server service
that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL 2000
Ent.
thanks
> that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL
2000
> Ent.
I forgot one thing, Win2k3 has SP1, and SQL server has SP3 applied.
- Gabor
sqlsql
Showing posts with label becomes. Show all posts
Showing posts with label becomes. Show all posts
Tuesday, March 27, 2012
Cluster problems?
Every now and then (about once a week) our SQL server cluster
(active/passive) becomes unresponsive, and the following events are logged:
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Timeout expired
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] OnlineThread: QP is not online.
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
SQL server errorlog contains these errors:
2005-08-07 07:52:16 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:16 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:52:19 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:19 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:47 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:47 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:54:27 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:55:05 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:55:05 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [382] Logon to server '(local)' failed (JobManager)
During this time, connections are terminated and SQL server does not allow
legitimate accounts to log in. it last for a couple of minutes. The server is
clearly not overloaded, and it doesn't have any specific jobs or anything to
do at this time. I would like to exclude network problems too, because the
machine is otherwise responsive and fine. it's just the SQL server service
that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL 2000
Ent.
thanks> that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL
2000
> Ent.
I forgot one thing, Win2k3 has SP1, and SQL server has SP3 applied.
- Gabor
(active/passive) becomes unresponsive, and the following events are logged:
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Timeout expired
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] OnlineThread: QP is not online.
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
SQL server errorlog contains these errors:
2005-08-07 07:52:16 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:16 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:52:19 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:19 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:47 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:47 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:54:27 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:55:05 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:55:05 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [382] Logon to server '(local)' failed (JobManager)
During this time, connections are terminated and SQL server does not allow
legitimate accounts to log in. it last for a couple of minutes. The server is
clearly not overloaded, and it doesn't have any specific jobs or anything to
do at this time. I would like to exclude network problems too, because the
machine is otherwise responsive and fine. it's just the SQL server service
that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL 2000
Ent.
thanks> that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL
2000
> Ent.
I forgot one thing, Win2k3 has SP1, and SQL server has SP3 applied.
- Gabor
Cluster problems?
Every now and then (about once a week) our SQL server cluster
(active/passive) becomes unresponsive, and the following events are logged:
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Timeout expired
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] OnlineThread: QP is not online.
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
SQL server errorlog contains these errors:
2005-08-07 07:52:16 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:52:16 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:52:19 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:52:19 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:53:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:53:27 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:53:47 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:53:47 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:54:27 - ! [298] SQLServer Error: 11, General network error
.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:54:27 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:54:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:55:05 - ! [298] SQLServer Error: 11, General network error
.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:55:05 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 11, General network error
.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [382] Logon to server '(local)' failed (JobManag
er)
During this time, connections are terminated and SQL server does not allow
legitimate accounts to log in. it last for a couple of minutes. The server i
s
clearly not overloaded, and it doesn't have any specific jobs or anything to
do at this time. I would like to exclude network problems too, because the
machine is otherwise responsive and fine. it's just the SQL server service
that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL 200
0
Ent.
thanks> that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL
2000
> Ent.
I forgot one thing, Win2k3 has SP1, and SQL server has SP3 applied.
- Gabor
(active/passive) becomes unresponsive, and the following events are logged:
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Timeout expired
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] OnlineThread: QP is not online.
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
SQL server errorlog contains these errors:
2005-08-07 07:52:16 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:52:16 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:52:19 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:52:19 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:53:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:53:27 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:53:47 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:53:47 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:54:27 - ! [298] SQLServer Error: 11, General network error
.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:54:27 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:54:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:55:05 - ! [298] SQLServer Error: 11, General network error
.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:55:05 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 11, General network error
.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [382] Logon to server '(local)' failed (JobManag
er)
During this time, connections are terminated and SQL server does not allow
legitimate accounts to log in. it last for a couple of minutes. The server i
s
clearly not overloaded, and it doesn't have any specific jobs or anything to
do at this time. I would like to exclude network problems too, because the
machine is otherwise responsive and fine. it's just the SQL server service
that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL 200
0
Ent.
thanks> that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL
2000
> Ent.
I forgot one thing, Win2k3 has SP1, and SQL server has SP3 applied.
- Gabor
Monday, March 19, 2012
CLUSTER
I have a SQL 7.0 Clustered Server with SP3. Sometimes a DB (16GB) becomes
suspect and the only way to get it back online is to reboot the server and
that gets it back to normal. This happens every week.
Any ideas?
Also can you tell me how to change the location where Microsoft Clustered
Server changes the Temporary file location. Currently on my server it is
c:\winnt which we want to change
Thanks
RodRod,
You are probably better off calling Microsoft PSS to troubleshoot this
issue.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Rod wrote:
> I have a SQL 7.0 Clustered Server with SP3. Sometimes a DB (16GB) becomes
> suspect and the only way to get it back online is to reboot the server and
> that gets it back to normal. This happens every week.
> Any ideas?
> Also can you tell me how to change the location where Microsoft Clustered
> Server changes the Temporary file location. Currently on my server it is
> c:\winnt which we want to change
> Thanks
> Rod
suspect and the only way to get it back online is to reboot the server and
that gets it back to normal. This happens every week.
Any ideas?
Also can you tell me how to change the location where Microsoft Clustered
Server changes the Temporary file location. Currently on my server it is
c:\winnt which we want to change
Thanks
RodRod,
You are probably better off calling Microsoft PSS to troubleshoot this
issue.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Rod wrote:
> I have a SQL 7.0 Clustered Server with SP3. Sometimes a DB (16GB) becomes
> suspect and the only way to get it back online is to reboot the server and
> that gets it back to normal. This happens every week.
> Any ideas?
> Also can you tell me how to change the location where Microsoft Clustered
> Server changes the Temporary file location. Currently on my server it is
> c:\winnt which we want to change
> Thanks
> Rod
Subscribe to:
Posts (Atom)