Create a DAG with Exchange 2013 – Troubleshooting

Hi,

A lot of you tried to create a DAG (database Availability Group) with Microsoft Exchange 2013. Me too…So a lot of you get many errors when you tried to add DAG member. Most of issues are found with the couple Active Directory under Windows Server 2012 + Exchange Server 2013. Most of issues and error list below are not present if you are using an Active Directory under Windows Server 2008 R2.

So you’ve installed two Exchange 2013 with the Mailbox role and you decide to create the DAG with those two server. So you create a DAG…so good so far, no errors 🙂

Now you decide to add the first member to your DAG. Hello problems 😉

 

First Issue:  ACCESS DENIED

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 ‘”CreateCluster() failed with 0×5. Error: Access is denied”‘ failed.. [Server: MBX1.fabrikam.int]

Cause: the ECP wizard tried to add the first mailbox server to the DAG. During this process the wizard create a computer object in Active Directory (the CNO). This object don’t have the good rights. Exchange Trusted Subsystem had special permissions assigned and not “Full Control” on CNO.
Resolution: assign “Full Control” to Exchange Trusted Subsystem on the CNO.

 

Second Issue: DNS Host Name

An Active Manager operation failed with a transient error. Please retry the operation. Error: The fully qualified domain name for node '<DAG Group Name>' could not be found.

Cause: if you go in the property of the CNO, in the tab ‘general’, you will see the field “DNS name” empty. The ECP cannot find this information, that’s why you have this message.

dag_dns

Resolution: go in the property of the CNO, in the tab ‘attribute’ tab and search for the “dNSHostName” attribute. Enter the FQDN of the CNO and apply.

dag_dns2

 

Third Issue: CNO not disable

A computer account named 'mydag2' already exists and is enabled. The account must be disabled in order to be used by the database availability group.

Cause: the CNO is enable. To operate the ECP need to have the CNO disable. The ECP will enable the CNO himself.
Resolution: GO in Active Directory and disable the CNO.

ok now you can add your mailbox server to your DAG 🙂 Well just one last question: why the ECP failed to create correctly the CNO? I don’t have this answer but if you read the technet article “Managing DAG” you will find a section named “Pre-staged the Cluster Network Object for DAG”.
This section explain to you that you can pre create the CNO manually and disable it. If you follow this technet you should not have the issue 1 and 3 describe in the post. However you will still have the issue 2 or you will have to change the attribute “dNSHostName” during the creation of the CNO (the best way to do FMO).

 

15 thoughts on “Create a DAG with Exchange 2013 – Troubleshooting

  1. Thanks Arnaud – I had all 3 issues in my test lab because a. I hadn’t read the manual, and b. I’d tried creating a cross-domain DAG previously (which I’m pretty sure isn’t supported, but thought I’d give it a go anyway) – now my DAG is up and running thanks to your blog – cheers!

  2. I’m having the FQDN error still. I’ve added the dNSHostName attribute but it is still failing with the same error. Any ideas?

    • Hi,

      are you using server 2012? maybe the server don t see the modification for the moment. Do you still have the same issue? I ask you this question cause I was in vacation I cannot respond before today and your message message has already 6 days.

  3. Pingback: Migration von Exchange 2010 auf 2013 / Troubleshoot | Stephan Verstegen

    • lol…you re welcome. I have a lot of article to publish but not a lot of time currently… Next week I will post more, keep in touch 😉

    • Thx Tiraj, you re welcome. I don t post a lot but I try to post only really helpful infos. Do not hesitate to suscribe to rss or other 😉

  4. A server-side database availability group administrative operation failed with a transient error. Please try the operation again. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed:

    MY Solution was:
    Start the Remote Registry Service – open the services panel and make sure that the Remote Registry Service is running and configured for automatic startup

Leave a Reply

Your email address will not be published. Required fields are marked *

*