Article ID: 2270849 - Last Review: August 25, 2010 - Revision: 1.0 Error 0x80040e97 can occur when indexing large document with integrated full-text search
SYMPTOMSWhen you index large or complex documents with SQL Server 2008 or SQL Server 2008 R2 integrated full-text search, you may receive timeout errors similar to the following: 2010-06-07 15:02:44.64 spid10s Error '0x80040e97' occurred during full-text index population for table or indexed view '[db1].[dbo].[Images]' (table or indexed view ID '622625261', database ID '171'), full-text key value '2375057'. Attempt will be made to reindex it. CAUSEWhile indexing data types such as varbinary, varbinary(max), image or xml, SQL Server sends data to the filter daemon process (fdhost.exe) for indexing. At any point during indexing, SQL Server will not wait for more than 60 seconds for fdhost.exe to respond. For large XML documents, the XML Filter hosted by fdhost.exe, reads in all the data from SQL Server and stores it in a temporary file. It then starts to process the XML content for filtering and word-breaking. If this process takes more than 60 seconds, then SQL Server terminates that batch and retries the operation with a smaller batch size. If an individual XML document is so big that it takes fdhost.exe more than 60 seconds to filter and break the words, then you can experience error documented in the Symptoms section. Note: The issue can happen with any IFilter that writes data to a temporary file. RESOLUTIONYou can resolve this problem by increasing the full-text indexing time out value by calling sp_fulltext_service with ‘ft_timeout’ as the first parameter and a number (in terms of milliseconds) as the second parameter. The example below will increase full-text indexing timeout to 20 minutes for any individual document. MORE INFORMATIONError 0x80040e97 can also be raised for other reasons as well. For example, you may see the same error code when SQL Server experiences issues loading an iFilter. Increasing the Timeout value in such cases may mask the error and prevent effective troubleshooting. Therefore, we recommend that you verify the size of the document and confirm that the size of the failing document is exceptionally large before you increase the timeout value. Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations. APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help Now
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
