Microsoft KB Archive/308716

= FIX: Index Is Corrupt When Full-Text Catalog Population Is Interrupted on a Cluster =

Article ID: 308716

Article Last Modified on 10/17/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q308716



BUG #: 352538 (SHILOH_BUGS)

BUG #: 352844 (SHILOH_BUGS)

BUG #:352510 (SHILOH_BUGS)



SYMPTOMS
If a full-text catalog population is interrupted by a failure of the server on which a virtual SQL server is running and a failover occurs to a node where there is at least one other SQL virtual server already running, the following error message may appear in the Microsoft Windows Application Log:

Content index corruption detected in component SmartBuffer1 in catalog g:\mssql80\mssql\ftdata\sql0000700005\build\indexer\cifiles.

Error messages similar to the following may also appear in the Windows Application log when the population resumes after the failover:

Corruption in Content Index data was detected in project .

Resetting project .

Unable to initialize project . Error: c0041800

- The content index is corrupt.

Resetting project .

Unable to load Content Index for project .

Error: c0041800 - The content index is corrupt.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack



WORKAROUND
To work around this problem, rebuild, and then repopulate the full-text catalog after the interrupted population is complete.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Keywords: kbbug kbfix KB308716

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.