Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««1234

SQL Server 2005 Cluster - [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed Expand / Collapse
Author
Message
Posted Friday, October 16, 2009 2:30 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, March 10, 2014 8:45 AM
Points: 329, Visits: 334
Hi All

This thread have saved our SQL cluster did the below seetings and it have fixed the issue, at least one week without problems, and they usually were there every second day or so. Our configuration was like so many others here with large memeory:

4 node SQL 2005 cluster config with 5 instances
All cluster nodes are 4 Dual core CPU HP bl45's with 50GB memory

I also had a ticket open with MS and they did not lead me to this fix, and they led me down the firmwre and driver road first so I upgraded to Firmware 8.03 and HP PSP 8.30 beforefinding this fix. Of cause firmware and drivers, did not fix the problem.



thomas.halligan (10/18/2008)
We have resolved this issue on a couple of Clusters by setting the following in Registry on the nodes(After having updated service packs, driver, firmware and disabling TCP/IP offload)

1. Set TcpMaxDataRetransmissions to 30 (decimal);
http://technet2.microsoft.com/WindowsServer/en/library/7dac9001-3e55-4e9c-b0fa-52841ece2fdd1033.mspx

2. Set KeepAliveInterval to 25000 (decimal).
http://technet2.microsoft.com/WindowsServer/en/library/734570a2-06d6-450e-b765-ccfa7530af491033.mspx

It worked for us you mileage may.
Post #804544
Posted Thursday, August 5, 2010 10:51 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, April 28, 2014 1:12 PM
Points: 3, Visits: 189
You can close this thread,
read the below links with the explanation of the problem and the ultimate fix.


SynAttackProtect
http://sqlblog.com/blogs/merrill_aldrich/archive/2010/06/10/windows-server-2003-network-boogey-men-every-dba-should-know.aspx
http://blogs.msdn.com/b/sql_protocols/archive/2006/04/12/574608.aspx



TCP Chimney Offload
http://support.microsoft.com/kb/942861



Query Timeout problem
http://support.microsoft.com/kb/945442


and Microsoft confirms:
SQL Server Intermittent Connectivity Issue
http://blogs.msdn.com/b/mssqlisv/archive/2008/05/27/sql-server-intermittent-connectivity-issue.aspx
Post #964490
Posted Wednesday, March 27, 2013 2:02 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 5:25 AM
Points: 4, Visits: 35
Hi, just spent whole day trying to distribute SQL procedure to linked servers . On some I got following error:

OLE DB provider
"SQLNCLI" for linked server "ccccc" returned message "Communication link failure".
Msg 121, Level 16, State 1,Line 0
TCP Provider: The semaphore timeout period has expired.


Somethimes also:

TCP Provider: An existing connection was forcibly closed by the remote host

As I found out, the problem is, that procedure contains substring:
'master.dbo.xp_cmdshell '

and something blocks the packets or connection (some firewall or so..)

Even following statement timed out:

insert into linkedsrv.DB.dbo.tblTmp
values ('master.dbo.xp_cmdshell ')

Post #1435792
« Prev Topic | Next Topic »

Add to briefcase «««1234

Permissions Expand / Collapse