ODBC not working after WIndows upgrade from 2003 R2 to 2016 for SQL Server 2005

Dathuraj Pasarge 1 Reputation point
2022-01-28T08:28:08.723+00:00

Well, I did the inplace upgrade of Windows Server 20003 R2 to Windows Server 2016 using some third party tool, however all went fine but only the issue that I am encountering is with the ODBC setup.

Existing or new ODBC works fine when I use the SQL Server 2008 instance but same is not working when using SQL 2005 as source database server, getting the error as attached below. Even after installing the SQL Server Native client 9.0 still unable to create the ODBC connection for SQL 2005 version. UDL also throwing the error msg.

Also installed the Microsoft® ODBC Driver 11 for SQL Server® - Windows, but still no luck.

NOTE: Able to ping the SQL host and port 1433 also open.

UDL attempt :
Attempting connection
[Microsoft][SQL Server Native Client 11.0]TCP Provider: An existing connection was forcibly closed by the remote host.
[Microsoft][SQL Server Native Client 11.0]Client unable to establish connection

169377-image.png

Any compatibility issue with SQL 2005 client authentication on windows server 2016 for ODBC setup??

Thanks,
Dathuraj Pasarge

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,773 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Olaf Helper 40,916 Reputation points
    2022-01-28T08:43:36.427+00:00

    when using SQL 2005

    I hope you know that SQL Server 2005 is out-of-support since a very long time?

    Microsoft® ODBC Driver 11 for SQL Server

    Also that ODB driver is more then outdated=unsupported, last version is 17

    Microsoft® ODBC Driver 17 for SQL Server® - Windows, Linux, & macOS

  2. Erland Sommarskog 101.4K Reputation points MVP
    2022-01-28T22:54:47.877+00:00

    I would guess that the issue is that you don't have TLS 1.0 enabled on the server, only TLS 1.2, which SQL Server 2005 thinks is complete garbage.

    0 comments
  3. YufeiShao-msft 7,061 Reputation points
    2022-01-31T08:03:43.157+00:00

    Hi @Dathuraj Pasarge ,

    This issue may occur when the SQL Native Client layer cannot connect to SQL Server after the TLS 1.2 protocol is enable on the SQL Serser
    This is documented at length at: KB3135244 - TLS 1.2 support for Microsoft SQL Server.

    Find out which driver SCCMC is using to connect to SQL Server by viewing the SCCM log, download and install the Native cilent fix that is listed in the Client Components downloads section of this acticle

    -------------

    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