41370, 41335, 41312 - Unable to connect to the EVIndexing virtual directory in IIS

Problem

EV 10 indexing services will not start when the EVIndexAdminService is unable to connect to the EVIndexing virtual directory in IIS.

Error Message

Type:  Error
Event:  41370
Source:  Enterprise Vault
Category: Index Admin Service
Description:
An error occured while synchronizing Indexing Engine metadata for Index volumes.
Error Details:
Could not connect to http://localhost/evindexing/Index Engine.aspx?v.app=api-soap&. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:80.
Unable to connect to the remote server
No connection could be made because the target machine actively refused it 127.0.0.1:80

V-437-41370

Type:  Error
Event:  41335
Source:  Enterprise Vault
Category: Index Admin Service
Description:
An error occured while trying to start indexing engine.
Further error details include: 'Could not connect to http://localhost/evindexing/Index Engine.aspx?v.app=api-soap&. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:80. '.

V-437-41335

Type:  Error
Event:  41312
Source:  Enterprise Vault
Category: Index Admin Service
Description:
The Indexing Service could not complete all the required startup routines: Starting Index Engine failed. Service will be stopped.

V-437-41312

A Dtrace of EVIndexAdminService shows:

(EVIndexAdminService) <4076> EV-L {IndexingWCFProxy`1} Calling RepositoryListXml
(EVIndexAdminService) <1772> EV-H {SERVICEBASEEX.EN_US} Waiting for some more time for Indexing Service to start. Start time[4:56:30 PM], Log Time[4:56:30 PM], Elapsed Time[00:00:14.1024000 ms]
(EVIndexAdminService) <4076> EV-L {IndexingWCFProxy`1} [2039ms] Called RepositoryListXml
(EVIndexAdminService) <4076> EV-H {VELOCITYPROXY.EN_US} Exception: Could not connect to http://localhost/evindexing/velocity.aspx?v.app=api-soap&. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:80.  Info: Diag: Type:System.ServiceModel.EndpointNotFoundException ST:|Server stack trace: |   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()|   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)|   at System.ServiceModel.Channels.HttpChannelFactory.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 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: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:80|   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)|   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)|   --- End of inner exception stack trace ---|   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)|   at System.Net.HttpWebRequest.GetRequestStream()|   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
(EVIndexAdminService) <4076> EV~E |Event ID: 41370 An error occurred while synchronizing Indexing Engine metadata for Index volumes.|Error Details:|Could not connect to http://localhost/evindexing/Index Engine.aspx?v.app=api-soap&. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:80. |Unable to connect to the remote server|No connection could be made because the target machine actively refused it 127.0.0.1:80
(EVIndexAdminService) <4076> EV-L {SERVICEBASEEX.EN_US} Releasing IDirectoryPublicV82 interface.

Cause

The EVIndexAdminService is attempting to http://localhost/evindexing/velocity.aspx?v.app=api-soap

The Log states that "No connection could be made because the target machine actively refused it 127.0.0.1:80."

Solution

Confirm that there are no requests from the local host in the W3SVC log file. 

IIS log file default location: inetpub\logs\logfiles\w3svc1

If there are no IIS listener Bindings for port 80, add them and then restart IIS.

How to add binding information to a site

1.Open Internet Information Services (IIS) Manager:

•If you are using Windows Server 2012 or Windows Server 2012 R2:

•On the taskbar, click Server Manager, click Tools, and then click Internet Information Services (IIS) Manager.

•If you are using Windows Server 2008 or Windows Server 2008 R2:

•On the taskbar, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

2.In the Connections pane, expand the server name, expand Sites, and then click the Web site on which you want to configure the bindings. 

3.In the Actions pane, click Bindings...

4.In the Site Bindings dialog box, click Add...

5.In the Add Site Binding dialog box, add the binding information, and then click OK.