Error HRESULT E_FAIL has been returned from a call to a COM component.
Upgrading to the April 2015 release. Just installed the Coveo Search API and followed steps of installation. However, Coveo Search API isn't running (and will terminate unexpectedly). Looked into systems logs and looks like it can't find the license, even though it's there.
212301879468469611|ERROR|2015-06-23|16:17:51|0|class CGLFile::FileCannotOpenException: An error occurred while opening the read-only file "C:\Program Files\Coveo Enterprise Search 7\instance/License.txt". (The system cannot find the file specified. [0x00000002])|||
Does it have to do with the face that there's a
</> instead of a
<\>? Isn't that weird?
I think therefore, diagnostics is telling me there's a 500 on the security service and also a 503 on the REST endpoint.
Hi, so the error disappeared for a while but then reappeared again, which was weird. I looked at the Even Viewer and found this:
Request format is unrecognized for URL unexpectedly ending in '/GetVersion'. at System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext context, String verb, String url, String filePath) at System.Web.Script.Services.ScriptHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String pathTranslated) at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) https://<websitename>/sitecore modules/Web/Coveo/webservice/sitecorewebservice.asmx/GetVersion /sitecore modules/Web/Coveo/webservice/sitecorewebservice.asmx/GetVersion
What is the user running the CES service? Is this user have permission to read/write the license file?
When you install CES and start the service for the first time, this is normal that there is no license. It will be set by Coveo for Sitecore at the first indexing operation.
When you install the Coveo Search API, its
config.yml file isn't configured to connect to your local CES instance. This is why it stops when you try to start it. This is normal. It will be configured and started by Coveo for Sitecore at the first indexing operation.
After installing Coveo for Sitecore, if you open its diagnostic page, it is normal to see an error for the following 2 components because no indexing operation was performed yet in Sitecore:
- Coveo Search REST Endpoint ()
- Coveo Security Provider
The installation documentation of Coveo for Sitecore states that after installing the softwares, the next action is to rebuild your indexes (see Installing Coveo for Sitecore on a Single Host). At the first indexing operation (and all subsequent indexing operations too), Coveo for Sitecore will configure the Coveo Search API if it is not already running. It will also set the CES license if it cannot be found. It will then create or update the CES collection, sources, field sets, user identity and security provider automatically.
Then, if you refresh the Coveo for Sitecore diagnostic page, all the components should be green.