FIX: Index Is Corrupt When Full-Text Catalog Population Is Interrupted on a Cluster (308716)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
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 <SQLServer$I1
SQL0000700005>.
Resetting project <SQLServer$I1 SQL0000700005>.
Unable to initialize project <SQLServer$I1 SQL0000700005>. Error: c0041800
- The content index is corrupt.
Resetting project <SQLServer$I1 SQL0000700005>.
Unable to load Content Index for project <SQLServer$I1 SQL0000700005>.
Error: c0041800 - The content index is corrupt.
RESOLUTIONTo 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.
STATUSMicrosoft 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.
| Modification Type: | Major | Last Reviewed: | 10/17/2003 |
|---|
| Keywords: | kbbug kbfix KB308716 |
|---|
|