Search Details Panel Info column shows HEX Code:
<0xc0041c0e>
Accelerator Server's Enterprise Vault Event Log Error:
Source: Accelerator Service Processor
Event ID: 297
Task Category: None
Level: Error
Description:
APP AT - Customer ID: X - Error processing Vault to Search off the queue: Searching Vault Thread - worker thread for index server: X (Y)
Vault ID: X
Number of tries: 5
Cause:<0xc0041c0e>
V-437-297
Enterprise Vault Server's Enterprise Vault Event Log Error:
Source: Enterprise Vault
Event ID: 7182
Task Category: None
Level: Error
Description:
Index Search failed: Unspecified error (0x80004005)
Index: ... /VolumeSet:...
Internal reference: SRCI
V-437-7182
Cause 1 Dtrace of the Accelerator Service process on the DA server while performing the Search shows:
(AcceleratorService) <2856> EV:L WinHttpRequest::Callback from WinHttp. Code=0x200000, context=0x0C10DF60
(AcceleratorService) <2856> EV:H WinHttpRequest::OnCallback. WINHTTP_CALLBACK_STATUS_REQUEST_ERROR.
(AcceleratorService) <2856> EV:H WinHttpRequest::OnCallback. WINHTTP_CALLBACK_STATUS_REQUEST_ERROR - Result=5, Error=12029|
(AcceleratorService) <2856> EV:H WinHttpRequest::OnCallback exit. ERROR HR=0x80004005.HR=0x80004005.
Cause 2 Dtrace of the AcceleratorService process on the DA server while performing the Search shows:
(AcceleratorService) <1836> EV:L WinHttpRequest::Callback from WinHttp. Code=0x200000, context=0x0DACED9C
(AcceleratorService) <1836> EV:H WinHttpRequest::OnCallback. WINHTTP_CALLBACK_STATUS_REQUEST_ERROR.
(AcceleratorService) <1836> EV:H WinHttpRequest::OnCallback. WINHTTP_CALLBACK_STATUS_REQUEST_ERROR - Result=5, Error=12007|
(AcceleratorService) <1836> EV:H WinHttpRequest::OnCallback exit. ERROR HR=0x80004005.
(AcceleratorService) <1836> EV:M WinHttpRequest::Callback from WinHttp. pRequest->OnCallback failed with HR=0x80004005. Calling pRequest->OnResponseComplete.
(AcceleratorService) <1836> EV:M IndexQueryServerRequest: OnResponseComplete - HR=Unspecified error (0x80004005)
Cause 3 Dtrace of the AcceleratorService process on the DA server while performing the Search shows:
(AcceleratorService) <1234> EV:L WinHttpRequest::Callback from WinHttp. Code=0x200000, context=0x0D10EAE0
(AcceleratorService) <1234> EV:H WinHttpRequest::OnCallback. WINHTTP_CALLBACK_STATUS_REQUEST_ERROR - Result=5, Error=12175|
(AcceleratorService) <1234> EV:L WinHttpRequest::Callback from WinHttp. Code=0x200000, context=0x0D20E630
(AcceleratorService) <1234> EV:L WinHttpRequest::Callback from WinHttp. Code=0x200000, context=0x0676D920
(AcceleratorService) <1234> EV:H WinHttpRequest::OnCallback exit. ERROR HR=0x80004005.
There following have been identified as possible causes of this issue.
1. This issue can be caused when HTTP requests are only listening on 127.0.0.1 (loopback address) on the Enterprise Vault (EV) Server.
2. This issue can be caused by a WINHTTP proxy being configured on the DA server.
3. This issue can be seen when Secure Socket Layering (SSL) is enabled in the environment, with EV being configured to use SSL in the EV Site's Properties > General tab in the Vault Administration Console, and there is an issue with the SSL certificate. The error code 12175 in the DTrace log entries above indicates ERROR_WINHTTP_SECURE_FAILURE.
This can be confirmed by testing access to the EV Search (EVS) web page from the Accelerator server, as follows:
- Open a browser on the Accelerator server.
- Browse to the EVS URL, typically at https://<evservername> to the EV Directory Server name.
- Review the browser page and determine if there are any prompts or indications listing certificate errors.
For Cause 1
Please run the below from command prompt to check the list of IP addresses listening for the http requests on the EV server
netsh http show iplisten
Make sure either the loopback address and the Enterprise Vault IP are added to the list, please add it using below command (using a privileged command line shell):
netsh http add iplisten ipaddress=
The output of the aforementioned command should return something similar to (where 192.168.2.3 would correspond to the Enterprise Vault Server)

For Cause 2
To check if we proxy exist on the DA server, run below command from the command prompt
netsh winhttp show proxy
In case the proxy exists, please take a note and remove it using below :
1. From a command prompt with administrator privileges, enter and execute the command:
netsh winhttp reset proxy
2. The command produces the output:
Current WinHTTP proxy settings:
Direct access (no proxy server).
3. Restart the Enterprise Vault Accelerator Manager Service (EVAMS).
4. Resubmit the previously failing searches.
For Cause 3
Certificate issues will need to be reviewed by the onsite team responsible for managing and maintaining the IT environment. Please contact your respective onsite technical support team to correct the certificate issue.