Description

In extremely rare circumstances, some data-files central to the 64-bit Indexing Engine can become corrupted, resulting in the engine becoming prone to crashes/failures.

This can be rectified by re-installing the indexing engine using the Indexing Redistributable supplied with the Enterprise Vault Install Media.
 

1. Stop the Enterprise Vault Indexing Service on the affected Enterprise Vault Server.
    
2. Stop the World Wide Web Publishing Service on the affected Enterprise Vault Server.
    
3. Launch IIS Manager and delete the EVIndexing virtual Directory.
    

Delete by navigating down to the EVIndexing directory on the left pane: Server > Sites > Default Web Site > EVIndexing.

4. Following the deletion of the Indexing virtual directory, delete the EVIndexingPool application pool for versions prior to EV 12.4.

5. Using Windows explorer, navigate to the Enterprise Vault installation Directory and delete or rename the EVIndexing folder.
   
   
   Note: If the IndexMetaData folder (which is usually found under the EVIndexing folder) may be held in a different location and will need to be deleted separately in addition to deleting or renaming the EVIndexing folder in Step 5. To locate this folder, run the below SQL query:

USE EnterpriseVaultDirectory
SELECT CE.ComputerName, ISE.MetaDataLocation
FROM ComputerEntry CE, IndexingServiceEntry ISE
WHERE CE.ComputerEntryID = ISE.ComputerEntryID
 

6. Reinstall the Indexing Engine
   • For EV 12.x and 14.x: Run the Veritas Enterprise Vault Indexing Redistributable.msi from Program Files (x86)\Enterprise Vault\Installation.
   • For EV 14.2 and later, install the following components to re-install Elastic Search indexing engine:
     • Veritas Enterprise Vault Indexing Redistributable.msi
     • Veritas Enterprise VaultJDK Redistributable.msi
     • Veritas EnterpriseVault Elasticsearch IndexingRedistributable.msi
7. If Enterprise Vault is on a Release Update version, for example "14.5.2", reinstall the Release Update.
   • Reboot once the update has successfully completed.
8. Start the World Wide Web Publishing Service and the Enterprise Vault Indexing Service

Note:
It may take a while for the Indexing service to become fully operational following the re-installation of the Indexing Engine, as a full Synchronization between Enterprise Vault and the Indexing Engine will be automatically triggered. The commencement and completion of this process will be marked by the following entries in the Enterprise Vault Event Log:

Event ID: 41372
Indexing Service has started the synchronization of index volume metadata between the indexing engine repository and the Directory database.

Event ID: 41377
Indexing Service has completed the synchronization of index volume metadata between the indexing engine repository and the Directory database.
Total index volume(s) whose metadata was created: x
Total index volume(s) whose location was updated: y

IMPORTANT: Do not edit this content in Information Manager