Solved

Exchange 2010 DAG Issue

Posted on 2011-03-02
23
2,180 Views
Last Modified: 2012-06-27
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.
0
Comment
Question by:RBrogen
  • 11
  • 8
  • 3
  • +1
23 Comments
 
LVL 7

Expert Comment

by:PraveenBalan
ID: 35024129
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
 
LVL 49

Expert Comment

by:Akhater
ID: 35024301
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
 

Author Comment

by:RBrogen
ID: 35024307
All servers are running the same version of Exchange 2010.  No Anti-Virus software installed yet and Firewalls are disabled..
0
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 49

Expert Comment

by:Akhater
ID: 35024323
i see these are virtual servers, by any chances are they deployed from a template ?
0
 

Author Comment

by:RBrogen
ID: 35024343
They are clean individual builds, no templates.
0
 

Author Comment

by:RBrogen
ID: 35024346
I can ping all DAGReplication ips from each server.
0
 
LVL 49

Expert Comment

by:Akhater
ID: 35024356
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
 
LVL 49

Expert Comment

by:Akhater
ID: 35024358
and also do you have ipv6 disabled on any of the nodes?
0
 

Author Comment

by:RBrogen
ID: 35024363
0
 
LVL 49

Expert Comment

by:Akhater
ID: 35024377
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
 

Author Comment

by:RBrogen
ID: 35024390
I currently have IP6 deselected on both nodes.

The log file you listed is the one I uploaded.
0
 
LVL 49

Expert Comment

by:Akhater
ID: 35024399
you just delselected IPv6 from the NIC ? if that is the case please enable it again on both and try
0
 

Author Comment

by:RBrogen
ID: 35024413
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
 
LVL 49

Expert Comment

by:Akhater
ID: 35024689
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
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 35024815
Are all DAG Members Exchange 2010 SP1?
0
 

Author Comment

by:RBrogen
ID: 35026285
Yes all DAG Members are Exchange 2010 SP1 Version 14.1 (Build 218.15)
0
 

Author Comment

by:RBrogen
ID: 35026319
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
 
LVL 49

Expert Comment

by:Akhater
ID: 35026321
did you try disabling ipv6 from the registry as per my last post ?
0
 

Author Comment

by:RBrogen
ID: 35026537
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
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 35029766
Are you using DHCP for the DAG members or assigning them static IP addresses?
0
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 35029892
0
 

Accepted Solution

by:
RBrogen earned 0 total points
ID: 35084802
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
 

Author Closing Comment

by:RBrogen
ID: 35126307
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

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Read this checklist to learn more about the 15 things you should never include in an email signature.
This article explains how to install and use the NTBackup utility that comes with Windows Server.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question