Reseed of catalog failed
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2012-03-08
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
^(5603|5005|5003)$ |
Event Source |
CI Troubleshooter |
Category |
KHI |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Mailbox/Database Search Copy |
Rule Name |
Reseed of catalog failed. |
Explanation
This Error event indicates that the Update-MailboxDatabaseCopy cmdlet did not complete a reseed of the catalog. This error may occur for any of the following reasons:
Disk corruption
Catalog issues
Services not running
Permissions issues
Network issues
User Action
View the error message for Event 5603, for Event 5005, or for Event 5003 in Event Viewer for more information that may help you troubleshoot this issue.
You may be able to resolve this issue by running the following ResetSearchIndex.ps1 script, which can force a rebuild of the catalog for a specific database on your server:
ResetSearchIndex.ps1 [-force] <dbname> [<dbname>]
This process removes and re-creates the index catalog. You can consider the index catalog files to be expendable. If the forced rebuild finds that the catalog is more than seven days out-of-date, the process discards the catalog, and then initiates a new crawl and catalog. The reasons to manually rebuild the index catalog include corruption, accidental deletion, or the simple troubleshooting of search errors.
To determine whether the issue is resolved, use the Update-MailboxDatabaseCopy cmdlet to try to reseed the catalog. For more information about this process, see Update-MailboxDatabaseCopy.
For More Information
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.