Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Event ID: 41315
Task Category: Index Query Server
Level: Warning
Computer: Ev1
Description:
A search failed with error "The indexing engine could not load the index".
Archive: Journal1
Archive ID: 11D297CA71BF1614A9C39C152E86776941110000EV01
Index volume ID: 22
User: EvLab\svc-evault
Maximum results: 50000
Timeout (seconds): 3600
Sort order: snum
V-437-41315
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Event ID: 41315
Task Category: Index Query Server
Level: Warning
Computer: EV1
Description:
A search failed with error "The indexing engine is unable to perform the search due to lack of resources.".
Archive: Journal1
Archive ID: 11D297CA71BF1614A9C39C152E86776941110000EV01
Index volume ID: 92
User: EvLab\svc-evault
Maximum results: 50000
Timeout (seconds): 3600
Sort order: snum
V-437-41315
This occurs when any combination of the following conditions are met:
Identify which resource(s) are lacking by using Performance Monitor or a simple overview of Task Manager.
In most cases, this issue is corrected by:
1. Additional RAM
2. Configuring the Pagefile to 1.5 to 2 times physical memory (in multiples of 1024MB, to a maximum of 48GB pagefile), and stored on a local (fast) non-system drive.
Note 1: This is usually a more prominent problem on EV servers with 16gb RAM or less, or on servers with significant active accelerator searches.
Note 2: "Automatically manage paging file size for all drives" should be avoided for optimal EV server performance.
Applies To
EV 10.x and above, using Windows Server operating systems through 2019.