Forum Discussion

millerii's avatar
millerii
Level 2
2 months ago
Solved

Enterprise Vault Indexing Service won't start

Hello everyone. I created a Windows cluster with two EV nodes. When activating the role on one node, the EV works fine. When activating the EV Indexing Service role on the other node, all services start fine, except for the Enterprise Vault Indexing Service. There are two errors in the logs.

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

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. Reference: ServiceBaseEx::Run Stack Trace: at KVS.EnterpriseVault.ProcessManagement.ChildProcessManager.StartChildProcesses() at Symantec.EnterpriseVault.Indexing.Admin.StateManager.StartChildProcesses() at Symantec.EnterpriseVault.Indexing.Admin.IndexAdminService.OnPerformStartup(Boolean HotRestart) at KVS.EnterpriseVault.Common.ServiceBaseEx.Run()

EV version - 15.2.1

Help me fix it

  • millerii's avatar
    millerii
    2 months ago

    Sorry, I fixed the problem, and it was due to the difference in EV versions. The first one was 15.2.1, the second one was 15.2. I updated to 15.2.1 and it worked.

3 Replies

  • millerii's avatar
    millerii
    Level 2
    2 months ago

    Sorry, I fixed the problem, and it was due to the difference in EV versions. The first one was 15.2.1, the second one was 15.2. I updated to 15.2.1 and it worked.

    • millerii's avatar
      millerii
      Level 2
      2 months ago

      Thanks, it works, but as soon as I reactivate the role on this cluster node, the situation repeats itself. The Enterprise Vault Indexing Service won't start until I rename the nodes\0\_state folder. If I activate the role on the first node, everything works fine.