Indexing Service fails to start and Event ID 41293 is logged followed by Event ID 2280 in Application events.

Example event IDs include:

Event ID:         41293
Log Name:        Veritas Enterprise Vault
Source:             Enterprise Vault
Task Category: Index Admin Service
Level:                Error

Description:
An unexpected error has occurred.

Error Summary: Indexing Service start up error

Error Details: The HTTP service located at http://localhost/evindexing/Indexing Engine.aspx?v.app=api-soap& is unavailable, This could be because the service is too busy no endpoint was found listening at the specified

address. Please ensure that the address is correct and try accessing the service again later.

The remote Server returned an error (503) Server Unavailable.

Reference: ServicebaseEx::Run

Stack Trace:

Server stack trace:

at System.ServiceMqdeI.Chennels.HttpChannelUtilities.ProcessGetResponseWebException(WebException WebException, HttpWebRequest request, HttpAbortReason abortReason)

at System.ServiceMqdeI.Chennels.HttpChanneIFactory'1.HttpRequestChenneI.HttpChanneIRequest.WaitForRepIy(TimeSpan timeout)

at System.ServiceMqdeI.Chennels.RequestChaneel.Request(message message, TimeSpan timeout)

at System.ServiceMqdeI.Chennels. atSystemSenQeModeI.Dispatcher.RequestChanne18inder.Reque5t(Messzge message TimeSpan timeout)

at SystemServiceModel.ChanneIs.ServiceChannel.CaII(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

at System.ServiceModeI.ChanneIs.ServiceChannelProxy.InvckeService(IMethcdCaIIMessage methodCall, proxyOperationRuntime operation)

at System.ServiceMqdeI.Chennels.ServiceChanneIProxy.lnvoke(Message message)

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at Symantec.EnterpriseVault.lndexing.lndexingService.Index EngineSrvRef.Index EnginePort.RepositoryListXmI(RepositoryListXmlRequest request)

At KVS.EnterpriseVauIt.Runtime.WCF.WCFProxy'1 Invoke[TResult](Exception'1 method)

Event ID:         2280

Log Name:        Application
Source:             Microsoft-Windows-IIS-W3SVC-WP
Task Category: None
Level:               Error
Keywords:        Classic
User:                 N/A
Description:
The Module DLL C:\Windows\system32\inetsrv\httpPlatformHandler.dll failed to load.  The data is the error.

The reason for 503-Service unavailable is that the application pool is stopped. However, something else has caused the application pool to crash and finally leading to a stopped state. This application pool was stopped because of the default 5 consecutive exceptions within 5 minutes, which is the default behavior for the IIS worker process.

1. This issue starts occurring during the re-installation of the HttpPlatformHandler if you select a different location to install but fails to update the applicationHost.config file.

When the IIS native Modules () was installed for the first time, it registers its custom modules and for this, it makes entries in the IIS root configuration file i.e. applicationHost.config at this location C:\Windows\System32\inetsrv\config. These entries are made under the <globalmodules> section. You will see entries for httpPlatformHandler.dll as below:

At the time of uninstallation, these entries might not be removed from the applicationHost.config. The issue starts when while re-installing these modules again, the installation drive is changed. So, such DLL's will be copied at some other location but this entry is not modified in the applicationHost.config file.

While accessing the website, IIS will try to load this dll from the old path " %SystemRoot%\System32\inetsrv\httpPlatformHandler.dll" while this dll is not there and exists at some other path now.

While loading this dll, IIS will not be able to locate this and will throw an error and you must see an event mentioned above.

2. The Windows Update reinstalls IIS, however, it fails to update the applicationHost.config file, causing 32-bit application pools to try to load the 64-bit version of the before mentioned assemblies.

1.      Take a backup of applicationHost.config file.

2.      Stop IIS using iisreset /stop cmdlet.

3.      Remove HTTP Platform Handler Module using below steps:

a.       Open the %SystemRoot%\System32\inetsrv\config\applicationhost.config file (run as Administrator).

b.       Find and lines.

c.       Comment or remove those lines and save the file.

4.      Try restarting the Enterprise Vault (EV) Indexing Service and if it does not solve the problem, Reinstall HTTP Platform Handler Module.