Indexing large files - complexities and behaviors


There are some complexities surrounding how the content of large files are indexed in Enterprise Vault. There is no simple answer to this question as whether an item's content is indexed or not is dependent on a number of factors:
  1. Processing of large files is governed by this limit:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KVS\Enterprise Vault\LargeFileSize
  • By default, this is set to 50mb
  • Per item
  • Note: this is not related to Indexing at all – just Storage
  1. Converted content will only be passed on to Indexing if it’s within this limit:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KVS\Enterprise Vault\MemLimitForTextConversionFallback
  • By default, this is set to 30mb
  • Per document/attachment (of converted content)
  • If limit is exceeded only metadata is indexed

      3. Converted content will only be indexed if it’s within this limit:

  • Server advanced setting – “Indexing Max Request Length”
  • By default, set to 75mb

Per document/attachment

  • If limit is exceeded, converted content is discarded and only metadata is indexed

Per item

  • Note: includes all indexable attributes across all attachments (but not any discarded content from previous bullet)
  • If limit is exceeded, item is not indexed at all
In summary and to simplify the caveats, all an item’s content will be indexed if:
  • Each document/attachment’s converted content is <30mb
  • Each item’s converted content plus metadata is <75mb
  • (otherwise you may get some/all metadata or perhaps nothing indexed – depending on the above rules



To identify index volumes containing missing items and to subsequently retrieve items missing from an index, see TECH204599.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)