Accelerator Searches fail with errors when the Enterprise Vault API is installed on the Accelerator Server
Problem
When the Enterprise Vault (EV) API is installed on the Accelerator Server, Accelerator Searches may fail with errors referencing the Enterprise Vault (EV) Index Volumes, Vault Stores, connectivity to EV, or missing files. Examples of these errors are logged in the Enterprise Vault Event Logs on the Accelerator Server are listed below.
Error Message
[Log Name: Symantec Enterprise Vault]
V-437-93
[Log Name: Symantec Enterprise Vault]
V-437-7264
[Log Name: Symantec Enterprise Vault]
V-437-8390
V-437-8392
Cause
This issue is seen when the EV API is installed on the Accelerator Server, instead of the full EV Binary files. The Accelerators rely on EV Indexing to perform Searches and require certain EV files be installed on the Accelerator Server to allow communication with the EV Indexing Server(s). The most common method of accomplishing this is to install the EV Binary files, also known as EV Binaries, on the Accelerator Server.
Solution
Uninstall the EV API and install the EV Binaries. On the Accelerator Server logged in as the Vault Service Account (VSA):
- Stop and Disable the EV Accelerator Manager Service (EVAMS).
- Uninstall the EV API files.
- Install the full EV Binary Files:
--- Run the EV Server installation that matches the version and service pack of EV on the EV Server(s).
--- Follow the prompts to install EV and reboot as prompted.
--- At the "Installation complete. The InstallShield Wizard has successfully installed Enterprise Vault. Click Finish to exit the wizard." screen, uncheck the 'Show configuration information' or 'Show information on configuring installed components' box and click on Finish.
--- Reboot as prompted.
--- If a Cumulative HotFix (CFH) or Release Update (RU) is installed on the EV indexing / storage server(s), install that same release on the Accelerator Server.
--- Reboot the server again as prompted.
- Start the EVAMS.
The Accelerator Searches can now be re-run and should not log these errors.