Quantcast
Viewing all articles
Browse latest Browse all 8719

Alert: Health Set unhealthy - Clustering

We have SCOM 2012 R2 setup to monitor our Exchange 2013 CU5 enviroment and we have gotten this error message about our Clustering going in to an unhealthy state a couple of times.  We have checked the FSW and everything seems OK on its end.  I cannot find much out there on this message, so any help would be greatly appreciated:

Alert: Health Set unhealthy
Source: EXCHANGE04 - Clustering
Path: EXCHANGE04.company.com;EXCHANGE04.company.com
Last modified by: System
Last modified time: 8/24/2014 1:36:35 PM Alert description: The Cluster Group has not been healthy for 7200 minutes. The most recent probe failure message is: Check 'Microsoft.Exchange.Monitoring.QuorumGroupCheck' thrown an Exception!
Exception - Microsoft.Exchange.Monitoring.ReplicationCheckFailedException: QuorumGroup has failed. Specific error is: Quorum resource 'Cluster Group' is not online on server 'exchange06'. Database availability group 'exchDAG' might not be reachable or may have lost redundancy. Error:
  File Share Witness (\\FSW01.company.com\exchDAG.company.com): Offline  is offline. Please verify that the Cluster service is running on the server.

   at Microsoft.Exchange.Monitoring.ReplicationCheck.Fail(LocalizedString error)
   at Microsoft.Exchange.Monitoring.QuorumGroupCheck.RunCheck()
   at Microsoft.Exchange.Monitoring.DagMemberCheck.InternalRun()
   at Microsoft.Exchange.Monitoring.ReplicationCheck.Run()
   at Microsoft.Exchange.Monitoring.ActiveMonitoring.HighAvailability.Probes.ReplicationHealthChecksProbeBase.RunReplicationCheck(Type checkType) Check 'Microsoft.Exchange.Monitoring.QuorumGroupCheck' did not Pass!
Detail Message - Quorum resource 'Cluster Group' is not online on server 'exchange06'. Database availability group 'exchDAG' might not be reachable or may have lost redundancy. Error:
  File Share Witness (\\FSW01.company.com\exchDAG.company.com): Offline  is offline. Please verify that the Cluster service is running on the server.

To add some additional information, when I look in Failover cluster manager this is what I see.  I know when we setup the servers the correct FSW information was being displayed.


Image may be NSFW.
Clik here to view.

Viewing all articles
Browse latest Browse all 8719

Trending Articles