SQLClient Exception: timeout expired under heavy process load RRS feed

  • Question

  • Using .NET 4.0 ADO.NET Windows Forms programs doing batch updates on Windows 2008 R2 server connecting to a networked SQL server 2008 R2.

    We start about 200 Windows Batch jobs on a server doing light SQL updates.  If there is an error causing many exceptions to be logged to SQL, we get SQL timeouts.

    Inspection of a server dump showed: a TCP Handshake, which should have been followed immediately by a TDS Pre-Login packet, but this didn’t happen.  After 70-90 seconds, SQL reset the stream as the client server never sent anything.

    Any ideas how to prevent this?  Thanks


    Thursday, December 4, 2014 7:25 PM


  • Hello Mister,

    >>Any ideas how to prevent this?

    Not sure which one you want to prevent, if you want to prevent the timeout expired exception, a command workaround is to increase timeout value as setting it to 300 second or move longer.

    If you want to the TCP Handshake occurs, it seems to be SQL Server protocol related and I afraid this should beyond the scope of ADO.NET Managed Providers forum, I suggest that you could post it to the SQL Server forum.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, December 5, 2014 9:53 AM