Error Message

Enterprise Vault Event Log entry on the affected EV indexing server:

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault 
Event ID:      41293
Task Category: Index Admin Service 
Level:         Error
Keywords:      Classic
Description:
An unexpected error has occurred.

Error Summary: Indexing Service start up error 
Error Details: Object reference not set to an instance of an object. 
Reference: ServiceBaseEx::Run 
Stack Trace:    at Symantec.EnterpriseVault.Indexing.Admin.IndexingEngineMonitor.ConfigureApplicationHost(ServerManager IISManager)
   at Symantec.EnterpriseVault.Indexing.Admin.IndexingEngineMonitor.ConfigureWebSite()
   at Symantec.EnterpriseVault.Indexing.Admin.IndexAdminService.OnPerformStartup(Boolean HotRestart)
   at KVS.EnterpriseVault.Common.ServiceBaseEx.Run()

V-437-41293
 

Below is seen in a Dtrace log of the EVindexAdminService process:

(EVIndexAdminService)    <21336>    EV-H    {VelocityProxy..cctor} Exception: Could not find endpoint element with name 'EndpointConfig' and contract 'VelocitySrvRef.VelocityPort' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this name could be found in the client element. Info:Failed to initialise the WCF proxy for the 64-bit engine. Diag: Type:System.InvalidOperationException ST:   at System.ServiceModel.Description.ConfigLoader.LoadChannelBehaviors(ServiceEndpoint serviceEndpoint, String configurationName)|   at System.ServiceModel.ChannelFactory.ApplyConfiguration(String configurationName, Configuration configuration)|   at System.ServiceModel.ChannelFactory.InitializeEndpoint(String configurationName, EndpointAddress address)|   at System.ServiceModel.ChannelFactory`1..ctor(String endpointConfigurationName, EndpointAddress remoteAddress)|   at KVS.EnterpriseVault.Runtime.WCF.WCFProxy`1..ctor(String endpointConfigurationName)|   at Symantec.EnterpriseVault.Indexing.Common.IndexingWCFProxy`1..ctor(String endpointConfigurationName)|   at Symantec.EnterpriseVault.Indexing.IndexingEngine.VelocityProxy..cctor() Inner:None

This issue is caused due to missing configuration files.

Repair the installed version of EV binaries:

1. Stop all EV services, including the Enterprise Vault SMTP Service, if it has been installed and is running.

2. Run the setup.exe file from the Enterprise Vault installation media using the same version currently in use on the EV server.  The default path for the file on the install media is Veritas Enterprise Vault\Server\x64\setup (x64).exe. 

Note: There should be no need to uninstall EV.  If the decision is made to completely uninstall and re-install an EV version that has a Product Update installed, the installation process must have the base version installed first and then the Product Update may be installed. For example, when working with EV 14.1.3, install 14.1.0 and then 14.1.3.

3. Select the Enterprise Vault Services option. Proceed with the wizard.

NOTE: From EV 12.4 onward, the user will be presented with the options of Modify, Repair, or Remove.  Choose the Repair option and proceed with the wizard

4. Start all EV services after the completion of the installation.  Note: Some instances of this action may require a server restart.  Proceed with the restart as the DLL registration will continue afterward.

Note: After Step No. 4, DO NOT proceed with running the Enterprise Vault Configuration Wizard.