Event IDs 41312 and 41293 are logged during Enterprise Vault Indexing service startup

book

Article ID: 100060457

calendar_today

Updated On:

Description

Error Message

Event ID: 41312

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

Event ID: 41293

An unexpected error has occurred.
Error Summary: Indexing Service start up error
Error Details: Fatal error in Indexing Service child process EV Indexing Engine Elasticsearch. Further error information:
Error while waiting to achieve the requested state Running.

dtrace of the EVIndexingEngineElasticsearch contains the following lines:
[20268]    (EVIndexingEngineElasticsearch)        EV-H    {ElasticsearchLogger} Exception in thread "main" org.elasticsearch.bootstrap.BootstrapException: java.nio.file.FileAlreadyExistsException: C:\Program Files (x86)\Enterprise Vault\Services\Elasticsearch\config\\elasticsearch.keystore.tmp
[20268]    (EVIndexingEngineElasticsearch)        EV-H    {ElasticsearchLogger} Likely root cause: java.nio.file.FileAlreadyExistsException: C:\Program Files (x86)\Enterprise Vault\Services\Elasticsearch\config\\elasticsearch.keystore.tmp

Cause

In rare circumstances, the temporary Elastic Search keystore file elasticsearch.keystore.tmp is present under the folder <EVInstall Directory>\Enterprise Vault\Services\Elasticsearch\config\EVSERVER\ and might cause the aforementioned issue.

Resolution

It is possible to rename the elasticsearch.keystore.tmp to elasticsearch.keystore and start the Enterprise Vault indexing service afterwards.

 

Issue/Introduction

Enterprise Vault Indexing service cannot be started properly