SOLUTION: Cannot add Exchange Database copy with error: 0xfffffae7. Error: The database was either not found or was not replicated

Problem:

Applies to Exchange 2010 DAG.

Cannot replicate Exchange 2010 database in DAG with error Hresult: 0xfffffae7. Error: The database was either not found or was not replicated

Symptoms:

We needed to replace database and the log disk of the second node of an Exchange 2010 DAG cluster. So I removed the second node from database replication. When the new disk is ready I readded the second replication node to databases but replication failed with the following error.

ExcDagDB17

Failed

Error:

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 ‘Exc1.internal.contoso.com ‘. Hresult: 0xfffffae7. Error: The database was either not found or was not replicated.. [Database: ExcDagDB17, Server: Exc2.internal.contoso.com]

Failed to open a log truncation context to source server ‘EXC1.internal.contoso.com’. Hresult: 0xfffffae7. Error: The database was either not found or was not replicated.

Click here for help… http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.2.342.0&t=exchgf1&e=ms.exch.err.Ex4543D9

Exchange Management Shell command attempted:

Add-MailboxDatabaseCopy -Identity ‘EXCDAGDB17’ -MailboxServer ‘EXC2’ -ActivationPreference ‘2’

Elapsed Time: 00:00:27

The database was either not found or was not replicated.

Resolution:

There are some blogs about deleting registery key DumpsterInfo. But my case there is no such key

So I reseeded all databases using update database copy operation. You don’t need choose  network for seeding. It will use replication network by default. Also it does not allow you to choose Public network with error “Public network is not enabled for replication”. Although in normal DAG operation Public  network may be used even if you disabled replication on it. Select source server for the database and continue.  Depending on your database size it may take 8-10 hours to complete replication.

Advertisements
Gallery | This entry was posted in Exchange Server and tagged . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s