Semaphore Timeout Period

Question

I've recently wiped and reinstalled/configured all the components of my web and DB servers. I'm running IIS 6, .NET 3.5, SQL Server 2005. The two servers are separate VM's in the same domain. My web app functions perfectly... 90% of the time. But every now and then I get this error or a generic runtime error:

System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)

Can you guys give me some leads on where to start troubleshooting? I really think I've missed something in IIS.

Thanks in advance!

Solution 1

After troubleshooting this for hours and sitting on the phone with my hosting group they discovered that there was a problem with their networking configuration. The solution was made clearer when during my testing one of the VM's suddenly couldn't find the domain, and a simple 'ping' to the IP of each box from the other would occasionally time out. This ruled out DNS entirely. After the hosting group applied the proper configuration on their end the app has been stable and FAST!

Thanks for everyone's help!

Solution 2

A few pointers are here .Basically the error is being thrown by the network layer and SQL server is just reporting it.

Hope that helps.

Solution 3

Well I would start by ensuring I'm running the latest version of my virtual machine's network drivers.

Sounds like comms is failing between your 2 VMS. Try opening a TCP socket between the two machines and see if it dies after a certain amount of time.

Solution 4

Can you double check the load on the db server? We do get them once in a while in our dev env, but never in the prod env.

Solution 5

I will post my experience just in case it might help someday somebody ;)

At the end of the year, just trying to connect remotely to our servers from a place far, far away, using my phone. I noticed that I could not login to one windows server via remote desktop (black screen), nor I could connect from a Windows Application to the same server.

As soon as I changed from my phone to a different connection (via a NightHawk M1 mobile router), it was all good.

As I have read, is is about NETWORKING issues mainly, so DO NOT PANIC and try to find the guilty there.

Hope it helps, R

View more solutions