Solving SQL Connectivity issues: A new guided walk through just got published

We recently published a new document that provides a one stop shop for solving majority of connectivity issues that you may run into when working with SQL Server. This can be accessed here:

Solving Connectivity errors to SQL Server

In addition to providing a quick checklist of items that you can go through, the doc provides step by step troubleshooting procedures for the following error messages:

  • A network-related or instance-specific error occurred while establishing a connection to SQL Server
  • No connection could be made because the target machine actively refused it
  • SQL Server does not exist or access denied
  • PivotTable Operation Failed: We cannot locate a server to load the workbook Data Model
  • Cannot generate SSPI context
  • Login failed for user
  • Timeout Expired
  • The timeout period elapsed prior to obtaining a connection from the pool

We hope that you use this to guide your troubleshooting of connectivity issues and would love to get your feedback on these kind of documentation experiences.

We also have the following troubleshooters available for Always On and SQL Azure DB connectivity issues:

Troubleshooting Always On Issues

Troubleshooting connectivity issues with Microsoft Azure SQL Database

Comments (8)
  1. Ekrem Önsoy says:

    En: What a coincidence! I wrote a comprehensive reference blog post about the same subject in Turkish this month. Turkish readers can reach it from the following link.

    Tr: Ne rastlandı ama! Aynı konu hakkında bu ay ben de kapsamlı bir Türkçe yazı yazdım. Türk okuyucular bu yazıya aşağıdaki adresten ulaşabilirler.

    1. Ramu_MSFT says:

      Thanks for the additional pointer to our customers.

  2. Papy Normand says:

    Old posts which could be found with this search
    I know that these links are related to SQL Server 2005 but I think that they could be useful.
    Anyway , thanks for your work
    And sorry for my poor English language

    1. Ramu_MSFT says:

      Thank you. Will go through the same for additional info.

  3. Hi Ramu,
    great work!
    The link for “Troubleshooting Always On Issues” is not correct. It should be “” without the “?preview”.

    1. Ramu_MSFT says:

      Thank you Christoph. Fixed the link in the post and republished.

  4. William Hug says:

    Nice! I did note that the troubleshooting doesn’t seem to address errors incurred when encrypted connections is turned on. Also, it doesn’t cover Java. Can these be added? I am always having issues with client apps connecting with Java with encrypted connections on.


    1. Ramu_MSFT says:

      Thanks for the feedback. We will look at adding these in a future revision of the article.

Comments are closed.

Skip to main content