Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 4101 Source: Ci
The content index filter for file <full file path> generated content data more than <n> times the file's size.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
|English: Request a translation of the event description in plain English.|
As per Microsoft: "This event record indicates that the file listed did not get indexed because it generated too much data relative to the physical size of the file. The file will appear in the unfiltered list. This might be normal, or it might be caused by a problem in the filter being used". See MSW2KDB for additional information about this event.
The file <full file path> did not get indexed because it generated too much data relative to the physical size of the file. The file will appear in the unfiltered list. This may be normal, or it may be caused by a problem in the filter being used. If you verify that the problem is not caused by the filter, you can increase the amount of data Indexing Service allows per document. To do that, see the The Microsoft Platform Software Development Kit for information about setting the MaxFilesizeMultiplier registry setting. See Indexing Service event messages link.
Woodrow Wayne Collins
If the problem is not in the filter being used, then you have to change the MaxFilesizeMultiplier registry setting located in:
MaxFilesizeMultiplier represents maximum amount of data (output) which can be generated from a single file, based on its size. This value is a multiplier. A value of 4 means that a file can generate up to 4 times its size in content index data. See Index Server Registry Parameters link below.
|Private comment: Subscribers only. See example of private comment|
|Links: Indexing Service event messages, Index Server Registry Parameters, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated