AlwaysOn Cluster reboot due to file share witness unavailability

Hi Team,
Anyone came across this scenario in AlwaysOn Availability Group (two node), file share witness times out and RHS terminate and cause the cluster node to reboot. File share witness is for continuous
failover and if the resource is unavailable my expectation was that it should go offline and should not impact Server or Sql Server. But its rebooting the cluster node to rectify the issue.
Configuration
Windows Server 2012 R2 (VMs) - two node, file share witness (nfs)
Sql Server 2012 SP2
Errors
A component on the server did not respond in a timely fashion. This caused the cluster resource 'File Share Witness' (resource type 'File Share Witness', DLL 'clusres2.dll') to
exceed its time-out threshold. As part of cluster health detection, recovery actions will be taken. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that is running this resource. Verify
that the underlying infrastructure (such as storage, networking, or services) that are associated with the resource are functioning correctly.
The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource.
Refer to the System event log to determine which resource and resource DLL is causing the issue.
Thanks,
-SreejitG

Thanks Elden, We were using DFS name for the file share! We gave the actual file share name and looks good now.
Few interesting facts, the failure happens exactly between window 12:30 PM to 1:30 AM and it never recorded any error specific to DFS! Not sure if there was any daily maintenance or task happens during the window pertaining to DFS.
+ DFS is not supported or recommended by Microsoft
Do not use a file share that is part of a Distributed File System (DFS) Namespace.
https://technet.microsoft.com/en-us/library/cc770620%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
Thanks,
-SreejitG

Similar Messages

File Share Witness Resouces Errors in a SQL 2012 Alwayson Availability Group Environment

Hi I am getting the following error in WFC Manager and in my system event log:
Event ID1564:
File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\SQL2012ClusterWitnessPath'. Please ensure that file share '\\SQL2012ClusterWitnessPath' exists and is accessible by the cluster.
Event ID 1069:
Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event ID 1205:
The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
These errors showed up every hour on the hour and then suddenly stopped. I tried looking at the cluster.log file but there wasn't anything recorded there. The file share witness shows to be online and my AG did not fail over to another node.
The cluster has read and write permissions to the share. I did not find any error messages about the witness share on the remote server.
I am wondering what caused these series of events to occur?
Thanks.

Hi Kevin Ni,
Thanks for your reply. I have ran the validation test and I have 2 warnings. My environment has 2 nodes and 2 AG's with each node a failover for each AG. So that each node hosts and primary and a secondary of an AG. Both nodes are
on the same subnet. Here are the errors.
- Validate Multiple Subnet Properties
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener1' is set to 1. For the current cluster configuration this value should be set to 0.
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener2' is set to 1. For the current cluster configuration this value should be set to 0.
- Validate Network Communication
Node ONE.domain.com is reachable from Node TWO.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
Node TWO.domain.com is reachable from Node ONE.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
I have node TWO setup with NIC Teaming. Node ONE is also setup with NIC teaming but it also has a second IP address but the second IP address cannot communicate with node TWO.

Quorum location for Failover cluster file share witness

So, I've done quite a bit of searching for what I'm about to propose and I've been able to find nothing.
I currently have a multi site failover cluster hosting separate 2-node SQL clusters at each site connected through an Availability Group. For the failover cluster I am using a file share witness hosted on a server at the primary site. Both sites
are built entirely on vSphere 5.5 and have full replication for the production servers. If the primary site goes down (disaster), I'll need to force quorum in the secondary site to a new file share witness.
Well, I got to thinking...
Why not just replicate the server hosting the file share? I completely understand the reasoning behind not putting the file share witness on DFS, but a replicated virtual server, why not? If the primary site fails, the replicated server hosting
the file share witness is brought online with the rest of the production servers in the DR site. In that case, the only thing that changes is the server IP address, but ultimately, the server name and share where quorum is hosted all stays the same.
Ultimately this prevents needing to find a 3rd geographical/cloud location to host a quorum/witness at. I can't imagine it's this "simple", but maybe it is. If this is possible, and there's not something I'm missing, this essentially
makes the quorum file share witness site agnostic, meaning it could live or be moved anywhere that replication is allowed.
Ideas, thoughts? Am I missing something?
Thanks!
Chris Miller

Most likely it would be better to put this question to the High Availability forum -
https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverClustering
But, might need a more complete definition of your environment. Are you saying that you have multiple 2-node clusters, each with one node in the primary and the second node in the DR site? And you have a single file share server located in primary that
is used to host the file share witnesses for all these clusters? You want to use VMware to replicate the file share server to the DR site so that it can be made available should the primary site fail?
It should work, but it will not be automatic. After all, the replicated VM will need to be brought online at the DR site so the SQL cluster will recognize it. That is not an automatic process. So the cluster will be down until
you bring the file share server online so it can be recognized. Not a whole lot different that simply forcing the DR SQL host to run without quorum.
. : | : . : | : . tim

The "Cluster Group" does not contain a File Share Witness or a Witness disk.

Hi,
I've been given a 4 node Server 2008 R2 cluster to work on. I have a couple of file servers under services and applications (file1 and file2). If I look under storage I see my quorum disk listed in Disk witness under quorum and then I see the file1
and file2 disk resources. Should I be concerned with this warning?

Hi,
Do you mean that you are expecting that you saw the File Share Witness under "Disk Witness in Quorum"?
I just created a cluster and set FSW like this:
However it will not displayed under Disks. It should be caused by design.
My test machines are Windows Server 2012 R2.
If you have any feedback on our support, please send to [email protected]

Exchange 2010 SP3 DAG Flip Flop File Share Witness Issue

Hi All,
We are facing one strange issue with Exchange 2010 SP3.
Our environment is as below
a single DAG spanned accross 2 AD sites with 6 MBX server.
Each site have 3 MBx server.
File Share Witness is on Hub server in primary site.
Note: The DAG IP is from Primary DC VLAN and which cant be streched accross DC due to network restrictions/limitations.
It was working fine till date.
But, yesterday onwards we are facing issue.
All DB dismounted and DAG name disappear from EMC and while doing refresh its giving error as below
Exception type: Microsoft.Exchange.Data.DataValidationException
Exception message: Could not convert property WitnessServer to type UncFileSharePath. Error while converting string 'vesthub700.mydomain.com\DAG1.mydomain.com' to result type Microsoft.Exchange.Data.UncFileSharePath: "vesthub700.mydomain.com\DAG1.mydomain.com"
is not an acceptable path. You must use an absolute, local, long file path, that doesn't contain '~', or a UNC path. Parameter name: path
We are not able to execute any cmdlets related to databaseavailabilitygroup from EMS and its giving same error.
Failover Cluster DAG resource is Flip/Flip continuously.
Its only become stable after reboot of the hub server holding FSW and the 1st mailbox server.(Cluster Owner)
We are even not able to move cluster group to different server.
Performed ExBPA no such issues found which related to DAG.
Performed clsuter validation.
Only generic cluster events in Mailbox servers.
Observation:
Its only become stabe if we remove the msExchFileShareWitness Value for DAG1 using ADSIEdit.
And the problem recurs if we set it back again.
Any help or suggestion is appreciated.
Thanks,
soumen
Soumen Ghosh

Hi Belinda,
Thanks! I have checked the Mailbox Server Application Log and found few 2155 Event Id generated at the time of the issue occured.
Process Microsoft.Exchange.ServiceHost.exe () (PID=9312). Configuration object CN=DAG1,CN=Database Availability Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=com
read from DCTDK35.mydomain.com failed validation. DataValidationException will be thrown. Set event logging level for Validation category to Expert to get additional events about each failure.
One update is that the DAG is stable now after we set an alternate FSW last night.
Regarding the 2nd IP assignment for DAG for the 2nd subnet, we have gone through technet and other sites which refering to add the same from EMC or EMS.
Is it sufficinet to simply adding the 2nd IP to DAG from EMC or EMS? Or do we need to take any other special consideration.
Also, adding another IP it will create one more IP address resource to Failover Cluster, but I belive at a time both the IP wont be online. Do we need to keep it offline manually or its automatically taken care by Exchange.
Please suggest.
Also, regarding executing the CollectOverMetrics.ps1 we are following
http://www.msexchange.org/articles-tutorials/exchange-server-2010/monitoring-operations/monitor-dag-database-failover.html
but failed to execute. Can you suggest the correct parameter.
Thanks,
Soumen
Soumen Ghosh

Exchange Server CCR 2007 unable to see the File Share Witness resulting in mailbox failover ?

Hi people,
Here's my Exchange Server 2007 SP3 in the ideal and normal situation:
Mailbox Server (CCR – Stretched Cluster) Nodes
PRODEXMBX01-VM (Active Mailbox, Quorum) – 10.1.1.53
DREXMBX01-VM (Passive mailbox) – 192.168.1.88
Hub Transport and Client Access Server Nodes
PRODEXHTCAS02-VM – 10.1.1.54
PRODEXHTCAS03-VM (FSW holder) – 10.1.1.55
DREXHTCAS02-VM – 192.168.1.89
Saturday early morning, for some unknown reason the Active Mailbox Server (PRODEXMBX01-VM)
cannot access or see the FSW on the HT server PRODEXHTCAS03-VM, thus
the mailbox gets failover to the DR Mailbox server (DREXMBX01-VM).
Here’s the Events logged:
Log
Name:      System
Source:        Microsoft-Windows-FailoverClustering
Event ID:      1564
Task Category: File Share Witness Resource
Level:Critical
User:          SYSTEM
Computer:      PRODEXMBX01-VM.domain.com
Description:
File
share witness resource 'File Share Witness (\\PRODEXHTCAS03-VM \FSM_DIR_ExMbxCluster01)'
failed to arbitrate for the file share '\\ PRODEXHTCAS03-VM \FSM_DIR_ExMbxCluster01'.
Please ensure that file share '\\ PRODEXHTCAS03-VM \FSM_DIR_ExMbxCluster01'
exists and is accessible by the cluster.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Event ID:      1177
Task Category: None
Level:       Critical
User:     SYSTEM
Computer:PRODEXMBX01-VM.domain.com
Description:
The Cluster service is shutting down because quorum was lost.
This could be due to the loss of network connectivity between some or all nodes
in the cluster, or a failover of the witness disk.
Run
the Validate a Configuration wizard to check your network configuration. If the
condition persists, check for hardware or software errors related to the
network adapter. Also check for failures in any other network components to
which the node is connected such as hubs, switches, or bridges.
So I had to perform manual failover back from DR to production so that both Active mailbox and the Quorum
are held by the Production Mailbox server (PRODEXMBX01-VM).
On Sunday Morning, the Event ID Critical 1564 occurred again thus causing only the quorum only to failover
to the DR mailbox server (DREXMBX01-VM) but the Active mailbox role is still held by the Production Exchange server (PRODEXMBX01-VM).
So now the situation is like the following:
Mailbox Server (CCR – Stretched Cluster) Nodes
PRODEXMBX01-VM (Active Mailbox) – 10.1.1.53
DREXMBX01-VM (Passive mailbox, Quorum) – 192.168.1.88
Hub Transport and Client Access Server Nodes
PRODEXHTCAS02-VM – 10.1.1.54
PRODEXHTCAS03-VM (FSW holder) – 10.1.1.55
DREXHTCAS02-VM – 192.168.1.89
So what causing the mailbox servers unable to contact the File Share Witness?
/* Server Support Specialist */

Did you check the blog above?
The account used in the clustered machine should have access to
\\PRODEXHTCAS03-VM\FSM_DIR_ExMbxCluster01. Please check the permissions. Try giving full permission to admins as well (just to try)
MAS
I've followed this (http://technet.microsoft.com/en-us/library/bb124922(v=exchg.80).aspx) instruction and there is no mentioning other than the Cluster Service Account.
/* Server Support Specialist */

Can I Load Balace a file share witness?

Hi,
I got AlwaysOn Availability Group working with a file share witness.
The file share reside on a server in my network, hence it's a single point of failure.
Can I put a load balancer endpoint for the file share path when configuring the quorum? (After the configuration I will manually copy the files from file share A to file share B, so they will be the same).
My concern is that I don't know if the quorum configuration changes(making the file shares not the same) without me initiating that change(failover or some other event).
Thank You!
(Originally I posted that question in "SQL Server High Availability and Disaster Recovery", but I was asked to move it to here.)

David,
on one hand you say that it is not a single point of failure, but on the other hand you say "or if you have other nodes fail in addition to the FSW". That means that if the FSW is offline I can't have automatic failover, a thing which puts my application
in danger since I relay on automatic failover.
For me not having automatic failover is very bad.
My network is in Azure, the FSW is on one of my web servers(web servers and the database cluster are on different cloud services), since I'm using availability sets I know that at least one web server will be up at any given time. It is possible
that Microsoft will do maintenance or there will be a failure on the infrastructure and the FSW plus one of my sql nodes will be down, I won't have automatic failover in that case.
If you got a solution for me I will be happy to implement it.
Thank You.

Configuring quorum file share witness access denied

in failover cluster administrator, when I try to configure the quorum for file share witness, it keeps coming up and say access denied.
any idea? I created the share as a domain admin and I am running the failover cluster admin as a domain admin

Hi JonDoe321,
From the error information It must the file share folder don’t meet the permission requirement, For the folder that the file share uses, make sure that the administrator has
Full Control share and NTFS permissions, grant the CNO on the file share with full control right, you can refer the following KB to realize the detail requirement.
Failover Cluster Step-by-Step Guide: Configuring the Quorum in a Failover Cluster
http://technet.microsoft.com/zh-cn/library/cc770620(v=ws.10).aspx#BKMK_requirements
More related third party article:
How to configure a Node and File Share Majority quorum
http://www.howtonetworking.com/server/cluster12.htm
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control
these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the
use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

NIC configuration for File Share Witness server

Best practices for a DAG is segment the MAPI or production network and the replication network. On the mailbox servers that are members of a DAG, we have two NICs that are configured differently.
What about the server with the File Share Witness (in my case, we are using a file server, there is not an extra Hub Transport server available).
Should this server be configured for two networks as well?
I'm thinking that the heartbeat traffic would be on the replication network? Or not?
I've read numerous documentation on the subject (Technet, MSExchange, ExchangeServerPro, SimpleTalk, etc..) and have never noticed a section about configuring dual NICs on the FSW server. Which leads me to think... that it is actually the "regular"
NIC that is used.
Can anyone confirm that?
Thanks in advance!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Right, FSW server doesn't need multiple NICs... FSW server is to just give a vote when you have even number of DAG members to make majority. Exchange is going to just lock a small file on the FSW server on the Witness directory, that is all...

DAG File share witness & Quorum best practice

I am building a new environment with 2 x cas & 2 x MBX in site A and 1 x cas and 1 x MBX in DR site B
First of all what happens if I lose/turn off my FSW in a production environment in the middle of the day?
Secondly I have 3 nodes so do I need a FSW?
In a failover to DR site with 1 MBX server do I need a FSW available to mount the databases? can I not just manually mount them?
***Don't forget to mark helpful or answer***

Hi KingMT,
-->First of all what happens if I lose/turn off my FSW in a production environment in the middle of the day?
FYI odd number of DAG member ignores FSW. Please check
this
-->Secondly I have 3 nodes so do I need a FSW?
Same as above answer.
-->In a failover to DR site with 1 MBX server do I need a FSW available to mount the databases? can I not just manually mount them?
In windows 2012 you can configure dynamic quorum. i.e. even if your 2 nodes goes down your 3rd node will be online. But in your case 3rd node is in DR site so we actually not recommend automatic fail over to DR site.
If your bandwidth and latency supports you can configure automatic fail-over else you have to manually mount and prevent automatic fail-over by this command
Set-MailboxServer -Identity EXDR02 -DatabaseCopyAutoActivationPolicy IntrasiteOnly
Please check
this for detals.
Additional Info
Enable DAC on DAG to avoid split brain.
https://technet.microsoft.com/en-us/library/dd979790%28v=exchg.150%29.aspx
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Request advice on File Share Sizing

Hi,
Anyone please advice me about file share with failover cluster on WS2008 R2 or later.
I have a data about 9TB for 1700 users roaming profile. Anyone please advice me about server sizing of failover cluster.
Thank you in advance

Hi,
There is no limitaions related to the maximum size of failover cluster. The existing NTFS limits would also apply to volumes used by failover clusters.
For more detailed information about NTFS and volume limits, please see:
Reviewing Storage Limits
http://technet.microsoft.com/en-us/library/cc773268(v=WS.10).aspx
You could also refer to the article belwo to know the requirements and recommendations for cluster using disk and file share.
Failover Cluster Step-by-Step Guide: Configuring the Quorum in a Failover Cluster
http://technet.microsoft.com/en-us/library/cc770620(v=ws.10).aspx
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Combine AlwaysOn AG with file share cluster

We’re a quite small company, but need HA for services in the DMZ. So we decided on SQL 2012 AlwaysOn AG in order to serve load-balanced web servers. (We do use AlwaysOn AG for SharePoint 2010 and a new critical application.) Now the web servers
in the DMZ also run EPiServer; here we need a HA file share for the AppData folder (BLOB files).
Could we combine these requirements on two servers? Or do we have to install four?
MCTS: Messaging | MCSE: S+M

Yes. If you have shared disks you can create an HA file share on the two cluster nodes that you use for your AlwaysOn AG. But this is an unusual configuration.
Another option is to simply use SQL Server as your HA file share using FileTable.
FILESTREAM and FileTable with AlwaysOn Availability Groups (SQL Server)
The cool thing here is that you get an HA file share without a shared disk. All the files saved to the share would be replicated to the other node by the AlwaysOn AG.
David
David http://blogs.msdn.com/b/dbrowne/

Windows 2003 File Share 4 node Cluster: Does Cluster Resources need to be brought offline prior removing / unmapping any LUN's from SAN end?

Hello All,
Recently, on a 4 node Windows 2003 File Share Cluster, we encountered a problem where when trying to remove few shares (that were no longer in use) directly from SAN end crashed the entire Cluster (i.e., other shares also lost their SAN connectivity). I
suppose the Cluster resources need to be brought offline prior removing it from SAN but I've been advised that these shares were not the root and instead a 'mount point' created within the share; and hence there is no need of bringing down any Cluster resources
offline.
Please can someone comment on the above and provide me detailed steps as to how we go about reclaiming SAN space from specific shares on a W2003 Cluster?
p.s., let me know if you need any additional information.
Thanks in advance.

Hi Alex,
The problem started when SAN Support reclaimed few storage LUNs by unmapping them from our clustered file servers. When they reclaimed the unused LUNs, other SAN drives which were there also disappeared causing the unavailability of file shares.
Internet access is not enabled on these servers. Servers in question are running 64-bit Windows Server 2003 Sp2. This is a four node file share cluster. When the unsued LUN's were pulled, the entire Cluster lost its SAN connectivity. Windows cluster service
was not starting on any of the cluster nodes. To resolve the problem all the four cluster nodes were rebooted after which cluster service started on all the cluster nodes and resources came online.
Some of the events at the time of problem occurrence were,
Event ID     : 57
Raw Event ID : 57
Record Nr.   : 25424072
Category     : None
Source       : Ftdisk
Type         : Warning
Generated    : 19.07.2014 10:49:46
Written      : 19.07.2014 10:49:46
Machine      : ********
Message      : The system failed to flush data to the transaction log.
Corruption may occur.
Event ID     : 1209
Raw Event ID : 1209
Record Nr.   : 25424002
Category     : None
Source       : ClusDisk
Type         : Error
Generated    : 19.07.2014 10:49:10
Written      : 19.07.2014 10:49:10
Machine      : ***********
Message      : Cluster service is requesting a bus reset for device
\Device\ClusDisk0.
Event ID     : 15
Raw Event ID : 15
Record Nr.   : 25412958
Category     : None
Source       : Disk
Type         : Error
Generated    : 11.07.2014 10:54:53
Written      : 11.07.2014 10:54:53
Machine      : *************
Message      : The device, \Device\Harddisk46\DR48, is not ready for access yet.
Let me know if you need any additional info, many thanks.

Windows Failover Cluster (Errors retrieving file shares)

I'm having an issue with Windows Failover Cluster with a Windows Server 2012 R2 machine. I have two cluster nodes (nodeA and nodeB). My issue is that when nodeA is the owner node, and I open failover cluster manager <clusterName> >>
roles >> <fileserver role> >> shares tab it will hang and say that it is loading, but this will occur infinitely. Although when I go to nodeB (not the owner node) and I go to shares it will show me all of the shares that I have. Next when
I go to <clusterName> >> Nodes >> click on Roles tab the information says "There were errors retrieving file shares."
Now when I switch the nobeB to the owner node, I cannot view the shares on that machine but can now view them on nodeA.
We alse have a test network where I have recreated the machines, environment and the failover cluster to as close as the production network as I can except everything works great in the test network

For anybody searching on this later...
I was getting "There were errors retrieving file shares" no matter which node of my cluster
owned the fileshare service. Turns out my problem was that my servers don't have internet access and I had set a system proxy. The fix described in the link below was to exclude the local domain from the proxy.
http://blogs.technet.com/b/askcore/archive/2012/12/03/cluster-aware-updating-cau-interaction-with-proxy-servers.aspx

Cannot Add File Share to (any) File Server Role of a Cluster in Windows Server 2012

Cannot Add File Share to (any) File Server Role of a Cluster in Windows Server 2012...
Get this message in the Operational Log in "FileServices-ServerManager-EventProvider" section of MS-Windows Eventlogs:
Exception: Caught exception Microsoft.Management.Infrastructure.CimException: The xsi:type attribute (MSCluster_Property_Resource_Network_Name) does not identify an existing class.
   at Microsoft.Management.Infrastructure.Internal.Operations.CimSyncEnumeratorBase`1.MoveNext(Boolean discardResultsAndErrors)
   at Microsoft.Management.Infrastructure.Internal.Operations.CimSyncEnumeratorBase`1.MoveNext()
   at Microsoft.FileServer.Management.Plugin.Services.FSCimSession.PerformQuery(String cimNamespace, String queryString)
   at Microsoft.FileServer.Management.Plugin.Services.ClusterEnumerator.BuildNodes(ICimSession session, ClusterRole scopeType, String query, IDictionary`2 groupNameToTypeMap)
   at Microsoft.FileServer.Management.Plugin.Services.ClusterEnumerator.GetClusterClientAccessPointNames(ICimSession session, IDictionary`2 groupNameToTypeMap)
   at Microsoft.FileServer.Management.Plugin.Services.ClusterEnumerator.RetrieveClusterConnections(ComputerName serverName, ClusterMemberTypes memberTypeToQuery)
Thanks for help...(everything else works fine in other type of cluster roles).
Thomas.

This issue also happens in fresh Windows 2012R2 installations, not just upgrades from 2008R2!
I have the issue where I cannot modify any settings on SMB shares. Here is the stacktrace. It appears to be WMI related.
Error: ERROR: Task 'TEST.xxxxxxx.COM-ClusterStorage$-SmbShareUpdate-46bcabf6-1dd4-4a48-a525-5e5d374596c7' has failed: Microsoft.FileServer.Management.Plugin.FSACException: Error occurred while updating an SMB share: The requested operation is not supported.
---> Microsoft.Management.Infrastructure.CimException: The requested operation is not supported.
   at Microsoft.Management.Infrastructure.Internal.Operations.CimSyncEnumeratorBase`1.MoveNext()
   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)
   at Microsoft.Management.Infrastructure.CimSession.ModifyInstance(String namespaceName, CimInstance instance, CimOperationOptions options)
   at Microsoft.FileServer.Management.Plugin.Services.FSCimSession.ModifyInstance(ICimInstance instance)
   at Microsoft.FileServer.Management.Plugin.Services.FSCimSession.ModifyInstance(ICimInstance instance, IEnumerable`1 propertiesWithKeys)
   at Microsoft.FileServer.Management.Plugin.Providers.WmiUpdateTaskBase.DoUpdateInstance(ICimSession session, ICimInstance instance)
   at Microsoft.FileServer.Management.Plugin.Providers.WmiUpdateTaskBase.DoWork(Object sender, DoWorkEventArgs e)
   --- End of inner exception stack trace ---
   at Microsoft.FileServer.Management.Plugin.Providers.WmiUpdateTaskBase.DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

AlwaysOn Cluster reboot due to file share witness unavailability

Similar Messages

Maybe you are looking for