Skip to main content

Exchange 2010 - A server-side database availability group administrative operation failed. Error: Windows Failover Clustering timed out while trying to validate server 'exchange03'. If this is in a disjoint DNS namespace, the DNS suffixes for all servers in the database availability group must be present on every server.

I was adding amailbox server to a DAG, the mailbox server was in another site than the original DAG members, the wizard fails with the errror "A server-side database availability group administrative operation failed. Error: Windows Failover Clustering timed out while trying to validate server 'exchange03'. If this is in a disjoint DNS namespace, the DNS suffixes for all servers in the database availability group must be present on every server."

as in the screen shot below:


after googling a bit i found this very useful post (http://www.exchangemaster.net/index.php?option=com_content&task=view&id=143&Itemid=1&lang=en) thank you Dejan, you really saved my day.

The issue was that there was an ISA server separating the two sites , the solution was to turn off the option called "Enforce Strict RPC Compliance" in ISA server.

SOLUTION


Turn off the Enforce Strict RPC compliance option in ISA Server.



This option can be found in 2 places:

1) On the firewall rule properties.

2) In the ISA System Policy. This policy is applied to new rules when you create them.



1) To disable the Enforce Strict RPC Compliance option on the firewall rule, right click the firewall rule and selelct Configure RPC Protocol.

















Clear the Enforce Strict RPC compliance option.




2) To disable this option in ISA Server System Policy, select Edit System Policy from the task pane on the right, select Authentication Services, Active Directory. Clear the Enforce Strict RPC compliance.



Credits goes to : http://www.exchangemaster.net/

 

Update

I found also that one of the reasons for this error is if you have multiple AD sites and the computer for the DAG has not replicated  to the site where you are adding the mailbox server to the DAG.
Labels:

Comments

Post a Comment

Popular posts from this blog

Upgrade from Lync Evaluation edition to Lync RTM.

If you have installed Lync Server using the 180 Day  trial bits  you can upgrade to the RTM bits nsing the following easy steps: Run setup.exe on your Lync server Volume License media. Click on "Install or Update Lync server system" Click on "Setup or remove Lync server components" Open CMD and  navigate to \Setup\amd64\setup and then run msiexec.exe /fvomus server.msi EVALTOFULL=1 /qb  Open Lync Server Management Shell and then run Enable-CSComputer and then you are done !
7 comments
Read more

Exchange 2010 - EMC "RBAC authorization returns Access Denied"

I was doing an Upgrade for Exchange 2003 to Exchange 2010 and after i installed the first CAS server and opened the EMC an error appeared that i have no permissions... while i was logged in with the setup account and it was a memeber of the Organization Managemnet Group. and i founbd this in the Applicaiton Log  "(Process w3wp.exe, PID 6716) "RBAC authorization returns Access Denied for user Udomain.Local/Users/AccountName. Reason: No role assignments associated with the specified user were found on Domain Controller XXXXX" " After alot of searches i was pulling my remaining hair out :)  I  found this post ( http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/fc568cc6-8691-4127-b70b-bcc82f9b1f7f?prof=required ) The issue was with 2 things : Allow inheritable permissions check Box was not enabled on the Exchange  Microsoft Exchange Organzaiton container inside the Configuration partition. The value for the attributes msExchRoleLink ...
Post a Comment
Read more

the networkmanager has not yet been initialized

I faced a very strange case with Exchange DAG, I was doing a site resiliency test I failed over to the DR site successfully and then I failed back to the main site, after failing back I found that the DAG was in a state that looks like split brain syndrome although the DAG was running in DAC mode. the symptoms were as follows: From the DR mailbox server: Cluster Console only showed this node while the active nodes were not present. From EMC the copies on the DR server were healthy. From the Main site mailbox servers: Cluster console showed the three nodes but the DR node was stopped, and the option to start it was grayed out. From EMC the copies on the DR server were failed. The fix was as follows:  run the following command: Cluster       /forcecleanup Then run the following: Start-DatabaseAvailabilityGroup "DAGname" -MailboxServer  "DRNodeName" After the first command you will find that the DR node can see the oth...
Post a Comment
Read more