Lesson Learned #145: Cannot communicate, because they do not possess a common algorithm

Published Nov 23 2020 01:23 AM 3,910 Views

Today, I saw a new service request that our customer is trying to create a linked server but they faced the following error message: SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm. OLE DB provider "MSOLEDBSQL" for linked server "servername" returned message "Client unable to establish connection". (.Net SqlClient Data Provider)"

 

From March 2020, Azure SQL Managed Instance enforces  to use TLS 1.2 protocol for outbound connections. In this link you could find the reason and also a fix.

 

 

1 Comment
%3CLINGO-SUB%20id%3D%22lingo-sub-1922799%22%20slang%3D%22en-US%22%3ELesson%20Learned%20%23145%3A%20Cannot%20communicate%2C%20because%20they%20do%20not%20possess%20a%20common%20algorithm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1922799%22%20slang%3D%22en-US%22%3E%3CP%3EToday%2C%20I%20saw%20a%20new%20service%20request%20that%20our%20customer%20is%20trying%20to%20create%20a%20linked%20server%20but%20they%20faced%20the%20following%20error%20message%3A%26nbsp%3BSSL%20Provider%3A%20The%20client%20and%20server%20cannot%20communicate%2C%20because%20they%20do%20not%20possess%20a%20common%20algorithm.%26nbsp%3BOLE%20DB%20provider%20%22MSOLEDBSQL%22%20for%20linked%20server%20%22servername%22%20returned%20message%20%22Client%20unable%20to%20establish%20connection%22.%20(.Net%20SqlClient%20Data%20Provider)%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20March%202020%2C%20Azure%20SQL%20Managed%20Instance%20enforces%26nbsp%3B%20to%20use%20TLS%201.2%20protocol%20for%20outbound%20connections.%20In%20this%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fupdates%2Fazure-sql-managed-instance-enforces-tls-12-on-outbound-connections%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Elink%3C%2FA%3E%20you%20could%20find%20the%20reason%20and%20also%20a%20fix.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1922799%22%20slang%3D%22en-US%22%3E%3CP%3EToday%2C%20I%20saw%20a%20new%20service%20request%20that%20our%20customer%20is%20trying%20to%20create%20a%20linked%20server%20but%20they%20faced%20the%20following%20error%20message%3A%26nbsp%3BSSL%20Provider%3A%20The%20client%20and%20server%20cannot%20communicate%2C%20because%20they%20do%20not%20possess%20a%20common%20algorithm.%26nbsp%3BOLE%20DB%20provider%20%22MSOLEDBSQL%22%20for%20linked%20server%20%22servername%22%20returned%20message%20%22Client%20unable%20to%20establish%20connection%22.%20(.Net%20SqlClient%20Data%20Provider)%22%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2227067%22%20slang%3D%22en-US%22%3ERe%3A%20Lesson%20Learned%20%23145%3A%20Cannot%20communicate%2C%20because%20they%20do%20not%20possess%20a%20common%20algorithm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2227067%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20getting%20the%20below%20error%20when%20connecting%20SQL%20server.%20Enabled%20TLS%201.2%20and%20disabled%201.0%20and%201.1.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBelow%20is%20the%20version%20information.%20Can%20you%20please%20suggest.%20How%20to%20resolve%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESQL%20Server%20Management%20Studio%2015.0.18369.0%3CBR%20%2F%3ESQL%20Server%20Management%20Objects%20(SMO)%2016.100.46041.41%3CBR%20%2F%3EMicrosoft%20Analysis%20Services%20Client%20Tools%2015.0.19342.0%3CBR%20%2F%3EMicrosoft%20Data%20Access%20Components%20(MDAC)%2010.0.19041.1%3CBR%20%2F%3EMicrosoft%20MSXML%203.0%206.0%3CBR%20%2F%3EMicrosoft%20.NET%20Framework%204.0.30319.42000%3CBR%20%2F%3EOperating%20System%2010.0.19042%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETITLE%3A%20Connect%20to%20Server%3CBR%20%2F%3E------------------------------%3C%2FP%3E%3CP%3ECannot%20connect%20to%20CIHCTSVDBSQA289.logon.ds.ge.com%5CPROD.%3C%2FP%3E%3CP%3E------------------------------%3CBR%20%2F%3EADDITIONAL%20INFORMATION%3A%3C%2FP%3E%3CP%3EA%20connection%20was%20successfully%20established%20with%20the%20server%2C%20but%20then%20an%20error%20occurred%20during%20the%20login%20process.%20(provider%3A%20SSL%20Provider%2C%20error%3A%200%20-%20The%20client%20and%20server%20cannot%20communicate%2C%20because%20they%20do%20not%20possess%20a%20common%20algorithm.)%20(Microsoft%20SQL%20Server%2C%20Error%3A%20-2146893007)%3C%2FP%3E%3CP%3EFor%20help%2C%20click%3A%20%3CA%20href%3D%22http%3A%2F%2Fgo.microsoft.com%2Ffwlink%3FProdName%3DMicrosoft%2520SQL%2520Server%26amp%3BEvtsrc%3DMSSQLServer%26amp%3BEvtID%3D-2146893007%26amp%3BLinkId%3D20476%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fgo.microsoft.com%2Ffwlink%3FProdName%3DMicrosoft%2520SQL%2520Server%26amp%3BEvtsrc%3DMSSQLServer%26amp%3BEvtID%3D-2146893007%26amp%3BLinkId%3D20476%3C%2FA%3E%3C%2FP%3E%3CP%3E------------------------------%3C%2FP%3E%3CP%3EThe%20client%20and%20server%20cannot%20communicate%2C%20because%20they%20do%20not%20possess%20a%20common%20algorithm%3C%2FP%3E%3CP%3E------------------------------%3CBR%20%2F%3EBUTTONS%3A%3C%2FP%3E%3CP%3EOK%3CBR%20%2F%3E------------------------------%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Nov 23 2020 01:23 AM
Updated by: