A customer of mine went upgraded one node of a two node DAG from Exchange 2013 CU7 to Exchange 2013 CU10. After installing the update on the first cluster node, they contacted us complaining complaining that the DAG was no longer available online in Failover Cluster Manager.
The following error was presented when attempting to bring the cluster online:
Failed to bring the resource 'Cluster Name' online.
Error code 0x80071736
The resource failed to come online due to the failure of one or more provider resources.
The resource it was complaining about was the Cluster IP address was unavailable (10.10.0.245).
In addition to this error, the following errors were logged in event viewer on a regular basis.
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 26/10/2015 8:45:01 AM
Event ID: 10028
Task Category: None
Level: Error
Keywords: Classic
User: DOMAIN\administrator
Computer: Exchange1.domain.local
Description:
DCOM was unable to communicate with the computer DAG1.domain.local using any of the configured protocols; requested by PID 6bc4 (C:\Windows\system32\ServerManager.exe).
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 26/10/2015 9:58:05 AM
Event ID: 1223
Task Category: IP Address Resource
Level: Error
Keywords:
User: SYSTEM
Computer: AB-EXCH-01.domain.local
Description:
Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 1' is not configured to allow client access. Please use the Failover Cluster Manager snap-in to check the configured properties of the cluster network.
These cluster nodes both had two interfaces:
After patching one of the Exchange 2013 servers the MapiDagNetwork got disabled on the with IgnoreNetwork set to true on the DagGroupNetwork. As this DAGNetwork contained the DAG cluster IP address 10.10.0.245 (within the 10.10.0.0/20 subnet), it forced the cluster offline. To re-enable the cluster we simply needed to set IgnoreNetwork to false.
After setting IgnoreNetwork to false, we were able to manually start the DAG in FailoverManager by right clicking and clicking Bring Online.
The following error was presented when attempting to bring the cluster online:
Failed to bring the resource 'Cluster Name' online.
Error code 0x80071736
The resource failed to come online due to the failure of one or more provider resources.
The resource it was complaining about was the Cluster IP address was unavailable (10.10.0.245).
In addition to this error, the following errors were logged in event viewer on a regular basis.
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 26/10/2015 8:45:01 AM
Event ID: 10028
Task Category: None
Level: Error
Keywords: Classic
User: DOMAIN\administrator
Computer: Exchange1.domain.local
Description:
DCOM was unable to communicate with the computer DAG1.domain.local using any of the configured protocols; requested by PID 6bc4 (C:\Windows\system32\ServerManager.exe).
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 26/10/2015 9:58:05 AM
Event ID: 1223
Task Category: IP Address Resource
Level: Error
Keywords:
User: SYSTEM
Computer: AB-EXCH-01.domain.local
Description:
Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 1' is not configured to allow client access. Please use the Failover Cluster Manager snap-in to check the configured properties of the cluster network.
These cluster nodes both had two interfaces:
- Mapi Interface
- Replication Interface
After setting IgnoreNetwork to false, we were able to manually start the DAG in FailoverManager by right clicking and clicking Bring Online.
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon