Lesson Learned #215: Hands-On-Labs: Communication link failed error message using ODBC.

This post has been republished via RSS; it originally appeared at: Azure Database Support Blog articles.

We used to have cases where our customer faced the following error messages like following:

  • ERROR [08S01] [Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: An existing connection was forcibly closed by the remote host.
  • ERROR [08S01] [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure

In this video below we going to provide us some insights about it. 


Why this issue happens?

  • Application or network issue at client level that closed unexpectedly the connection to the database


How to find the issue?

  • Application Error messages: mainly followed by client driver names or protocols (ODBC/ TCP)


How to Fix the issue?

  • Look for network issues.
  • Check performance on target/application server
  • Implement the retry-logic at connection and command execution.


In this video we will cover scenarios causing error - Communication link failure





Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.