FIX: Error message when you run a full-text query against a catalog in SQL Server 2005: “The execution of a full-text query failed. The content index is corrupt.”

Article translations Article translations
Article ID: 938243 - View products that this article applies to.
Bug #: 50001194 (SQL Hotfix)
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.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by the hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

Consider the following scenario. You run a full-text query against a catalog in Microsoft SQL Server 2005. The query may be very complex or retrieve lots of data. At the same time, the catalog is being rebuilt. In this scenario, you may receive the following error message when you run the query:
Msg 7619, Level 16, State 1, Line 1
The execution of a full-text query failed. "The content index is corrupt."
Additionally, a minidump file is generated on the server. The following error message is logged in the SQL Server 2005 error log:
An index corruption was detected in component SmartBuffer1 in catalog CatalogName.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have SQL Server 2005 Service Pack 2 installed on the computer. For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You have to restart the Microsoft Search service and the SQL Server service after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
SQL Server 2005, 32-bit version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Chsbrkr.dll12.0.7822.01,684,84022-Jun-200709:22x86
Chtbrkr.dll12.0.7822.06,112,61622-Jun-200709:22x86
Databasemailprotocols.dll9.0.3179.046,44803-Jul-200708:23x86
Fteref.dll12.0.7822.0446,46422-Jun-200709:22x86
Infosoft.dll12.0.7822.0468,32822-Jun-200709:22x86
Korwbrkr.dll12.0.7822.071,01622-Jun-200709:22x86
Langwrbk.dll12.0.7822.0136,55222-Jun-200709:22x86
Microsoft.analysisservices.dll9.0.3179.01,217,90403-Jul-200708:23x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3179.0296,30403-Jul-200708:23x86
Msfte.dll12.0.7822.02,430,31222-Jun-200709:22x86
Msftefd.exe12.0.7822.066,92022-Jun-200709:22x86
Msftepxy.dll12.0.7822.095,59222-Jun-200709:22x86
Msftesql.exe12.0.7822.095,59222-Jun-200709:22x86
Msir5jp.dll5.0.2130.03,159,91222-Jun-200709:22x86
Msmdlocal.dll9.0.3179.015,948,14403-Jul-200708:23x86
Mssqlsystemresource.ldfNot applicable524,28803-Jul-200701:18Not applicable
Mssqlsystemresource.mdfNot applicable40,108,03203-Jul-200701:18Not applicable
Nlhtml.dll12.0.7822.0124,26422-Jun-200709:22x86
Nls400.dll5.0.4217.012,240,74422-Jun-200709:22x86
Odsole70.dll2005.90.3179.059,24803-Jul-200708:23x86
Query.dll12.0.7822.048,48822-Jun-200709:22x86
Rdistcom.dll2005.90.3179.0644,97603-Jul-200708:23x86
Replmerg.exe2005.90.3179.0320,88003-Jul-200708:23x86
Replrec.dll2005.90.3179.0784,75203-Jul-200708:23x86
Sqlaccess.dll2005.90.3179.0350,57603-Jul-200708:23x86
Sqlagent90.exe2005.90.3179.0349,55203-Jul-200708:23x86
Sqlservr.exe2005.90.3179.029,194,60803-Jul-200708:23x86
Sqlwep.dll2005.90.3179.090,99203-Jul-200708:23x86
Sqsrvres.dll2005.90.3179.070,51203-Jul-200708:23x86
Sysdbupg.sqlNot applicable510,62205-Jun-200718:12Not applicable
Thawbrkr.dll12.0.7822.0206,18422-Jun-200709:22x86
Xmlfilt.dll12.0.7822.0197,99222-Jun-200709:22x86
Xpstar90.dll2005.90.3179.0298,86403-Jul-200708:23x86

SQL Server 2005, x64-based version

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Chsbrkr.dll12.0.7822.01,694,05622-Jun-200710:51x64
Chtbrkr.dll12.0.7822.06,109,03222-Jun-200710:51x64
Databasemailprotocols.dll9.0.3179.046,44803-Jul-200709:52x86
Fteref.dll12.0.7822.0433,15222-Jun-200710:51x64
Infosoft.dll12.0.7822.0621,41622-Jun-200710:51x64
Korwbrkr.dll12.0.7822.0101,73622-Jun-200710:51x64
Langwrbk.dll12.0.7822.0236,90422-Jun-200710:51x64
Microsoft.analysisservices.dll9.0.3179.01,217,90403-Jul-200709:23x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3179.0296,30403-Jul-200709:23x86
Msfte.dll12.0.7822.03,808,10422-Jun-200710:51x64
Msftefd.exe12.0.7822.099,17622-Jun-200710:51x64
Msftepxy.dll12.0.7822.0127,33622-Jun-200710:51x64
Msftesql.exe12.0.7822.0158,56822-Jun-200710:51x64
Msir5jp.dll5.0.2130.03,421,54422-Jun-200710:51x64
Msmdlocal.dll9.0.3179.015,948,14403-Jul-200709:23x86
Mssqlsystemresource.ldfNot applicable524,28803-Jul-200702:18Not applicable
Mssqlsystemresource.mdfNot applicable40,108,03203-Jul-200702:18Not applicable
Nlhtml.dll12.0.7822.0191,84822-Jun-200710:51x64
Nls400.dll5.0.4217.014,101,35222-Jun-200710:51x64
Odsole70.dll2005.90.3179.090,48003-Jul-200709:52x64
Query.dll12.0.7822.068,45622-Jun-200710:51x64
Rdistcom.dll2005.90.3179.0828,78403-Jul-200709:52x64
Replmerg.exe2005.90.3179.0417,64803-Jul-200709:52x64
Replrec.dll2005.90.3179.01,011,56803-Jul-200709:52x64
Sqlaccess.dll2005.90.3179.0357,74403-Jul-200709:52x86
Sqlagent90.exe2005.90.3179.0429,42403-Jul-200709:52x64
Sqlservr.exe2005.90.3179.039,634,80003-Jul-200709:52x64
Sqlwep.dll2005.90.3179.090,99203-Jul-200709:23x86
Sqlwep.dll2005.90.3179.0123,76003-Jul-200709:52x64
Sqsrvres.dll2005.90.3179.083,31203-Jul-200709:52x64
Sysdbupg.sqlNot applicable510,62205-Jun-200719:12Not applicable
Thawbrkr.dll12.0.7822.0209,76822-Jun-200710:51x64
Xmlfilt.dll12.0.7822.0271,20822-Jun-200710:51x64
Xpstar90.dll2005.90.3179.0550,25603-Jul-200709:52x64

SQL Server 2005, Itanium architecture version

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Chsbrkr.dll12.0.7822.01,883,49622-Jun-200710:06IA-64
Chtbrkr.dll12.0.7822.06,153,57622-Jun-200710:06IA-64
Databasemailprotocols.dll9.0.3179.046,44803-Jul-200713:27x86
Fteref.dll12.0.7822.0433,15222-Jun-200710:06IA-64
Infosoft.dll12.0.7822.01,915,24022-Jun-200710:06IA-64
Korwbrkr.dll12.0.7822.0182,63222-Jun-200710:06IA-64
Langwrbk.dll12.0.7822.0333,16022-Jun-200710:06IA-64
Microsoft.analysisservices.dll9.0.3179.01,217,90403-Jul-200709:23x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3179.0296,30403-Jul-200709:23x86
Msfte.dll12.0.7822.07,072,10422-Jun-200710:06IA-64
Msftefd.exe12.0.7822.0173,41622-Jun-200710:06IA-64
Msftepxy.dll12.0.7822.0135,52822-Jun-200710:06IA-64
Msftesql.exe12.0.7822.0294,76022-Jun-200710:06IA-64
Msir5jp.dll5.0.2130.03,824,48822-Jun-200710:06IA-64
Msmdlocal.dll9.0.3179.049,904,49603-Jul-200713:28IA-64
Mssqlsystemresource.ldfNot applicable524,28803-Jul-200702:18Not applicable
Mssqlsystemresource.mdfNot applicable40,108,03203-Jul-200702:18Not applicable
Nlhtml.dll12.0.7822.0295,78422-Jun-200710:06IA-64
Nls400.dll5.0.4217.014,750,05622-Jun-200710:06IA-64
Odsole70.dll2005.90.3179.0179,56803-Jul-200713:28IA-64
Query.dll12.0.7822.0123,24022-Jun-200710:06IA-64
Rdistcom.dll2005.90.3179.01,885,55203-Jul-200713:28IA-64
Replmerg.exe2005.90.3179.0957,29603-Jul-200713:28IA-64
Replrec.dll2005.90.3179.02,145,13603-Jul-200713:28IA-64
Sqlaccess.dll2005.90.3179.0352,11203-Jul-200713:28x86
Sqlagent90.exe2005.90.3179.01,254,25603-Jul-200713:28IA-64
Sqlservr.exe2005.90.3179.072,892,78403-Jul-200713:28IA-64
Sqlwep.dll2005.90.3179.090,99203-Jul-200709:23x86
Sqlwep.dll2005.90.3179.0221,04003-Jul-200713:28IA-64
Sqsrvres.dll2005.90.3179.0147,31203-Jul-200713:28IA-64
Sysdbupg.sqlNot applicable510,62205-Jun-200719:12Not applicable
Thawbrkr.dll12.0.7822.0253,28822-Jun-200710:06IA-64
Xmlfilt.dll12.0.7822.0445,80022-Jun-200710:06IA-64
Xpstar90.dll2005.90.3179.0966,00003-Jul-200713:28IA-64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

After you apply this hotfix, you must run the following statements for each affected catalog. Additionally, you must run these statements for every newly created catalog or for catalogs that are rebuilt.
declare @mmchkpt_interval int
set @mmchkpt_interval = 1048576 -- 1Gigabyte (GB)
exec sp_fulltext_MasterMergeCheckpointInterval
'CatalogName', @mmchkpt_interval
go
Note In this code, CatalogName is a placeholder for the catalog name.

After you run these statements for a catalog, you run the following statement.
exec sp_fulltext_MasterMergeCheckpointInterval 'CatalogName '
After you run the statement, you receive the following result:
master_merge_checkpoint_interval 1048576
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 938243 - Last Review: October 8, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard 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
Keywords: 
kbautohotfix kbexpertiseadvanced kbfix kbqfe kbHotfixServer KB938243

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com