Event ID 41311 can be logged multiple times for certain Index Volumes wrongly identified as needing an update

book

Article ID: 100051519

calendar_today

Updated On:

Description

Error Message

Type : Information
Date : 13/09/2021
Time : 08:19:48
Event : 41311
Source : Enterprise Vault
Category : Index Admin Service
User : N/A
Computer : EVServer1.EV.local
Description:
The following informational message occurred in the core indexing engine:

Identified the following index volume :1029787F80C25A1234B334ADB4BF6D7AB_6113 require an update. Proceeding to update it.

 

 

Cause

EV 12.4 introduced an updated version of the Indexing engine. An EV upgrade processes each Index to also update its internal schema to match the Indexing engine's schema. This schema update is performed during the first startup of the Indexing service after the EV 12.4 upgrade. An informational event 41467 is logged advising the successful schema update of all Indexes, however, the update was missing a column.

In EV 12.5.1 a fix was introduced to identify those index volumes based on an error logged in the Indexing Core Engine "COLLECTION_SERVICE_SERVICE_TERMINATED", however this error can occur for other reasons resulting in index volumes already updated to be wrongly processed again

 

Resolution

This issue has been resolved in the following release:

Enterprise Vault 14.1.2 - Maintenance Release which is available for download from the following location after logging in:

https://www.veritas.com/content/support/en_US/downloads/update.UPD388400

 

 

Issue/Introduction

When upgrading to 12.5.1 onwards, an Index volume can be wrongly identified as needing an update to its Index Schema. As a result, Event Id 41311 may be seen multiple times for the same Index Volume.

Additional Information

JIRA: CFT-4043 SW Download: UPD388400 JIRA: CFT-4805