Select the product you need help with
Large Text Files Are Not Fully IndexedArticle ID: 318747 - View products that this article applies to. This article was previously published under Q318747 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
On This PageSYMPTOMS
If you crawl documents on a computer that is running SharePoint Portal Server, large text files may not be fully indexed. The Microsoft Search service may log an error message in the Microsoft Windows Event Viewer Application event log that is similar to:
Event Type: Warning Event Source: Microsoft Search Event Category: Gatherer Event ID: 3035 Date: 1/1/2002 Time: 12:00:00 PM User: N/A Computer: COMPUTERNAME Description: One or more warnings or errors were logged to file <C:\Program Files\SharePoint Portal Server\Data\FTData\SharePointPortalServer\GatherLogs\WORKSPACE\WORKSPACE.1.gthr>. If you are interested in these messages, please, look at the file using the gatherer log query object (gthrlog.vbs, log viewer web page). Context: SharePointPortalServer Application, WORKSPACE Catalog
Time: 1/1/2002 12:00:00 PM Type: Document Added Message: Error fetching URL, (8004173e - The document was too large to filter in its entirety. Portions of the document were not emitted.) URL: file://./backofficestorage/localhost/sharepoint portal server/workspaces/HOME/Do... Time: 1/1/2002 12:00:00 PM Type: Document Added Message: Error fetching URL, (8004173e - The document was too large to filter in its entirety. Portions of the document were not emitted.) URL: \\.\backofficestorage\localhost\sharepoint portal server\workspaces\HOME\documen...
http://computer_name/workspace/portal/resources/updatelog.asp?Workspace=workspace CAUSE
This issue can occur if some text files are too large for the server to index by using the default SharePoint Portal Server settings, which are configured for performance reasons.
RESOLUTIONIndexing Large Text FilesIf you are indexing large text files (.txt), to resolve this issue, change the MaxTextFilterBytes registry value.WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To change the MaxTextFilterBytes registry value:
Indexing Other Types of Large DocumentsYou can fully index most other document types by changing the MaxDownloadSize and MaxGrowFactor registry values:
NOTE: After you make these changes, restart the Microsoft Search service. If you want your documents to be re-indexed immediately, do a full update on the content source that contains the large files. MORE INFORMATIONFor additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
287231
The following registry keys and values are used in this article:
(http://support.microsoft.com/kb/287231/EN-US/
)
Search Only Indexes 16 Megabytes of a Document
PropertiesArticle ID: 318747 - Last Review: February 28, 2007 - Revision: 2.1
|


Back to the top








