I specify the device using a UNC name to the share on the WinXP box (e.g., \\winxpbox\sharename). * I have maintenance plans (MP) on each server to do Full DB backups each night and Log backups every 30 minutes to a device on another computer on that subnet (WinXP Pro SP2, GB ethernet). * Two identical servers (Dell PE 840, Quad core, 4GB RAM, 300GB 10,000 rpm RAID 1) running Windows 2003 R2 SE SP2 (x32), each running SQL Server 2005 SE SP3 on two distinct GB subnets (using Netgear GS605 GB Switches). I've been trying to solve this for many months on our systems. īy upgrading this setting we encounter a 8x speed up of our most heavly used systems and probably lose the semaphore issue.(I hope) We're hosting our SAN and they once set this queue depth length to 4. Hope this will be sollved when we move over to MS Windows 2008 (running SQL Server 2008) within several months.Įxamin your HBA's queue depth length and set it at least to 128. The Timeout could be related to several parts on the hardware and/or probably to some software as well. Recentley we where supported by a microsoft engineer for a project and aksed him if he was familiar with this problem but he also was scratching his head again and again.Īs mentioned in the opening text this is still a random issue which occurs every now and then.
I Entered this on the Microsoft Helpdesk (we've got platinum support) but they cannot solve this either. This problem still excists and no cause can be found.
Who delt with this issue before and /or can help me out on this? 64 bits SP1 or this is a bug/failure to properly release the cached memory. Others say this could be a Memory issue on windows 2003 SP1 cluster node with sql 2005 Ent. This can be Hardware response timeout or an Autodetect setting on cluster network interface card. Hardly any info is to be found in the Internet so I need your help guys!!Īs far as I found out this is an OS error which is written in the SQL server 2005 logs just before losing contact with one of the parts of the subsystems. (Error 121) Communication link failure (Error 121). TCP Provider: The semaphore timeout period has expired. This message occurs when using all kinds of I/O to the subsystem (which resides on the SAN).Įxecuted as user. Just moving over to a new firm I was asked to find out the reason why most of the clustered servers where prompting "SEMAPHORE TIMEOUT" every now and than so I digged in.
0 kommentar(er)
