Indexing Service does not start when no index locations are configured
book
Article ID: 100042683
calendar_today
Updated On:
Description
Error Message
Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Event ID: 41306
Task Category: Index Admin Service
Level: Error
Description:
There are no index locations. No indexing can take place until an index location has been created.
V-437-41306
Cause
The Indexing service has not been configured with any locations, closed or open, the Indexing service will immediately stop.
For the Enterprise Vault 14.2.0 and greater releases, the new ElasticSearch (ES) indexing engine is used instead of the 64-bit indexing engine. As a result, all existing index locations are closed and a new index location must be configured for the ES indexes.
Resolution
Add at least one Index location on the properties of the Indexing service within the Vault Administration Console (VAC). Once added, the location(s) can be closed.
To add a new index location:
- Log onto the Enterprise Vault server as the Vault Service Account.
- Open File Explorer.
- Navigate to the drive to contain the ES indexes.
- Create a new folder on that drive to contain the ES indexes. Example: E:\Indexes\Elastic.
- Open the VAC.
- Navigate to the EV server.
- Expand the Server and select the Services option.
- Click on the Enterprise Vault Indexing Service to select that service.
- Right click on the service to see the list of available options.
- Select the Properties option to open the EV Index Service properties window.
- Select the Locations tab.
- Click the Browse button.
- Browse to the drive and folder to contain the ES indexes.
- Click the OK button to save the designation for the new ES index location.
- Click the OK button to close the EV Index Services properties window.
- Click the Start icon to start the Enterprise Vault Indexing Service.
Issue/Introduction
The Indexing Service fails to start when no index locations are configured.
Was this article helpful?
thumb_up
Yes
thumb_down
No