Fixing File Share Quorum Configuration Access is Denied

Helping businesses improve reliability and efficiency of SQL Server

Couple of days ago while working on Always on setup in my personal lab I encountered an interesting error. For testing and experiment I was using File Share as witness during cluster configuration and it won’t allow me creating File Share witness and throwing Access is denied error. Fixing file share quorum configuration access is denied error message was simple one and I think it will help you as well, so here is the trick.

Fixing File Share Quorum Access is denied

I was pretty sure that it was permission issue but somehow I had to struggle for about 20 minutes before I figure out the exact issue.

Fixing file share quorum configuration access is denied

Part 1 – NTFS Permission

  1. Go to the File Share location
  2. Open the properties and go to Security tab > Add
  3. In the Object Types select “Computers”
  4. Location must be “Domain Forest”
  5. Once you click find now you will see computers DNS names
  6. select participating nodes and cluster virtual name
  7. In my case it is “SSCAG01, SSCAG02 and SSCAGPOC”
  8. Allow full control to each of them

Part 2 – Share Permission

  1. Go to the Folder > Properties
  2. Click on Sharing > Advanced Sharing
  3.  Click on Permissions
  4. Here, you will have to add participating nodes and cluster virtual name
  5. In my case it is “SSCAG01, SSCAG02 and SSCAGPOC”
  6. assign them the full control

Before this workaround, the Share permission will look like below:

Fixing file share quorum configuration access is deniedFixing file share quorum configuration access is denied

 

 

 

 

 

 

Once you update the permissions as mentioned in Part 2 it should look like below

Fixing file share quorum configuration access is denied

 

 

 

 

 

 

 

 

 

 

 

 

 

We are done with the permission part for Share and NTFS, run the wizard and add File Share as quorum and you will be able to add file share as quorum successfully.

If you encounter such issues please refer to this article Resolving High CPU usage in SQL Server.