Overview:
The issue is generated when an Index Server Worker Thread cannot access the Index in its allotted time frame.  The timeout of the Worker Thread is due to resource issues, Index size, or search criteria complexity.  


Solution:
In the Compliance Accelerator (CA) and Discovery Accelerator (DA) Program:
 

 

1. Open the CA/DA client

2. Modify Configuration | Settings | Search (Hidden Setting (To show hidden settings hit Ctrl + Click on Configuration Settings in the upper left hand corner))
 

'Maximum Number of consecutive search on the same index'
Value: 1

3. Restart the Customer background Task or the Enterprise Vault Accelerator Manager Service and conduct the search again.


Other factors can influence Enterprise Vault (EV) resources:
 

- Increasing RAM on the Enterprise Vault (EV) Indexing servers.  In 32-bit environments, EV can address up to 4GB of memory.  Having additional memory available for the Application Pool increases the efficiency of all worker threads.
 
- Disabling Anti Virus scanning of the Vault Service Account (VSA) Temporary folder increases the efficiency during the extraction and examination of the index contents

- Increasing VSA Temporary folder available disk drive space has an effect on the ability and quantity of indexes that can be extracted and examined.
 

In order to modify the VSA Temporary folder:
 

1. Log on the server using the VSA account
2. Open the System Properties of My Computer
3. Open the Advanced tab and then Environmental Variables
4. Edit the TEMP and TMP file location


- Inserting the Microsoft Memory Management settings in the registry to allow the Microsoft memory manager to more efficiently allocate Application Pool memory
Refer to the reference document listed below

- Reducing Index size (AVSMaxLoc)
Refer to the reference document listed below

- Changing Index Schema Type to 1. (SchemaType)
Refer to the reference document listed below