The index volume has X number of failed items.
Checking the ItemAdditionStatusLog table in the vault store database shows that the failed items have an error code of 101 and the raw error text is "Estimated item size of (filesize)KB exceeds limit of (Indexing Max Request Length)".
This error is caused when the overall size of an item being archived is larger than the "Indexing Max Request Length" size configured for the Enterprise Vault Server. In the case of an email, the overall size of the email being archived is the result of the size of the message added to the size of the header information.
A common reason for this error is when a large email message is archived that also contains a very large Distribution List (DL), a combination of DLs or embedded DLs (DLs within DLs). When the email is archived, and DL expansion is enabled, all the recipients of the email are added to the header information for the archived email. If the email message and recipient information exceed the "Indexing Max Request Length" size, the item will fail to be indexed.
For example, 140,000 names/recipients equates to roughly 93MB of added size to an email. Also, If a recipient is in more than 1 DL, they are included each time their name appears in a DL.
In order to process items that have failed because they have exceeded the Indexing Max Request Length limit, perform the following steps:
1. From the Enterprise Vault (EV) Console, right click on the EV Server that runs the indexing service and select Properties.
2. Select the Advanced Tab.
3. Select Indexing from the List Settings From dropdown box.
4. Locate the "Indexing Max Request Length" setting and change the value to a number above the size of the largest failed item. Default is 76800KB.
5. Restart the EV Admin service and IIS.
6. Rebuild the index volume or retry the failed items.
Applies To
Enterprise Vault 10 and above.