When you create a Mailbox database in a multi-site topology AD environment and immediately add this Mailbox database to a DAG (Database Availability Group) on a Microsoft Exchange Server 2010 server, the operation may fail. Additionally, you receive the following error message in Exchange Management Console:
Add-MailboxDatabaseCopy : A source-side operation failed. Error An error occurred while running prerequisite checks. Error: The specified database isn't configured for replication and therefore cannot be used to perform seed operations.. [Database: Mailbox Database, Server: Server]
Or:
A source-side operation failed. Error An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server
↑ Back to the top
This issue may occur because the Add-MailboxDatabaseCopy cmdlet utilizes different DC�s (Domain Controllers) in different parts of the task and the DC�s may inconsistent due to site replication delay.
Operation failure and similar errors may also occur using Mount-Database, Add-MailboxDatabaseCopy, Update-MailboxDatabaseCopy and Set-MailboxDatabase cmdlets.
↑ Back to the top
To resolve this issue, create the new database, force Active Directory replication, or wait until the replication occurs between the sites, and then update the Mailbox Database Copy using the Add-MailboxDatabaseCopy cmdlet.
↑ Back to the top
You cannot create a new Exchange Server 2010 Mailbox database in a multiple domain environment
http://support.microsoft.com/default.aspx?scid=kb;EN-US;977960
For more information about the Update-MailboxDatabaseCopy cmdlet, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/dd351100.aspx
↑ Back to the top
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See
Terms of Use for other considerations.
↑ Back to the top