A corrupt xml metadata file for an index volume can causes search, ingestion and rebuild to fail

book

Article ID: 100046523

calendar_today

Updated On:

Description

Error Message

The following error is logged when the xml file metadata of an Index volume is corrupted:

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      41352
Task Category: Index Volumes Processor
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EV-EXCH.EV.local
Description:
The processing of the Index Volume has stopped following errors.

Archive name: Smith, John
Task:
Index Volume ID:1D91712B2154E34448BA031186E2A0A671810000evserver_1004
Reason:
Error Type: NonCritical
Description: Indexing engine unreachable. Inner exception: Error in deserializing body of reply message for operation 'SearchIndex VolumeStatus'.

The following error can be seen if a rebuild was attempted on the Index Volume

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      41352
Task Category: Index Volumes Processor
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EV-EXCH.EV.local
Description:
The processing of the Delete index volume task has stopped following errors.

Archive name: Smith, John
Task:
Delete index volume task ID: 1D91712B2154E34448BA031186E2A0A671810000evserver_1004
Reason:
Error Type: NonCritical
Description: Indexing engine unreachable. Inner exception: Error in deserializing body of reply message for operation 'SearchIndex VolumeStatus'.

 

Cause

The corruption of the index metadata can be caused by multiple reasons.

The most common causes of corruption affecting the Indexing Engine and Index Metadata locations is having an Anti-virus solution without the recommended exclusions.
 

 

Resolution

To prevent this issue from occurring in the first place, please review the following article to ensure all Antivirus Exclusions are in place: 10001772

Please contact Veritas Support if you are experiencing this issue

Veritas has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article.

There are currently no plans to address this issue by way of a cumulative hotfix or service pack in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time, but is not scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see http://www.Veritas.com.

 

Issue/Introduction

Certain Index Volumes metadata xml file can encounter some form of corruption resulting in searches and indexing to fail for the affected Index. Rebuilding of the index volume will also fail as EV fails to read the indexmetada for this particular index volume before performing the last step which is to remove the old\failed index being rebuilt The metadata xml fle is located in the Index MetaData Location under the associated index volume name in the \EVIndexing\data\indexmetadata\search-collections\xxx\IndexVolumeReference.xml

Additional Information

JIRA: CFT-1826