Exchange 2010 DAG Error – A server-side database availability group administrative operation failed. CreateCluster errors may result from incorrectly configured static addresses. The operation failed…
I came across this error while adding the first DAG member to an Exchange 2010 SP1 DAG. The DAG was created successfully, but adding the first server to the DAG resulted in the following error. Error: A server-side database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured…
I came across this error while adding the first DAG member to an Exchange 2010 SP1 DAG. The DAG was created successfully, but adding the first server to the DAG resulted in the following error.
Error:
A server-side database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: The computer account ‘DAG1’ could not be validated. Access was denied. Check that the current user (NT AUTHORITYSYSTEM) has permissions to create computer accounts in the domain or to claim the computer account. [Server: MBX01.domain.local]
A server-side database availability group administrative operation failed. Error: The computer account ‘DAG1’ could not be validated. Access was denied. Check that the current user (NT AUTHORITYSYSTEM) has permissions to create computer accounts in the domain or to claim the computer account.
I did the following to troubleshoot the issue.
- As it was complaining about access denied, I checked the account I was using and the necessary permissions were in place.
- As the error mentioned about incorrectly configured static IPs, I checked the DAG IP and everything was fine.
- I checked AD to see the permissions on the DAG account (CNO) and to my surprise there was no account with the name DAG1, but Exchange Console created the DAG without errors!
As I was in a rush to get the system up and running, I deleted the DAG, pre-staged the DAG account in AD and gave the first mailbox server full rights on the DAG object and disabled the DAG computer account. Once this was done, DAG creation and member addition went smoothly!
http://support.microsoft.com/kb/2032601
Thanks Sankar
A server-side database availability group administrative operation failed. Error: The operation failed with message: Windows Failover Clustering timed out while trying to validate server ‘A1’. 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. [Server: WIN-0T78VRONQF8.intel.com]
Did you fix it Arunlal?
Thanks Zizi. Giving Exchange Trusted Subsystem full control on the DAG object gives all servers access to the account and hence I only added one server.
This sounds similar to the error described here and the exact same issue I had while deploying Exchange 2010:
http://forums.msexchange.org/m_1800529315/mpage_1/key_/tm.htm#1800530376
The suggested solution from the last comment:
"I had this same issue. After so much web seaching I did not find any direct solution. What worked for me was to add "Exchange Trusted Subsystem" to the OU where the Exchange servers are located and grant it Full Control. Then I was able to add membership to the DAG."