Consider the following scenario:

  • You have an instance of Microsoft SQL Server 2017 that has a server setup that's linked to another instance of SQL Server.

  • A user without Bypass traverse checking local policy rights runs the first linked server query after a restart of the SQL Server service.

In this scenario, the initial linked server query is run, and every successive linked server query by any user returns error messages that resemble the following:

OLE DB provider "SQLNCLI11" for linked server "server_name" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online."

OLE DB provider "SQLNCLI11" for linked server "server_name" returned message "Client unable to establish connection".
Msg 21, Level 16, State 1, Line 0
Encryption not supported on the client


This problem is fixed in the following update for SQL Server:

Cumulative Update 12 for SQL Server 2017

About SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:

The latest build for SQL Server 2017


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the standard terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!