Error Message

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault 
Event ID:      41293
Task Category: Index Admin Service 
Level:         Error
Keywords:      Classic
User:          N/A
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.
Unable to connect to the remote server
No connection could be made because the target machine actively refused it 127.0.0.1:80 
Reference: ServiceBaseEx::Run 
Stack Trace: 
Server stack trace: 
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, 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.RepositoryListXml(RepositoryListXmlRequest 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)
   at Symantec.EnterpriseVault.Indexing.IndexingEngine.VelocityProxy.RepositoryListXml()
   at Symantec.EnterpriseVault.Indexing.IndexingEngine.VelocityIndexingEngine.GetIndexVolumeNames(Boolean filterInvalidNames)
   at Symantec.EnterpriseVault.Indexing.Admin.IVMetadataSync.PerformSync(String metadataPath, Boolean isCompleteSync)
   at Symantec.EnterpriseVault.Indexing.Admin.IndexingEngineMonitor.PerformIVMetadataSynchronization(IndexAdminService indexAdminservice)
   at Symantec.EnterpriseVault.Indexing.Admin.IndexAdminService.OnPerformStartup(Boolean HotRestart)
   at KVS.EnterpriseVault.Common.ServiceBaseEx.Run() 

The aforementioned could be caused by erroneous entries in the netsh http show iplisten 

By default no ip addresses should be shown by the command 

netsh http show iplisten 

In case the iplisten parameter is required / desired then both local IP and loopbacks are required like

netsh http add iplisten 127.0.0.1

netsh http add iplisten

Therefore the netsh http show iplisten would return:

It is mandatory to restart IIS with the command iisreset /noforce