Unhandled Exception in Content Editor Prior to Coveo for Sitecore Activation

Coveo for Sitecore (October 30, 2020) Coveo for Sitecore (December 11, 2020)

Symptoms

After installing Coveo for Sitecore, but prior to its activation, you get an unhandled exception if you try to load the Content Editor.

Exception Details: System.InvalidOperationException: Could not find configuration node: coveo/restEndpointConfiguration
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[InvalidOperationException: Could not find configuration node: coveo/restEndpointConfiguration]
Sitecore.Configuration.DefaultFactory.GetConfigNode(String xpath, Boolean assert) +543
Sitecore.Configuration.DefaultFactory.CreateObject(String configPath, String[] parameters., Boolean assert) +187 Coveo.Framework.Configuration.RestEndpointConfigurationFactory.GetConfiguration() +27 System.Lazy'l.CreateValue() +734 System.Lazy'1.LazyInitValue() +189
Coveo.SearchProvider.Licensing.Processors.<>c	DisplayClass6_0.<.ctor>b	11() +19
Coveo.SearchProvider.Licensing.Processors.RemoveActions.Process(Sections p_Sections) +69

Cause

Changes in the October 30, 2020 release of Coveo for Sitecore cause a situation where the Sitecore instance tries to load a node from a still disabled configuration file.

Resolution

The issue was fixed in the December 2020 release of Coveo for Sitecore.

Workaround

As a workaround, you can follow the steps below after installing Coveo for Sitecore.

  1. Disable the Coveo.SearchProvider.Licensing.config by renaming it Coveo.SearchProvider.Licensing.config.disabled.

  2. Perform the actions you want to perform in the Content Editor.

  3. Remove the .disabled extension you added to the Coveo.SearchProvider.Licensing.config file in step 1.

  4. Activate Coveo for Sitecore.

Recommended Articles