Exchange 2010 DAG Issue

Hello Everyone,

I'm running into a bear of an issue that is supposed to be really simple thing to setup.  I am getting an error when trying to add the 2nd node to my Exchange 2010 DAG.  I have added the Exchange Trusted Subsystem to the Local Administrators group on my servers.  

Here's my configuration and all 3 servers are running in VMWare ESXi 4.1:
3 Servers

Server1
DAGWS - Witness server
Windows 2008 R2 Enterprise SP1
Production NIC
DAGReplication NIC

Server2
Exch1
Windows 2008 R2 Enterprise SP1
Production NIC
DAGReplication NIC

Server3
Exch2
Windows 2008 R2 Enterprise SP1
ProductionNIC
DAGReplication NIC

When I try to add the 2nd node I get this error:
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..

Any assistance would be greatly appreciated.
RBrogenAsked:
Who is Participating?
 
RBrogenConnect With a Mentor Author Commented:
I wound up formatting one of the servers and  the DAG Cluster configured fine.  There appeared to be some pretty bad corruption somewhere as everything was configured fine.
0
 
Praveen BalanSolution ArchitectCommented:
Hope all the above three servers are Exchange 2010 servers, if not the server has to be member of the "Exchange servers"(because if you plan to use DC as Witness, that will not be part of the above said group).

I have explained the DAG configuration details on the below post.

http://www.exchangedictionary.com/index.php/Articles/configure-dag-exchange-2010.html
0
 
AkhaterCommented:
do you have any antivirus/firewall running on your nodes ? like symantec endpoint or such ? if so uninstalling them is the first thing to try
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
RBrogenAuthor Commented:
All servers are running the same version of Exchange 2010.  No Anti-Virus software installed yet and Firewalls are disabled..
0
 
AkhaterCommented:
i see these are virtual servers, by any chances are they deployed from a template ?
0
 
RBrogenAuthor Commented:
They are clean individual builds, no templates.
0
 
RBrogenAuthor Commented:
I can ping all DAGReplication ips from each server.
0
 
AkhaterCommented:
fair enough, when it all fails exchange should point you to a .log file typically in the "C:\ExchangeSetupLogs\DagTasks\" directory

can you please attach it ?
0
 
AkhaterCommented:
and also do you have ipv6 disabled on any of the nodes?
0
 
RBrogenAuthor Commented:
0
 
AkhaterCommented:
did you disable ipv6 on any node?

i also need this log please

The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2011-03-03_04-15-07.593_add-databaseavailabiltygroupserver.log".

0
 
RBrogenAuthor Commented:
I currently have IP6 deselected on both nodes.

The log file you listed is the one I uploaded.
0
 
AkhaterCommented:
you just delselected IPv6 from the NIC ? if that is the case please enable it again on both and try
0
 
RBrogenAuthor Commented:
I reenabled IPV6 on both DAGReplication and Production networks with the same result.

A point to note is that I can remove the server that is in the DAG and add the other one successfully.  I only get the error when I try to add the second server to the DAG.  I've also tried performing the add from each respective server with same results.
0
 
AkhaterCommented:
OK let's try something else totally disable IPv6 (not by deselecting it)
http://support.microsoft.com/kb/929852
reboot the servers and try again
0
 
MegaNuk3Commented:
Are all DAG Members Exchange 2010 SP1?
0
 
RBrogenAuthor Commented:
Yes all DAG Members are Exchange 2010 SP1 Version 14.1 (Build 218.15)
0
 
RBrogenAuthor Commented:
Akhater:  It is my understanding, that ipV6 is required to be available or the HubCas will stop functioning correctly and won't even install if you are starting from scratch.  I'm trying to find the article that I found when I first began tinkering with Exchange 2010 and thought I'd get rid of ipV6 because I wasn't using it and shortly there after my server stopped functioning correctly.
0
 
AkhaterCommented:
did you try disabling ipv6 from the registry as per my last post ?
0
 
RBrogenAuthor Commented:
Akhater:  I did with the same results.  I even removed the existing member and DAG and created a new one with a never before used name and I got the same error.  I briefly mentioned this before as well, I can successfully add either one of the servers to the DAG but I only get the error when I go to add the second  server.  I've tried creating/adding from both nodes.
0
 
MegaNuk3Commented:
Are you using DHCP for the DAG members or assigning them static IP addresses?
0
 
MegaNuk3Commented:
0
 
RBrogenAuthor Commented:
I wound up just formatting the system to remove any corruption.  All settings were correct but something hidden in the registry would not let it work.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.