I receive error 'The catalog is corrupt' when performing an Index Server search, what can I do?

John Savill

January 8, 2000

1 Min Read
ITPro Today logo in a gray background | ITPro Today

A. Index Server catalogs can be caused by unsafe computer shutdowns,system crashes, or applications that write to or lock the catalog files whileIndex Server is active.

Normally, Index Server attempts to fix any corruption automatically; however,sometimes it is necessary to manually fix the corruption.

To do manually fix the corruption, stop and restart the Content Indexservice, For Index 1.x, stop and restart the World Wide Web service, underWindows 2000 start the Computer Management MMC snap-in, expand 'ServerApplications and Services', right click on 'Indexing Service' and stop thenstart.  This normally causes Index Server to rebuild the catalog.

If this does not work, stop Index Server again, locate the Catalog.wcifolder, and delete the contents of the folder. This manually deletes thecatalog. When you restart Index Server, the catalog is re-created.

This can also occur when a file is unfilterable and the Filter Retries is setto a number greater than 4. When this happens, the information that the filterprocess sends to the Content Index Service (CISVS) causes the CISVS to reportthat the in-memory catalog information is corrupt, even though the data on thedrive is fine.

To correct set retry value to 4 or less:

  1. Start the registry editor (regedit.exe)

  2. Move to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlContentIndex

  3. Double click FilterRetries

  4. Change to 4 or below and click OK

  5. Restart Index Server

About the Author

Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like