Searches fail with Index Search failed: %1 Index: %3 Internal reference: %2 [0xc0041c0e] error

book

Article ID: 100029406

calendar_today

Updated On:

Description

Error Message

From the Veritas Enterprise Vault Event Log on the Accelerator server:

Event Type: Error
Event ID: 42077
Description:
Error:
Searching Vault Thread - worker thread for index server: 13 (4)
Vault ID:
Number of tries: 5
Cause:Index Search failed: Error:
Cause:Index Search failed: %1    Index: %3   Internal reference: %2   [0xc0041c0e]
Description:
Error processing Vault to Search off the queue.
V-437-42077

 

Cause

This error can be generated when performing a search within Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA). The 0xc0041c0e error indicates low resources and will generate an Event ID 42077 error in the Symantec or Veritas Enterprise Vault Event log on the CA or DA server.

The causes of this error are, but are not limited to:

  1. Lack of memory resources.
    1. For EV servers that are hosting 32-bit index volumes that have this error, server's paged memory configuration may not be set to release memory fast enough for the search to succeed.
    2. For EV servers that are hosting 32-bit and / or 64-bit index volumes, the index volume may be fragmented to the point where insufficient space is available to contain the index volume contents, search criteria and search hits.
  2. Slow access to the drive(s) and /or folder(s) containing the index files.

 

Resolution

For a lack of memory resources:

1. On EV Indexing Servers hosting 32-bit index volumes where this error occurs, make the following registry changes on the Compliance Accelerator or Discovery Accelerator server and the Enterprise Vault Indexing server when running on 32-bit versions of the Microsoft Windows Server operating systems.  

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

1. Start Registry Editor (Regedt32.exe).

2. Locate and then click the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management

3. On the Edit menu, click Add Value, and then add the following registry value:

 
Value name: PoolUsageMaximum
 
Data type: REG_DWORD
 
Radix: Decimal
 
Value data: 50
 
Setting the value at 50 informs the Memory Manager to start the trimming process at 50 percent of PagedPoolMax rather than the default setting of 80 percent. If a threshold of 50 percent is not enough to handle spikes in activity, reduce this setting to 40 percent or 35 percent.
 
 
Value name: PagedPoolSize
 
Data type: REG_DWORD
 
Radix: Hex
 
Value data: 0xFFFFFFFF
 
 
Setting PagedPoolSize to 0xFFFFFFFF allocates the maximum paged pool in lieu of other resources to the computer.
 

4. Quit Registry Editor.

5. Restart the server for the changes to take effect.

Reference Microsoft Article: 312362 


2. On EV servers hosting 32-bit and / or 64-bit index volumes having this error, defragment the affected index volume(s) by
1. For 32-bit index volumes, create an empty file named compact.task in the index volume folder and run an Index Sync operation.
2. For 64-bit index volumes, run the Index Sync operation without any additional actions.
 

For slow access to the drive(s) and / or folder(s) containing the index volumes, either

  1. Move the index volume(s) to faster media, or
  2. Adjust the search criteria to decrease its complexity and / or search date range.

Issue/Introduction

Searches fail with Index Search failed: %1 Index: %3 Internal reference: %2 [0xc0041c0e] error

Additional Information

ETrack: 42077 UMI: V-437-42077
Powered by Wolken Software