Problem

The Enterprise Vault Indexing Service fails to start if any of the index snapshot locations configured for taking a snapshot of index data on the Enterprise Vault Index Server is not accessible. Also, a new index snapshot location cannot be configured until the indexing service starts.

Error messages

Following events are displayed to the administrator in the Event Viewer:

• Elasticsearch Indexing Engine logs warning event 41678 for inaccessible snapshot locations:

The index snapshot location '\\server\folder' configured for the Enterprise Vault index server 'server_name' is not accessible. Enterprise Vault Indexing service will not start until the index snapshot location is accessible.  

• Elasticsearch Indexing Engine logs error event 41312:

The Elasticsearch Indexing Engine could not complete all the required startup routines: Failed to start Elasticssearch JVM. Service will be stopped. 

• Index admin service logs error event 41293:

Fatal error in Indexing Service child process EV Indexing Engine Elasticsearch. 

V-437-41678
V-437-41312
V-437-41293

Cause

The Enterprise Vault Indexing Service synchronizes all the index snapshot locations from Enterprise Vault Directory Database to the Elasticsearch configuration file in the path.repo setting. The Elasticsearch JVM fails to perform the startup routines if there are any inaccessible locations registered in the path.repo. Since the Elasticsearch JVM fails to start, the Enterprise Vault Indexing Service does not start.

Solution

• Ensure that all the index snapshot locations are accessible and then restart the Enterprise Vault Indexing Service.
  
  OR
   
• Remove all the inaccessible snapshot locations if no longer required and configure a new snapshot location. 

Removing the inaccesible snaphot location

Note:

• Removing the index snapshot location puts the indexing data at risk since snapshots are not available.
• A new snapshot of index data cannot be taken until a new snapshot location is configured.

Execute the following SQL queries to remove each inaccessible index snapshot location and associated entities from the Enterprise Vault Directory database:

--Get the location identity for index snapshot location which is inaccessible
USE EnterpriseVaultDirectory

DECLARE @LocationIdentity INT 
DECLARE @RepositoryIdentity INT

SELECT @LocationIdentity = LocationIdentity FROM SnapshotLocations
WHERE PATH = N''

--Get the snapshot repository identity using location identity
SELECT @RepositoryIdentity = RepositoryIdentity FROM SnapshotRepositories
WHERE LocationIdentity = @LocationIdentity

--Delete the snapshots associated with the snapshot repository
DELETE FROM snapshots 
WHERE RepositoryIdentity = @RepositoryIdentity

--Delete the snapshot repository
DELETE FROM SnapshotRepositories
WHERE RepositoryIdentity = @RepositoryIdentity

--Delete the snapshot location
DELETE FROM SnapshotLocations
WHERE LocationIdentity = @LocationIdentity

Configuring a new snapshot location

1. Ensure that Enterprise Vault Indexing Service is running.
2. Use Enterprise Vault PowerShell command Set-EVIndexSnapshotLocation. Refer to the Enterprise Vault PowerShell Cmdlets guide for more details on the command.
3. Restart the Enterprise Vault Indexing Service which creates a new snapshot repository.