Gravatar for shirazi@rdacorp.com

Question by aga, Oct 6, 2015 5:44 PM

No Search results - Coveo Search Web Service failure

Hi,

I have CES installed on VM-A along with Sitecore (CMS) and now I'm setting up VM-B (delivery) but I'm not seeing any results show up on the delivery VM (but works on CMS VM). The search API is also installed on VM-A (CMS). When I run the diagnostics the "Coveo Search Web Service" fails with error

Exception Name:class CES::SearchServerException, What:class CES::SearchServerException: No user has been provided for the search request. (Hide details)

System.ServiceModel.FaultException`1[Coveo.Framework.CoveoSearchService.ExceptionBaseDetail]: Exception Name:class CES::SearchServerException, What:class CES::SearchServerException: No user has been provided for the search request. (Fault Detail is equal to Coveo.Framework.CoveoSearchService.ExceptionBaseDetail).

I've ensured that the "server url" is pointing to VM-A. Security provider is also set and is passing the diagnosis. The cert is also copied locally and the path is valid. Hitting http:///coveo/rest is returning 64317 results. Firewall is disabled on VM-A Tried clearing the security cache from the AdminTool

One difference that Ive noticed between the 2 VMs is that when I look into the query parameters made by JS, the field names are postfixed with difference values i.e. VM-A is postfixed with 64624 and the VM-B is 21506

What can i be possibly missing?

Thanks

1 Reply
Gravatar for jflheureux@coveo.com

Answer by Jean-François L'Heureux, Oct 7, 2015 7:56 AM

The "Coveo Search Web Service" is the SOAP Search Service inside CES. This exception generally occurs when the security provider is not yet created inside CES.

Please verify the <AdminServiceUri> and <SearchServiceUri> nodes values to ensure they are using URIs with VM-A as the host.

Please verify the <CesConfigurationPath> node value to ensure it is the same as on the CMS and the <SearchCertificatePath> node value to ensure the certificate was copied to this path on the VM-B.

The postfix issue is due to the <SourceName> nodes of the Sitecore indexes configuration. They also need to be the same across all the Sitecore servers of a farm (CMs and CDs) (see Installing Coveo for Sitecore in a CM/CD Configuration). The postfix is also different if you run the search page in normal mode (published version) or in edit/preview mode (in the Page/Experience Editor).

Gravatar for shirazi@rdacorp.com

Comment by aga, Oct 7, 2015 11:16 AM

Hi Jeff,

Adding the sourceName fixed the "no results" issue.

But the "Coveo Search Web Service" is still failing diagnostics. I've verified the AdminServiceUri and SearchServiceUri are pointing to VM-a. CesConfigurationPath is pointing to the same dir on VM-a. And I can hit both urls (AdminServiceUri and SearchServiceUri)

Is it normal to get a certificate error when hitting SearchServiceUri?

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Oct 7, 2015 11:51 AM

<CesConfigurationPath> must be a path local to the Sitecore machine. So on VM-A CMS config, the path should be local to VM-A file system. On VM-B CD config, the path should be local to VM-B file system. On both cases, the .p12 certificate file should be located at that path.

It is normal to get a certificate error when opening the SearchServiceUri in a browser because you are not providing the .p12 certificate in your connection attempt. Ignore the error and continue.

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Oct 16, 2015 6:10 PM

What is the user that runs your Sitecore AppPool? Is it a local machine user or a domain user?

Ask a question