Error Message

Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Event ID: 41352
Task Category: Index Volumes Processor
Level: Error
Description:
The processing of the Index Volume has stopped following errors.

Archive name: Archive Name
Task:
Index Volume ID: 1E13E909A5BDD9649B68C75462C443D3F1110000server_103
Reason:
Error Type: NonCritical

Description: Indexing engine unreachable. Inner exception: The remote server returned an unexpected response: (413) Request Entity Too Large.

v-437-41352

A Dtrace of EVIndexVolumesProcessor shows the following:

(EVIndexVolumesProcessor)        EV-L    {EVAdditionDataReader} Traversing EV item. SavesetID=[201912166534562~201912162214200000~Z~E130418C89B259CD3EEB9621E36756B1], ItemSequenceNum=[98421]

[...]

(EVIndexVolumesProcessor)        EV-L    {AdditionsIndexer} Time to flush! Estimated size of current batch=0KB. Maximum batch size=10000KB. Estimated size of next item=62849KB

(EVIndexVolumesProcessor)    <25008>    EV-M    {VelocityIndex} DoFlush is called by Indexer (1) Thread for 14F50DC8F2DEAD448A26087121EA022431110000server_103
(EVIndexVolumesProcessor)    <25008>    EV-L    {VelocityIndex} Enqueuing a batch of 1 actions to Velocity. IndexVolumeID=[14F50DC8F2DEAD448A26087121EA022431110000server_103]
(EVIndexVolumesProcessor)    <25008>    EV-L    {IndexingWCFProxy`1} Calling CollectionBrokerEnqueueXml

(EVIndexVolumesProcessor)    <25008>    EV-L    {IndexingWCFProxy`1} TraceTimer [8011ms] Called CollectionBrokerEnqueueXml
(EVIndexVolumesProcessor)    <25008>    EV-H    {IndexingWCFProxy`1} Exception: The remote server returned an unexpected response: (413) Request Entity Too Large.

IIS logs show a 413.2 status:

2022-07-08 22:43:37 ::1 POST /EVIndexing/Velocity.exe v.app=api-soap& 443 - ::1 - - 413 2 0 15

Workaround

Generally it is not desirable to send very large amounts of data to the index if it is not relevant to any potential search. Some file types that are converted into large streams of XML or HTML can be excluded from indexing.  Try to identify the item that leads to the issue from a Dtrace and retrieve it from storage to see what kind of content may be at issue. Including StorageCrawler component in the Dtrace may help show the type of attachments (file extensions.) Refer to the trace snippets above to help determine which items may be leading to the issue. 

Exclude the file type from conversion under Site settings -> Advanced -> Content conversion -> File types excluded from conversion.

Note: Besides applying to conversion when items are first archived, the setting applies when indexing items.  Content from any file with the extensions listed will not be sent to the index, even if they were previously converted. 

Alternate Workaround

If it is not possible or desirable to exclude large content from the index, an alternative is to manually manage the web.config file request limit settings  for the /EVIndexing virtual directory in IIS.

In 12.4+ the file is located in the [EV installation directory]\EVIndexing\www\cgi-bin\web.config
In versions prior to 12.4, it is located in the [EV installation directory]\EVIndexing\www\asp\web.config

Important: Make a backup of the web.config file before attempting any changes.

There are two settings in the web.config file that change in tandem based on the EV server advanced setting IndexingMaxRequestLength

Setting show in Vault Admin Console, default value is 76800 kilobytes

The settings in web.config are:

•  maxAllowedContentLength (in bytes), under system.webServer/security/requestFiltering
•  maxRequestLength (in kilobytes), under system.web/httpRuntime.

Increase the values to be around 25% larger than the EV server setting.   So for the default setting of 76800 kilobytes, this becomes 76800 x 1.25 or 96000 kilobytes for maxRequestLength and 96000 x 1024 or 98304000 bytes for maxAllowedContentLength.

These changes to the /EVIndexing web.config will get overwritten upon startup of the indexing service.  To prevent this stop indexing before saving the changes and edit the file [EV installation directory]\EVindexAdminService.exe.config.  In the section: 

Set the following:

        True
      

Some items or attachment types that are converted into large streams of HTML or XML can expose an issue where Enterprise Vault doesn't correctly enforce the server indexing setting MaxRequestLength. 

This issue has been addressed in the following releases:

Enterprise Vault 12.5.1
https://www.veritas.com/content/support/en_US/downloads/update.UPD372650