FIX: You receive error messages when you perform a population for a large full-text index in SQL Server 2008

When you perform a population for a large full-text index in Microsoft SQL Server 2008, you may receive an error message in the full-text log file. The number of times that this error message is logged depends on the batch size minus one. For example, on a 32-bit computer, the batch size is 1,000, so the error is logged 999 times. The error message resembles the following: After you receive this error message, you may also receive the following error message for the batch size minus one: After you receive this error message, you may also receive the following error message for the batch size minus one:

This problem occurs because of a bug in the communication between the Sqlservr.exe process and the Fdhost.exe process. When batches are sent from the Sqlservr.exe process to the Fdhost.exe process, sometimes the outbound shared memory (OSM), which is the shared memory from Sqlservr.exe to Fdhost.exe, has insufficient space to fit the next column of a document. When this occurs, the Sqlservr.exe process sends a message to notify the Fdhost.exe process to process all the existing data in the OSM. While the Fdhost.exe process is processing data, the inbound shared memory (ISM), which is the shared memory from Fdhost.exe to Sqlservr.exe, may become full. In this situation, the Fdhost.exe process sends a "rewind" message to the Sqlservr.exe process. This message requests that the Sqlservr.exe process resend the last document from the first column. However, when the Sqlservr.exe process starts to send the document again, it starts from column 2 instead of column 1. This causes the error messages that are mentioned in the "Symptoms" section.

Cumulative update information for the release version of SQL Server 2008

The fix for this issue was first released in Cumulative Update 4 for the release version of SQL Server 2008. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: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 2008 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:

Cumulative update information for SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: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 2008 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:

To work around this problem, increase the ISM size. To do this, configure the ISM_Size variable by using the sp_fulltext_service stored procedure.

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

This problem does not prevent the population from completing. The full-text index has built-in retry logic that will continue to retry the failed entry until it succeeds. Therefore, you can safely ignore the error messages. The only known potential negative side effects are that it may take longer than usual for the population to complete and the full-text log growth increases significantly for the reporting of the error.

The retry logic in the source code causes an eventual successful population without corruption to the index, despite the error message that indicates possible corruption.

More information about cumulative update package 4 for SQL Server 2008

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

More information about cumulative update package 1 for SQL Server 2008 Service Pack 1

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base: 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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: