Error adding WSFC witness cloud azure disk

MaksymKam 1 Reputation point
2022-10-12T11:33:55.313+00:00

I have WSFC with two node and I want to add Azure witness disk to qourum.
I have error
249589-wsfcazureerror.png

What I do wrong?

Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
962 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Alex Bykovskyi 1,831 Reputation points
    2022-10-13T17:30:45.42+00:00

    Hello,

    I haven't found a lot of information about the issue. Did you check Event Logs and Cluster logs? Might help:
    https://blog.sqlauthority.com/2019/01/04/sql-server-unable-to-set-cloud-witness-error-the-client-and-server-cannot-communicate-because-they-do-not-possess-a-common-algorithm/

    As an alternative, you can use StarWind VSAN to configure disk witness on your nodes.
    https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-windows-server-2016/

    Cheers,
    Alex Bykovskyi
    StarWind Software
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    0 comments No comments

  2. Limitless Technology 43,996 Reputation points
    2022-10-14T09:37:07.147+00:00

    Hello there,

    Grant the cluster nodes read/write permissions on the file share, you have to grant the virtual server name of your Windows Server Failover Cluster read/write permissions to the file share. This should be done at the NTFS permission level on top of the shared folder permissions.

    For some users performing the below steps has sorted the issue.

    1) Find cluster - Cluster core resources - Server name - <cluster name resource>. Take it offline;

    2) Right-click on the name - More actions - Repair. This will reset the cluster computer account and its password;

    3) Repeat configuring quorum witness. It should succeed now.

    The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.

    https://social.technet.microsoft.com/Forums/en-US/a038fa07-1a11-4045-9fd5-e38bb49e4f5e/issue-with-adding-a-file-share-witness?forum=winserverClustering

    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/4bccac68-7406-4fb8-92c7-e17d01b6772f/issue-setting-up-my-file-share-witness?forum=sqldisasterrecovery


    --If the reply is helpful, please Upvote and Accept it as an answer–

    0 comments No comments