Index Volumes are randomly being marked as failed due to a 'Users_Exists' Exception

Index Volumes are randomly being marked as failed due to a 'Users_Exists' Exception

Article: 100032191
Last Published: 2016-03-30
Ratings: 0 0
Product(s): Enterprise Vault

Problem

Index Volumes are randomly marked as failed. Analysis of the indexes showed that there is no corruption and a synchronisation is needed for the Index to switch back to a healthy state
 

Error Message

Event ID 41329 will be generated when an Index is marked as failed. However using the Error on its own is not sufficient. A corresponding backtrace\dtrace is needed to confirm whether a USERS_EXISTS Exception also occurred.

Event 41329
Type :        Error
Date :        02/12/2015
Time :        08:52:22
Event :        41329
Source :        Enterprise Vault
Category :    Index Volumes Processor
User :        N/A
Computer :    EV Server
Description:
Index volume is marked as failed.

Archive Name: User 1
Index Volume ID: 123426140E189A547A0DE99E163R561C1110000EVArchive
Reason: IndexingEngineError
Error Type: CriticalError

Description: Indexing engine exception
 

Dtrace\Backtrace snippet of EVIndexVolumesProcessor

221299    09:46:56.551     [3408]    (EVIndexVolumesProcessor)    <Agent Thread for 123426140E189A547A0DE99E163R561C1110000EVArchive:7512>    EV-L    {IndexingWCFProxy`1} SOAP FAULT: detail xml = <exception time="47" date="1430293616" id=" USERS_EXISTS" function="vivisimo_load" fid="50" process="*" name="users-exists-error" stack-trace="//scope/function[@name='api-authenticate']/scope/scope/function[@name='util-authenticate-user']///function[@name='authenticate-user-without-password']/scope/exception[@id='USERS_EXISTS']" xmlns="urn:/velocity/objects">Failed to create the user <string>apiuser</string> because a user with that name already exists.  </exception>
 

Cause

In some circumstances a ‘Sharing Violation’ is encountered when trying to update the Users.xml file for Velocity resulting  in the exception 'USERS_EXISTS' being returned to Enterprise Vault (EV) which is then treated as a critical
failure.

Solution

This issue has been addressed in the following release:
 
Enterprise Vault 12.1
 
The following link contains information about Enterprise Vault 12.1
https://www.veritas.com/docs/000107766
 
Note: For information on how to obtain Enterprise Vault 12 see: How to obtain the license key and installation download for Veritas products
 

References

Etrack : 3857621

Was this content helpful?