Catalog Corruption Occurs after Indexing Is Complete

ID: Q217151

The information in this article applies to:

Microsoft Index Server version 2.0

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

Index Server reports that the catalog is corrupt after the index process is completed. This can occur as soon as the indexing process has completed, or several minutes later.

CAUSE

This occurs when a file is unfilterable and the Filter Retries is set to a number greater than 4. When this happens, the information that the filter process sends to the Content Index Service (CISVS) causes the CISVS to report that the in-memory catalog information is corrupt, even though the data on the drive is fine.

RESOLUTION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

Change the value of the following registry key to a value of 4 or less:

HKEY_LOCAL_MACHINE\system\currentcontrolset\control\contentindex\FilterRetries

After you change this value, restart Index Server.

STATUS

Microsoft has confirmed this to be a problem in Index Server version 2.0.

Additional query words:

Keywords :
Version : winnt:2.0
Platform : winnt
Issue type : kbbug