Strange errors when creating a new DAG

Good afternoon, all!

I'm setting up a new Exchange infrastructure for my company and want to implement DAG.  I have a test environment I'm using to profile the new production setup.  The DAG completes, but I can't add servers to the DAG - "Access is denied" error on a cluster operation followed by an error in finding the FQDN for the DAG that was successfully created. 

Here are the errors (sanitized for your protection):

ERROR

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: ". Error: Access is denied" [Server: exchg2.test.local]
ERROR

The fully qualified domain name for node 'TestDAG07' could not be found.

Maybe my Google-fu is weak after lunch - if someone knows about where to look and what permissions are needed for this, I'd be most grateful for any pointers.

Thanks for looking!

G

July 14th, 2015 5:45pm

Have seen this when Server computer account doesn't have enough permission on the cluster AD object.

Can you try following "PRE-STAGING THE CLUSTER NAME OBJECT" portion (specially disabling the cluster object & assign full permissions to all nodes that you are planning to add) of below article?

http://exchangeserverpro.com/installing-an-exchange-server-2013-database-availability-grou

July 14th, 2015 6:42pm

Hi Gregg,

Thank you for your question.

Because of permission changes in Windows 2012 for computer objects, when implementing DAG and the Mailbox servers are running on Windows 2012the Computer Name Object (CNO) must be pre-staged and provisioned.

We could refer to the following link to resolve this case:

http://blogs.technet.com/b/meamcs/archive/2014/02/13/exchange-2013-and-windows-2012-error-when-try-to-add-server-to-the-dag.aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

July 15th, 2015 4:29am

Hi Gregg,

Thank you for your question.

Because of permission changes in Windows 2012 for computer objects, when implementing DAG and the Mailbox servers are running on Windows 2012the Computer Name Object (CNO) must be pre-staged and provisioned.

We could refer to the following link to resolve this case:

http://blogs.technet.com/b/meamcs/archive/2014/02/13/exchange-2013-and-windows-2012-error-when-try-to-add-server-to-the-dag.aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Free Windows Admin Tool Kit Click here and download it now
July 15th, 2015 4:29am

Hello, Amit!

Thanks for the answer on this - and the Exchange Server Pro blog is excellent - lots of pictures for reference!  I went back through and deleted/re-did all the steps and found some places where I had not read closely enough or some information wasn't clear. 

TL:DR - these steps, along with the first article, were the key.

Thanks!

G

July 15th, 2015 1:37pm

Hello, Amit!

Thanks for the answer on this - and the Exchange Server Pro blog is excellent - lots of pictures for reference!  I went back through and deleted/re-did all the steps and found some places where I had not read closely enough or some information wasn't clear. 

TL:DR - these steps, along with the first article, were the key.

Thanks!

G

Free Windows Admin Tool Kit Click here and download it now
July 15th, 2015 1:37pm

Hello, Jim!

As noted above, I had some errors arising from a confusion regarding Server 2012 and 2012 R2 - my servers are R2-based and the requirements about pre-staging weren't clear.  I went ahead and deleted everything and re-did the steps and it worked.

Thanks!

G

July 15th, 2015 1:39pm

Hello, Jim!

As noted above, I had some errors arising from a confusion regarding Server 2012 and 2012 R2 - my servers are R2-based and the requirements about pre-staging weren't clear.  I went ahead and deleted everything and re-did the steps and it worked.

Thanks!

G

Free Windows Admin Tool Kit Click here and download it now
July 15th, 2015 1:39pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics