Error Message

Log Name:              Symantec Enterprise Vault
Source:                   Enterprise Vault 
Event ID:                 40966
Task Category:       None
Level:                      Error
Keywords:               Classic
Description:

This issue can occur upon startup from a server restart (boot up) when Discovery Accelerator (DA) is installed on a server as that has Enterprise Vault installed and configured to provide archiving, indexing and / or storage services. DA uses a service named Enterprise Vault Accelerator Manager Service (EVAMS) to provide for and control the DA functionality.  During the server boot up processing, EVAMS may try to start prior to the services used by Enterprise Vault to provide connectivity between DA and EV.  Those services are 'Enterprise Vault Admin' and the 'Enterprise Vault Directory'.    Those two services have dependencies and preliminary checks at startup. Since DA is an add-on product to EV, it relies on the Enterprise Vault Directory service for communications to provide information to DA such as a listing of all Vault Stores and Archives within each Vault Store.

A temporary connectivity issue is caused between the EV and DA services when EVAMS tries to contact the Enterprise Vault Directory that has not  yet started, resulting in the issue occurring and the Event ID error being thrown.

No functionality loss is traced and this error can be safely be ignored in above mentioned scenario once the Enterprise Vault Directory service has started.

A workaround to prevent this issue from occurring is to configure the EVAMS to the 'Startup type:' value of "Automatic (Delayed Start)" so that it waits until after all the EV services are started before it starts.

1. Log onto the EV/DA server with an account that has local Administrator privileges, such as the Vault Service Account (VSA).
2. Open the Services application.
3. Locate and select the Enterprise Vault Accelerator Manager Service entry.
4. Stop this service if it is running.
5. Right click on the service once it has stopped.
6. Select the Properties option.
7. Click the drop down arrow for the Startup type: option.
8. Select the Automatic (Delayed Start) setting.
9. Click the OK button to save the changes and close the service properties page.
10. Start the service.

Note: For better overall server performance, the recommendation is to install DA wherever possible on its own server that has only the EV binaries installed.   DA does not require direct access to any EV service as it can use indirect access through RPC and DCOM connectivity.  Having DA on a separate server provides for more local resources to be available on the EV server during DA functions such as searches, reviews and exports.

When Discovery Accelerator (DA) is installed on an Enterprise Vault (EV) server that is providing archiving, indexing and / or storage services, the Enterprise Vault Accelerator Manager Service (EVAMS) used to run DA fails to start and the event shown in the Error Message section is thrown into the Veritas Enterprise Vault Event Log on the server.