Please let me know if this is the correct forum for this question:
We have an application which uses the following on a VM machine:
Windows Server 2008 R2 Standard
SQL Server 2008 R2 Standard
64-bit OS
32 GB RAM
We have increasingly getting more and more TCP errors. They run the range of the following:
Within an application built using VS 2010 in VB.Net, users receive the follwing errors:
- A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
- A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
- A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
Today, a developer who had left the SSMS activity monitor open, received the following error:
- The ACtivity Monitor is unable to execute queries against the server XXXXX. Activity Monitor for this instance will be placed in a paused state. Use the context menu in the overview pane to resume the Activity Monitor.
- ADDITIONAL INFORMATION: A transport level errro has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) Micorsoft SQL Server, Error: 64)
peonysmiles