SQL SERVER – Unable to Set Cloud Witness. Error: The Client and Server Cannot Communicate, Because They do Not Possess a Common Algorithm

Recently, I was trying to simulate a client’s environment for which I need to have windows cluster with cloud witness. It didn’t go well, and I encountered an error message. In this blog, I will share the solution of error – “The client and server cannot communicate, because they do not possess a common algorithm” which I received while adding cloud witness. I was following below documentation: Deploy a Cloud Witness for a Failover Cluster

Here is the screenshot of the error message.

SQL SERVER - Unable to Set Cloud Witness. Error: The Client and Server Cannot Communicate, Because They do Not Possess a Common Algorithm cloudwitness-tls-01

Solarwinds

The text of the message is as follows.

An error was encountered while modifying the quorum settings.
Your cluster quorum settings have not been changed.
The client and server cannot communicate, because they do not possess a common algorithm.

Based on my earlier experience, this error can be seen when client and server do not talk using the same version of TLS protocols. Based on my search I found that the communication between storage account and cluster nodes happens on using TLS 1.0. The error appeared because TLS 1.0 was disabled on the server. To overcome this, we can use below PowerShell commands to use TLS1.2 for cloud quorum setup.

SQL SERVER - Unable to Set Cloud Witness. Error: The Client and Server Cannot Communicate, Because They do Not Possess a Common Algorithm cloudwitness-tls-02

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Set-ClusterQuorum -Cluster ClusterName -CloudWitness -AccountName "NameOfStorageAccount" -AccessKey "AccessKeyForStorageAccount"

As you can see command ran successfully and witness for setup correctly.

Have you encountered some other error while deploying cloud witness?

Reference: Pinal Dave (https://blog.sqlauthority.com)

Solarwinds
, , , , ,
Previous Post
SQL SERVER – FIX: Msg 41105: Failed to Create the Windows Server Failover Clustering (WSFC) Resource With Name and Type ‘SQL Server Availability Group’
Next Post
SQL SERVER – FIX: Cannot Connect to SQL in Azure Virtual Machine From Laptop

Related Posts

Leave a Reply

Menu