Quantcast
Viewing all articles
Browse latest Browse all 8719

Error when adding new database to Exchange 2013 SP1 DAG

This is a new Exchange 2007/2013 SP1 coexistence.

We are using IP-less DAG in 2013 SP1/Server 2012 R2. (DAG without cluster administrative access point)
There are only 2 members in the DAG and a random witness server.  Servers are MAIL101 and MAIL102 and the witness is AP104.  I've used generic domains so don't get hung up on that below.  Databases are DB1, DB2, DB3... etc..

I get the following error whenever I add a new database to the DAG.

warning
Couldn't communicate with the Microsoft Exchange Replication service on server "MAIL101.us.rootdomain.rootdomain" to pick up new configuration changes for database "DB3 Archive". Make sure that the service is running and that the server has network connectivity. Error: A server-side administrative operation has failed with this error: The database operation failed due to a transient condition. Error: The database operation failed due to a transient condition. Error: Unable to query Active Directory for database 'dbba2bc2-b1ed-4e3a-9b00-56df3e83017e'. You can try the operation again, and you may not get the error. [Database: dbba2bc2-b1ed-4e3a-9b00-56df3e83017e, Server: MAIL101.us.rootdomain.rootdomain]

Please restart the Microsoft Exchange Information Store service on server MAIL101 after adding new mailbox databases. 

After restarting the information store the database seems to mount just fine.  Is this error common or is there something else involved here?  I get initial seeding problems on these databases as well, but again restarting the information store after creating the DAG copy and just waiting a couple minutes or telling it to resume seem to solve the issue as well.

It doesn't ultimately seem to be a problem as I can work around it in the end, but I want to make sure I won't have some sort of long standing problem or if there's a way to solve the warning.


Viewing all articles
Browse latest Browse all 8719

Trending Articles