August 22, 2022 at 6:14 pm
Hi all,
I'm having issues communicating via a linked server from a Windows 2019 Standard server running SQL 2017 Standard to a Windows 2003 R2 Enterprise server running SQL 2005 Standard. The operating system on the source server was just upgraded from Windows 2012 R2.
Error:
OLE DB provider "SQLNCLI11" for linked server "server" returned message "Client unable to establish connection".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
I tried enabling TLS 1.0 and 1.1 thinking that was the culprit, but no luck. Any ideas what I'm missing?
August 23, 2022 at 7:57 am
Wow, running sql server 2005. Maybe it's better to setup a new 2019 and restoring the data. TLS 1.0 en 1.1 are getting obsolete fast.
Regarding linked server: did it work beforre the Windows 2012 R2 upgrade?
(SQL 2019 -> SQL 2005 on Windows 2003)
Checked the firewall / eventviewer logs?
August 23, 2022 at 5:24 pm
Yes, the linked server worked before the upgrade and the event logs don't provide any other insights. I've also tried other servers with the same configuration (Windows Server 2019, SQL Server 2017) and they all give the same error when trying to access the SQL 2005 box via the linked server. Servers running Windows Server 2016 work just fine though. I thought enabling TLS 1.0/1.1 would be the solution, but no luck.
Believe me, I want to get rid of the 2005 server as soon as possible. Unfortunately, it won't be for a few months and I need to get this working for the time-being.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply