Error Message

Log Name:         Veritas Enterprise Vault
Source:              Enterprise Vault
Event ID:            41293
Task Category:   Index Admin Service
Level:                 Error
Description:
An unexpected error has occurred.
Error Summary: Indexing Service start up error
Error Details: There was no endpoint listening at http://localhost/evindexing/velocity.exe?v.app=api-soap& that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote server returned an error: (404) Not Found.
Reference: ServiceBaseEx::Run
Stack Trace:
Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Snippets from the d-trace of  'EVIndexAdminService' process during the Indexing service start up

(EVIndexAdminService)       <12180>               EV-H       {IndexingWCFProxy`1} Exception: There was no endpoint listening at http://localhost/evindexing/velocity.exe?v.app=api-soap& that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Info: Diag: Type:System.ServiceModel.EndpointNotFoundException ST:|Server stack trace: |   at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)|   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)|   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)|   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)|   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)|   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)|   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)|Exception rethrown at [0]: |   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)|   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)|   at Symantec.EnterpriseVault.Indexing.IndexingEngineService.VelocitySrvRef.VelocityPort.SearchServiceGet(SearchServiceGetRequest request)|   at KVS.EnterpriseVault.Runtime.WCF.WCFProxy`1.Invoke[TResult](Expression`1 method, String server)|   at Symantec.EnterpriseVault.Indexing.Common.IndexingWCFProxy`1.Invoke[TResult](Expression`1 method) Inner:System.Net.WebException: The remote server returned an error: (404) Not Found.|   at System.Net.HttpWebRequest.GetResponse()|   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

Execution of .'exe' files blocked under request filtering features section of 'EVIndexing' virtual directory. This can cause the 'velocity.exe' being blocked from execution and thus halting the indexing service startup.

 Please perform below steps to remove '.exe' from the blocked list.

                1) Open Internet Information Services (IIS).

                2) Navigate to 'EVIndexing' Virtual Directory under the Default Web Site.

                3) Navigate to Request Filtering in the features view.

                4) Click on File Name Extensions tab.

                5) Select '.exe' extension rule which is set to False.

                6) Right Click and select 'Remove'.

                7) Restart IIS service.

                8) Start Indexing service and it should be started and fully operational.