Reseed the Search Catalog

If the content index catalog for a mailbox database copy gets corrupted, you may need to reseed the catalog. Corrupted content indexes are indicated in the Application event log by the following event.

Event ID	Level	Source	Details
123	Error	ExchangeStoreDB	At <timestamp> the Microsoft Exchange Information Store Database <identity> copy on this server experienced a corrupted search catalog. Consult the event log on the server for other "ExchangeStoreDb" and "MSExchange Search Indexer" events for more specific information about the failure. Reseeding the catalog is recommended via the 'Update-MailboxDatabaseCopy' task.

Note

If the mailbox database copy is the only copy, Exchange Search must create a new content index catalog. You can use the ResetSearchIndex.ps1 script to do this.

Looking for other management tasks related to Exchange Search? Check out Managing Exchange Search.

Reseed the content index catalog from any source

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Exchange Search" entry in the Mailbox Permissions topic.

This example reseeds the content index catalog for the database copy DB1 on Mailbox server MBX1 from any source server that has a copy of the database.

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -CatalogOnly

For detailed syntax and parameter information, see Update-MailboxDatabaseCopy.

Reseed the content index catalog from a specific source

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Exchange Search" entry in the Mailbox Permissions topic.

This example reseeds the content index catalog for the database copy DB1 on Mailbox server MBX1 from Mailbox server MBX2, which also has a copy of the database.

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -SourceServer MBX2 -CatalogOnly

For detailed syntax and parameter information, see Update-MailboxDatabaseCopy.