Gravatar for praful.memane@towerswatson.com

Question by prafulmemane, Feb 26, 2016 3:47 PM

Error in Sitecore_analytics_index (lucene) when crawling due to Coveo default processor

Hi Team, I have a

Sitecoreanalyticsindex

(lucene) which is throwing error while crawling the latest visits.

ManagedPoolThread #80 15:40:19 INFO Crawler [sitecoreanalyticsindex]: 4 items to index ManagedPoolThread #80 15:40:19 WARN Crawler : Update failed

  • contactTag|cadbd4dc-6924-4d67-a4de-18add28ac5ceFull name Exception: System.NullReferenceException Message: Object reference not set to an instance of an object. Source: Coveo.SearchProviderBase at Coveo.SearchProvider.InboundFilters.ItemPathInboundFilter.<>cDisplayClass4.b1(String path) at System.Linq.Enumerable.Any[TSource](IEnumerable1 source, Func2 predicate) at Coveo.SearchProvider.InboundFilters.ItemPathInboundFilter.Process(InboundIndexFilterArgs p_Args) at (Object , Object[] )
    at Sitecore.Pipelines.CorePipeline.Run(PipelineArgs args) at Sitecore.Abstractions.CorePipelineWrapper.Run(String pipelineName, PipelineArgs args) at Sitecore.ContentSearch.Pipelines.IndexingFilters.InboundIndexFilterPipeline.Run(ICorePipeline pipeline, InboundIndexFilterArgs args) at Sitecore.ContentSearch.LuceneProvider.LuceneIndexOperations.BuildDataToIndex(IProviderUpdateContext context, IIndexable version) at Sitecore.ContentSearch.LuceneProvider.LuceneIndexOperations.Update(IIndexable indexable, IProviderUpdateContext context, ProviderIndexConfiguration indexConfiguration) at Sitecore.ContentSearch.Crawler1.DoUpdate(IProviderUpdateContext context, T indexable, IndexEntryOperationContext operationContext) at Sitecore.ContentSearch.FlatDataCrawler1.<>cDisplayClass18.b12(T indexable, ParallelLoopState loopState)

So I believe the default setting in Coveo.SearchProvider.config file. As per the post https://developers.coveo.com/pages/releaseview.action?pageId=31916270

true

Not able to understand why is it calling ItemPathInboundFilter processor which is configured in Coveo.SearchProvider.config and the Sitecore.ContentSearch.config is pretty empty

Coveo.SearchProvider.config settings

What is needed to fix this issue?

2 Replies
Gravatar for esavoie@coveo.com

Answer by esavoie, Mar 1, 2016 10:54 AM

The problem is that inbound filters are affecting all Sitecore indexes and not only the Coveo ones. I believe this post contains an answer to your question:

https://answers.coveo.com/questions/3690/sitecore-inbound-filtering-abort-inbound-filter-pipeline-to-certain-indexes-only

Gravatar for praful.memane@towerswatson.com

Comment by prafulmemane, Mar 1, 2016 11:08 AM

Hi Eric, This was a post by our developer Abhishek Shrivastava (@abhisfortitude) who had implemented in our solution already. We are in-process to upgrade Sitecore 8.1 and Coveo 3.0 Jan 2016 release and wanted to make sure that Coveo fixes this issues in the latest release "A fix has been done for this and will be delivered with September 2015 release, along with the ability to choose which filter is applied to which Coveo index." - (05 Aug '15, 12:35) sbelzile

Gravatar for chris.williams@readwatchcreate.com

Comment by chris williams, Apr 25, 2016 1:37 PM

Hi all, I am getting the same error in v8.1 when I go to List Manager and create a new empty list. What specifically do I need to change regarding this? I am using these versions:

Current Coveo for Sitecore version: 3.0.1226.0

Current Sitecore version: 8.1.151207

Gravatar for jflheureux@coveo.com

Answer by Jean-François L'Heureux, Apr 25, 2016 3:33 PM

Hi,

As @esavoie stated, this exception occurs because you have the Coveo.SearchProvider.InboundFilters.ItemPathInboundFilter inbound filter processor enabled in the Coveo.SearchProvider.config file. Pipeline processors are cumulative even if declared in different configuration files.

As explained in the Coveo documentation (see Excluding Sitecore Items From Your Index), using Sitecore's indexing.filterIndex.inbound pipeline is not a good idea as it runs its processors for all the Sitecore indexes (Coveo, Lucene, Solr…). It is recommended to at least upgrade to the September 2015 release of Coveo for Sitecore 3.0 to be able to use the coveoInboundFilterPipeline pipeline instead.

Ask a question