A Dtrace of the EVIndexAdminService shows the following information:
(EVIndexAdminService) <5072> EV~E |Event ID: 41370 An error occured while synchronizing Indexing Engine metadata for Index volumes.|Error Details:|There was no endpoint listening at http://localhost/evindexing/Index Engine.aspx?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.
(EVIndexAdminService) <5072> EV-L {SERVICEBASEEX.EN_US} Releasing IDirectoryPublicV82 interface.
(EVIndexAdminService) <5072> EV-L {SERVICEBASEEX.EN_US} Releasing IDirectoryAdminV82 interface.
(EVIndexAdminService) <5072> EV-L {INDEXADMINSERVICE.EN_US} Starting indexing engine
(EVIndexAdminService) <5072> EV-L {INDEXINGENGINEMONITOR.EN_US} Starting Collection Broker...
(EVIndexAdminService) <5072> EV-L {IndexingWCFProxy`1} Calling CollectionBrokerStart
(EVIndexAdminService) <5072> EV-L {IndexingWCFProxy`1} [8ms] Called CollectionBrokerStart
(EVIndexAdminService) <5072> EV-L {IndexingWCFProxy`1} [4ms] Called CollectionBrokerStart
(EVIndexAdminService) <5072> EV-H {VELOCITYPROXY.EN_US} Exception: There was no endpoint listening at http://localhost/evindexing/velocity.aspx?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.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.CollectionBrokerStart(CollectionBrokerStartRequest request)| at lambda_method(ExecutionScope , VelocityPort )| at KVS.EnterpriseVault.Runtime.WCF.WCFProxy`1.Invoke[TResult](Expression`1 method)| 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.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
(EVIndexAdminService) <5072> EV~E |Event ID: 41335 An error occured while trying to start indexing engine.|Further error details include: 'There was no endpoint listening at http://localhost/evindexing/Index Engine.aspx?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.'.
(EVIndexAdminService) <5072> EV-H {INDEXADMINSERVICE.EN_US} The Indexing Service could not complete all the required startup routine: Starting Index Engine failed.. Service will be stopped.
(EVIndexAdminService) <5072> EV~E |Event ID: 41312 The Indexing Service could not complete all the required startup routines: Starting Index Engine failed. Service will be stopped.
V-437-41335
V-437-41312
V-437-41370
Open IIS Manager
To check that it's working, browse to this URL.
https://localhost/evindexing/velocity.aspx
Note: If text displays saying: "Please specify an application" the issue has been resolved.