Share via

Linked server issue between SQL 2022 and SQL2008

Sampath Challagonda 0 Reputation points
2026-01-23T12:18:25.9766667+00:00

Hi ,

I have installed new SQL Server 2022 and trying to create linked server with SQL Server 2008 but getting below error message.

TITLE: Microsoft SQL Server Management Studio

The linked server has been created but failed a connection test. Do you want to keep the linked server?

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm.

OLE DB provider "MSOLEDBSQL" for linked server "PROD02" returned message "Client unable to establish connection". (Microsoft SQL Server, Error: -2146893007)

For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver--2146893007-database-engine-error

BUTTONS:

&Yes

&No

then I have installed SQL 2019 but again same issue but I was able to create linked server with same SQL 2008 instance on one of the production SQL 2019 instance.

SQL Server Database Engine

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-01-23T12:18:38.4466667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error you are encountering when trying to create a linked server between SQL Server 2022 and SQL Server 2008 is likely due to a mismatch in the supported encryption algorithms or cipher suites between the two SQL Server versions. This specific error message indicates that the client and server cannot communicate because they do not possess a common algorithm, which can occur when the SQL Server 2022 instance is configured to use newer security protocols that are not supported by SQL Server 2008.

    To resolve this issue, you can check the following:

    1. Cipher Suites: Ensure that both SQL Server instances support a common set of cipher suites. You can check the cipher values on both servers using PowerShell commands to compare them.
    2. TLS Protocols: SQL Server 2022 may require TLS 1.2 or higher, while SQL Server 2008 may not support these protocols. You might need to enable TLS 1.2 on the SQL Server 2008 instance if possible.
    3. Registry Settings: If RSA encryption is being used, ensure that it is enabled on the SQL Server 2008 instance. You can modify the registry key to enable RSA encryption if it is currently disabled.
    4. Network Configuration: Ensure that there are no network issues or firewalls blocking the connection between the two servers.

    If you continue to experience issues, consider reviewing the specific error logs for more detailed information about the connection failure.

    References:

  2. Erland Sommarskog 132K Reputation points MVP Volunteer Moderator
    2026-01-25T13:06:02.1233333+00:00

    The version of SQL Server 2008 R2 that you have does not have support for TLS 1.2. Here is a new from https://sqlserverbuilds.blogspot.com/#sql2008r2x

    User's image

    I've highlighted the build that adds TLS 1.2 support. I have marked the build you have now, and the one I recommend you to install. (The one that is on top is only available to customers who have paid for Extended Security Updates.)

    Note that you may still face problems after installing the build, since the OS must also have TLS 1.2 support. Windows Server 2012 R2 is too old to come with TLS 1.2 support out of the box, but it is new enough for patches being available. You need to check if your server has such a patch.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.