Building an Exchange 2013 DAG in my lab, I was having problems adding a second DAG node. I was getting various errors:

There are no more endpoints available from the endpoint mapper...

Error: This operation returned because the time-out period expired...

And even more in the DAG logs:

Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A server-side database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. ---> Microsoft.Exchange.Cluster.Replay.AmClusterApiException: An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed.. ---> System.ComponentModel.Win32Exception: This operation returned because the timeout period expired

After rebuilding several times did I realize that it could be a result of enabling the failover cluster feature in my template, then cloning it.

 

Found this on TechNet, here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/2c83bdda-7cd4-4ee3-abeb-82b62199f3e1/teredo-and-clustering

It is not supported to SysPrep / Clone OS images once the Failover Clustering feature has been installed.  The NetFT adapter generates it’s MAC address off a hash of the local interface.  If you clone post-feature install, the adapters will generate valid errors.  You need to SysPrep / Clone, then you can have a script to install the Failover Clustering feature in the Run / Run Once.

The fix was to remove the Failover Cluster feature, re-add it and then re-join the servers to the DAG.

 

Tags: Clustering, DAG, endpoints, Exchange, Exchange 2013, hash, interface, microsoft, time out, timeout period