Gravatar for mkrimi@absolunet.com

Question by mohamed krimi, Oct 22, 2014 2:57 PM

Why only ''queuedocument'' document type are indexed ?

Hi guys, The Sitecore Search Provider Document Type Set shows that Web Pages and PDF Document Type could be indexed. However, my index source indexes only ''queudocument'' Document type. Is it a configuration Issue ?

I'm using Coveo for sitecore 72. with the default Coveo.SearchProvider config file. Thank you.

Gravatar for cbolduc@coveo.com

Comment by Carl Bolduc, Oct 22, 2014 3:53 PM

Which build of Coveo for Sitecore are you using?

4 Replies
Gravatar for mkrimi@absolunet.com

Answer by mohamed krimi, Oct 22, 2014 5:30 PM

Hi Vincent, Thank you for the follow up.

When we try to rebuild the index : the indexing is working properly in Sitecore Index Manager (no front-end error) but the CES Console is not logging any activity. Only Rabbit MQ still showing activity.

In our Sitecore log files, we have an ''Invalid URIFormatException'', in that case it seems that Coveo skip the indexing process for that item.

I also noticed that the only indexed elements have (Langue : Langue inconnue) in Source > Details > Propreties (PS: Note that our sitecore is running on a french instance of Windows Server/IIS, and all items have a custom url such as domain/fr/item-url and not the default sitecore Url with /fr-CA/ prefix).

I hope this will help you. Thank you.

----- Log output : ManagedPoolThread #2 16:33:24 ERROR An exception occurred while trying to process the item {1D9065B8-015F-434F-855C-7B6FB9D6636E} : URI non valide : Impossible de déterminer le format de l'URI. Exception: System.UriFormatException Message: URI non valide : Impossible de déterminer le format de l'URI. Source: System à System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) à Coveo.SearchProvider.Documents.ItemLinkFactory.GetClickableUri(IIndexableWrapper pIndexable) à Coveo.SearchProvider.Documents.DocumentBuilder.AddLinks() à Coveo.SearchProvider.Documents.DocumentFactory.CreateIndexableItem(IIndexableWrapper pIndexable, IPipelineArgsFactory pPipelineArgsFactory, PropertyStoreConfig pPropertyStoreConfig)

ManagedPoolThread #2 16:33:24 ERROR Item {1D9065B8-015F-434F-855C-7B6FB9D6636E} will be skipped because an exception occurred while processing it. An exception occurred when processing the item with the id : {1D9065B8-015F-434F-855C-7B6FB9D6636E} Exception: Coveo.Framework.Exceptions.InvalidItemException Message: An exception occurred when processing the item with the id : {1D9065B8-015F-434F-855C-7B6FB9D6636E} Source: Coveo.SearchProviderBase à Coveo.SearchProvider.Documents.DocumentFactory.CreateIndexableItem(IIndexableWrapper pIndexable, IPipelineArgsFactory pPipelineArgsFactory, PropertyStoreConfig pPropertyStoreConfig) à Coveo.SearchProvider.IndexOperations.d_2e.MoveNext()

Nested Exception

Gravatar for vseguin@coveo.com

Comment by Vincent Séguin, Oct 22, 2014 6:20 PM

It seems like it gives invalid urls when trying to reindex. It's probably caused by your custom link provider. Try setting a ServerUrl in your Coveo.SearchProvider.config. If it doesn't work, let me know, we had an issue with custom link providers recently, and you would need the latest November build to fix it.

Here's the documentation for the ServerUrl: https://developers.coveo.com/display/SC201410/Understanding+the+Coveo+Search+Provider%27s+Configuration+File

Gravatar for mkrimi@absolunet.com

Answer by mohamed krimi, Oct 22, 2014 4:19 PM

Coveo for Sitecore 72 3.0 (758)

Gravatar for vseguin@coveo.com

Answer by Vincent Séguin, Oct 22, 2014 4:50 PM

Hi Mohamed,

It is normal. Your documents are coming from the Queue Crawler, hence they are recognized as queuedocuments. Their bodies are empty, so CES doesn't detect any specific document type. If you try to index some Media Library items however (files, pdf etc.), they will be recognized with their good types.

Gravatar for mkrimi@absolunet.com

Answer by mohamed krimi, Oct 23, 2014 10:31 AM

Hi Vincent, thanks for the tip I confirm Setting ServerUrl and Rebuilding the index had fixed the UriFormatException issue.

Still have Unkonwn Language in my Index Source Language Field but i'm sure it's not related to the Uri Issue. May be due to the .Net CultureInfo Language value (''French'' vs ''Français'') ?

Thanks again and have a nice day.

Gravatar for vseguin@coveo.com

Comment by Vincent Séguin, Oct 23, 2014 10:33 AM

Hi Mohamed,

Yes, it could definitly be related to the .NET CultureInfo language value. I suggest you enter a support ticket for that, we could look at it since it looks like a bug.

Don't forget to accept the answers :)

Thank you, Vincent

Ask a question