A rare error: "TCP Provider: An existing connection was forcibly closed by the remote host."

Sinan 1 Reputation point
2022-09-08T13:30:07.137+00:00

I have a linked server, where the main and linked SQL servers is SQL 2012".
I am having one or two times error per month! the error is:
TCP Provider: An existing connection was forcibly closed by the remote host.

This problem is happening one time only. How can I check what happened at that time! I have the logs and I can check the exact time.

I really need a help on this!

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,660 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Bjoern Peters 8,781 Reputation points
    2022-09-08T13:47:17.327+00:00

    I don't know if you have already read this article... maybe it helps to identify your problem.

    https://learn.microsoft.com/en-us/troubleshoot/sql/connect/tls-exist-connection-closed


  2. Tom Phillips 17,716 Reputation points
    2022-09-08T14:07:27.36+00:00

    Since you are seeing this error intermittently, and not all the time, it is almost certainly a network error of some kind causing the error.

    There may be something in the destination SQL Server log, but most likely not. You would have to trace the network packets when it happens to get a real idea of the problem.


  3. Seeya Xi-MSFT 16,436 Reputation points
    2022-09-09T06:16:53.197+00:00

    Hi @Sinan ,

    Welcome to Microsoft Q&A!

    This problem is happening one time only. How can I check what happened at that time! I have the logs and I can check the exact time.

    If the link from BjoernPeters doesn't solve your problem and you're having an accidental problem, it should be a network-level problem. Since TCP/IP is a protocol at the network layer, you'd better contact your network administrator. Good luck.

    Best regards,
    Seeya


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. risolis 8,701 Reputation points
    2022-09-09T06:40:52.177+00:00

    Hello @Sinan

    Thank you for your heads up.

    I would like to provide some extra steps that might be useful to follow in order to isolate the issue stated on your case scenario description previously.... So please see them down below:

    -TCP properties
    -Encryption/Authentication settings review(TLS/SSL version supported, certificate used/Certificate attributes and among others)
    -Port Allocation used/NAT port exhaustion at the FW settings review
    -Dynamic Port allocation setting review
    -If any NAT device in between the routing path
    -MTU mismatch value
    -Asymmetric routing
    -DNS delay or DNS flapping look up causing Asymmetric routing issues or time outs
    -Confirm any network session was stuck due to ProcessID (PID)
    -Packet Capture
    -Bottleneck network issues(For instance: Traceroute/Tracert and so on)
    -VM size upgrade if issue can be for lack for resources
    -Swap listening port On server settings
    -VPN session rekey lifetime(If any IPsec/SSL/OPENVPN tunnel in between)
    -Encryption/encryption policy
    -Certificate inspection policy
    -TCP-OUT-OF orders packets

    I hope you can find this useful to address your concern.

    Looking forward to your feedback,

    Cheers,

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments