July 30, 2018 at 2:47 pm
Have a .NET (3.5 thru 4.6) WinForms/C#/VB.NET Desktop application been used with SQL Server (2008 or 2016) running on Windows Server (2008 thru 2016). Application gets intermittent database errors. Below are the various types we have seen. Does not seem to be tied to release of SQL Server or Windows Server.
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider; error: 0 - An existing connection was forcibly closed by remote host.)
Our app logs show variations of the error .. sometimes it is sending results. The TCP Provider error has following variations
>> TCP Provider; error: 0 - The semaphore timeout period has expired.
>> TCP Provider; error: 0 - An existing connection was forcibly closed by the remote host
>> Shared Memory Provider; error: 0 - No process is on the other end of the pipe.
>> TCP Provider; error: 0 - The network connection was aborted by the local system.
This is like a network connection drop, cable pulled, Wireless disconnected etc.
Have checked that application is not leaving open connections. Also confirmed the connections open stay less than 50 during our tests.
Need help from the community on how would I troubleshoot root cause? Most cases we ask user to retry and it just works.
July 30, 2018 at 5:01 pm
anup.mistry - Monday, July 30, 2018 2:47 PMHave a .NET (3.5 thru 4.6) WinForms/C#/VB.NET Desktop application been used with SQL Server (2008 or 2016) running on Windows Server (2008 thru 2016). Application gets intermittent database errors. Below are the various types we have seen. Does not seem to be tied to release of SQL Server or Windows Server.A transport-level error has occurred when receiving results from the server. (provider: TCP Provider; error: 0 - An existing connection was forcibly closed by remote host.)
Our app logs show variations of the error .. sometimes it is sending results. The TCP Provider error has following variations>> TCP Provider; error: 0 - The semaphore timeout period has expired.
>> TCP Provider; error: 0 - An existing connection was forcibly closed by the remote host
>> Shared Memory Provider; error: 0 - No process is on the other end of the pipe.>> TCP Provider; error: 0 - The network connection was aborted by the local system.
This is like a network connection drop, cable pulled, Wireless disconnected etc.Have checked that application is not leaving open connections. Also confirmed the connections open stay less than 50 during our tests.
Need help from the community on how would I troubleshoot root cause? Most cases we ask user to retry and it just works.
Check for network issues in the Windows event logs on that server. Make sure you are using the drivers for the NIC(s).
Sue
July 30, 2018 at 10:08 pm
It would seem to suggest you're getting timeouts waiting for the SQL to run. Check how long your queries are taking to run and compare against your timeout values.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply