XADM: How to Restore Content Indexing If the Full-Text Indexing Catalog Is Corrupted (305171)

SUMMARY

This article describes how to restore content indexing if the full-text indexing (content indexing) catalog is corrupted on an Exchange 2000 server. For example, the full-text indexing catalog may be corrupted if hardware fails on the Exchange 2000 server. After the catalog is corrupted, content indexing may run but it does not index any documents. In addition, the application event log may log the following event ID message:

Source: Microsoft Search
Event ID: 3047
Description:
The end of the incremental crawl for project Project_id has been detected. The Gatherer successfully processed 0 documents totaling 0K. It failed to filter 0 documents. 0 URLs could not be reached or were denied access.

If you delete the full-text index, and then re-create it, you still cannot use content indexing successfully.

MORE INFORMATION

To resolve this issue, delete the property store and all the log files, and then re-create them. To do so:

Start the Exchange System Manager snap-in, and then browse to the following location:
Organization\Administrative Groups\Administrative_Group\Servers\Server\Storage_Group\Mailbox Store object
Right-click the applicable mailbox store, and then delete the full-text index.
Open the ExchangeServer_Server_name folder, and then delete the .edb, .log, and .chk files.
In Exchange System Manager, browse to the following location:
Organization\Administrative Groups\Administrative_Group\Servers\Server\Storage_Group\Mailbox Store object
Right-click the applicable mailbox store, and then re-create a full-text index for the appropriate store.

The property store and the property store logs are re-created when the full-text indexing catalog is re-created.