Microsoft Knowledge Base Email Alertz

(217151) - 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.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 217151 - Last Review: May 30, 2004 - Revision: 2.0

Catalog corruption occurs after indexing is complete

This article was previously published under Q217151
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://kbalertz.com/Feedback.aspx?kbNumber=256986/EN-US/ ) Description of the Microsoft Windows Registry

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 behavior occurs if a file is unfilterable and the value of the Filter Retries registry key is set to a number that is less 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: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Change the value of the following registry key to 4 or greater:
HKEY_LOCAL_MACHINE\system\currentcontrolset\control\contentindex\FilterRetries
After you change this value, restart Index Server.

STATUS

Microsoft has confirmed that this is a problem in Index Server version 2.0.

APPLIES TO
  • Microsoft Index Server 2.0
Keywords: 
kbbug kbpending KB217151
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate