This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
You have a computer that is running Microsoft SQL Server 2005. The content index may be corrupted when the master merge process for a full-text search is paused by an external process. For example, this external process is performing a full backup of the database.
When this occurs, the following error message is logged in the SQL Server error log file:
<Data Time> spid<ID>s Informational: Full-text catalog health monitor reported a failure for catalog '<catalog name>' ('<catalog id>') in database '<databaseName>' ('<dbid>'). Reason code: 5. Error: 0xc0041800(The content index is corrupt.). The catalog is corrupted and all in-progress populations will be stopped. Use rebuild catalog to recover the failure and start population from scratch.
Additionally, the following error message is logged in the full-text search log file:
<TRC time="<Date Time>" tagname="FTEAdmin" pid="0x13d0" tid="0x1690"> <MSG><msgtype>Heartbeat</msgtype><catalog>SQLFT0000500076</catalog><state>Forced Paused</state><stateSourceHR><HR>The content index is corrupt.
This problem occurs because the number of records at the top level of an index Directory file does not match the number of records at the page level of this index Directory file.
The fix for this issue was first released in Cumulative Update 9 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
980176 Cumulative update package 9 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about full-text indexing and the querying process, visit the following Microsoft Developer Network (MSDN) Web site:
Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Workgroup Edition, Microsoft SQL Server 2005 Standard X64 Edition, Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems, Microsoft SQL Server 2005 Enterprise X64 Edition, Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems