-
Known Issues
- An Index Should Be Configured for Database web Error Is Preventing the REST Service from Loading
- Cannot insert the value NULL into column ID, table INSTANCE_HOSTNAME_Core.dbo.Properties column does not allow nulls. INSERT fails.
- Coveo for Sitecore Not Properly Replicating the Sitecore Permission Model
- ERROR Error in FileWatcher Internal Buffer Overflow While Installing Coveo for Sitecore
- ERROR Exception while handling event Sitecore.ContentSearch.Events.IndexingFinishedEvent, Index MY_INDEX was not found
- Error in the Experience Profile After Installing Coveo for Sitecore
- Failed to Reactivate the Organization Message in Command Center
- Field Is No Longer Indexed in the Sitecore Items
- Handler CoveoSearchEndpoint has a bad module ManagedPipelineHandler in its module list
- Items in Different Languages Are Not Automatically Indexed or Updated When Language Fallback Is Enabled
- Metadata Duplicated Keys are Producing Warnings in the Log Browser
- Missing Valid xDB License
- Multi-Value Field - Migrating from On-Premises to Cloud Version
- Opening the Experience Explorer Sets the Static Context to 'Master'
- Prebinding Isn't Applied to Elements Within a Searchbox Container
- Publishing Multi-Language Sitecore Items Leads to a Large Amount of Files Being Indexed
- Sitecore 8.0+ Error When Saving a Coveo-Powered Search Page Using the Sitecore Rule Engine
- Sitecore 8.2 With WFFM Refuses to Start After Installing Coveo for Sitecore
- Sitecore.ContentSearch.SitecoreItemCrawler.IsAncestorOf(Item item) error
- Slow Initial Rebuild Time Caused By The ExcludeCoveoDataSourceItems Processor
- Solr - Error When Initializing Coveo When Side-by-Side with Solr Is Enabled
- Solving the Conflict Between Keys from Dynamic Placeholder Modules and Coveo Dynamic Placeholders
- The Experience Editor for Non-Default Language Page Fails to Load When Using Coveo for Sitecore Hive
- The RouteData must contain an item named 'controller' error with SXA
- Two Instances of the Same Search Page Component Have Been Added on a Page but Only One is Initialized
- Unexpected Token < When Editing Page With SXA Components in Experience Editor
- Send Analytics to Sitecore Component Not Working in Sitecore 9
- Exception When Trying to Switch Organization
- Issues When the Core Database Is Disabled on Content Delivery Servers
- Content Database 'master' Not Found on a Content Delivery Server
- Coveo Analytics Events Are Not Logged in Sitecore 9.1 Analytics
- Ajax Error 500 When Using Special Characters in a Query
THIS IS ARCHIVED DOCUMENTATION
Send Analytics to Sitecore Component Not Working in Sitecore 9
Coveo for Sitecore 4.1 (February 2019)
Symptoms
When using the Send Analytics to Sitecore
component in a Coveo-powered search page in Sitecore 9, you get the following error message on a searchFromLink
event:
Server Error in '/' Application.
Precondition failed: The parameter 'p_EventData' must not be null
Parameter name: p_EventData
Description: An unhandled exception occurred.
Exception Details: System.ArgumentNullException: Precondition failed: The parameter 'p_EventData' must not be null
Parameter name: p_EventData
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:
[ArgumentNullException: Precondition failed: The parameter 'p_EventData' must not be null
Parameter name: p_EventData]
Coveo.Framework.CNL.Precondition.NotNull(Object p_Parameter, String p_ParameterName) +181
Coveo.Framework.CNL.Precondition.NotNull(Object p_Parameter, Func`1 p_ParameterExpression) +27
Coveo.Analytics.Events.SqlEventTracker.Track(PageEventData p_EventData) +162
Coveo.Analytics.xDB.Processors.HandleSitecoreSearchEventProcessor.Process(CoveoAnalyticsPipelineArgs p_Args) +333
Cause
A Coveo.Analytics.xDB.config
patch command isn’t applied because configuration files aren’t loaded in the proper order.
Resolution
The issue has been corrected in the February 2019 version of Coveo for Sitecore 4.1 by moving the Coveo.Analytics.xDB.config
file into a new Analytics
sub-folder.
Workaround
If you don’t want to upgrade to the February 2019 version of Coveo for Sitecore 4.1 right now, you can perform the following steps to have the Coveo.Analytics.xDB.config
file load at the right moment in the configuration file loading sequence:
- In a file explorer window, open the
<SITECORE_INSTANCE_ROOT>\App_Config\Modules\Coveo
folder. - Create a sub-folder called
Analytics
. It must be calledAnalytics
exactly to avoid issues during a future upgrade. - Select and cut the following files from the
<SITECORE_INSTANCE_ROOT>\App_Config\Modules\Coveo
folder:Coveo.Analytics.XConnect.config.disabled
Coveo.Analytics.xDB.config
- Paste the files in the
<SITECORE_INSTANCE_ROOT>\App_Config\Modules\Coveo\Analytics
folder.
What's Next for Me?