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

The semaphore timeout period has expired Expand / Collapse
Posted Monday, June 28, 2010 2:47 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: 330, Visits: 334

I'm investigating a different track as well, I was always wondering about the SAN track, since the SQL Agent error refers to TCP, i.e issues in the TCP stack, and the parameters mentioned in this thread also refes to tcp/ip.

Our test have been to disable the Arcserve open file agent, this is a kernel driver, that loads deep down in the tcp/ip stack (ofant.sys). Stopping the windows service is not enough since the driver stays loaded, so we went for an uninstall. Only two weeks after uninstall but have not seen any issues yet.

I mention Arcserve, but I guess all backup poducts have similar agents for backing up open files.

More news after some time running in this configuration...

Post #944249
Posted Thursday, August 5, 2010 10:50 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, October 9, 2015 2:43 AM
Points: 3, Visits: 198
You can close this thread,
read the below links with the explanation of the problem and the ultimate fix.


TCP Chimney Offload

Query Timeout problem

and Microsoft confirms:
SQL Server Intermittent Connectivity Issue
Post #964488
Posted Sunday, August 8, 2010 2:47 AM


Group: General Forum Members
Last Login: Thursday, July 2, 2015 7:37 AM
Points: 154, Visits: 174
Hi everyone,

we've had the same issue on a 2-node cluster. On 1 node everything runs fine but as soon as everything fails to the other node we encounter this issue randomly. This cluster used to run Windows 2003 R2 SP2 and SQL 2005 SP3 x64.

We rebuilt the cluster on the same hardware this weekend using Windows 2008 R2 and SQL 2008 SP1, and are encountering the same issue with the upgraded software... Grrr....

I'm not too sure if the HBA queue depth contributes to this specific error, although it does help with I/O throughput.

Has anyone been able to resolve this issue? We're left stranded with a half-working cluster now.
Post #965636
« Prev Topic | Next Topic »

Add to briefcase «««1234

Permissions Expand / Collapse