-
Most Common Issues
- Inactivity Timeout During Rebuild
- Coveo Sort Components Are Stacked in an MVC Search Page
- Security Provider Error Something Went Wrong on the Server
- Problem Accessing the Coveo Admin Service
- Problem Loading the Ninject Assembly
- Empty Strings are not Allowed Exception Occurring When Specifying Creator-Owner Permissions
- Internal Server Error When Querying the REST Service
- Editing the Properties of a Coveo Search MVC Component Freezes the Page Editor in IE11
- Error with ID NO\_DOCUMENT\_INDEXED
- Error or Document Not Found Page After Rebuilding the Indexes
- Problem Registering Search Page Events in Sitecore Analytics Database
- Sitecore Items Do Not Get Automatically Indexed
- Sitecore 8.0 Session is not Initialized Exception
- The Indexing Manager Is Reporting an Error
- Configuration Wizard error - Unable to add the certificate to the Root store. Access is denied.
- Slow Queries in a Coveo-Powered Search Page
- Issue in IE During Admin Service Configuration with the Configuration Wizard
- High Memory Usage While Rebuilding Indexes
- Root Element of a Crawler for a Coveo Index is Invalid
- 404 Errors on Coveo Usage Analytics Search Events
- HTML Version of Indexed Items Are Showing an Error Page
- Coveo-Powered Search Page Fails to Load After Upgrade
- Diagnostic Page Error - Invalid cast from System.String to Coveo.Framework.Configuration.SecurityConfiguration
- Including a Search Box with OmniboxResultList Results in Cannot read property addEventListener of null Error
- Timeout While Expanding Sitecore Security Provider
- NullReferenceException on Tracking.Current When Executing a Request for a Quick View
- Coveo for Sitecore Security Cache Refresh Issues
- How to Modify the Coveo for Sitecore Security Provider Refreshing Parameters
- 403 Forbidden Error When Calling YourSitecoreSite/coveo/rest
- Getting log4net Errors When Attempting to Browse Sitecore Pages
- The Sitecore Security Provider ABC has encountered a fatal exception class CSP FatalException Unable to connect to Sitecore
- No User has been Provided for the Search Request
- Opening Sitecore Indexing Manager Returns a 405 (Method Not Allowed) Error
- Secured Admin Service - Could Not Establish Trust Relationship for the SSL/TLS Secure Channel with Authority Localhost
- Hive Components - Inserting an Example Search Page Results in No Renderings
Slow Queries in a Coveo-Powered Search Page
Symptoms
When executing a query in a Coveo-Powered Search Page, search results may take a considerable amount of time before they’re returned.
Causes
Slow queries can be caused by a number of factors:
- Low performance hardware. For example, virtualized servers are known to be slower than physical ones. Also, indexes containing a lot of documents are typically slower than smaller ones.
- High network latency. This slows down communications between Coveo for Sitecore and the Coveo Search API, so your queries take a longer time to return search results.
-
Overly complex query expressions. For example, query expressions containing wildcards are a common cause of bad query performance.
Wildcard query expressions are field queries that use the
*=
operator and one or more star (*
) or question mark (?
) character in the value.Example of a wildcard query expression
@fz95xfullpath56518*="/sitecore/content/Home*"
Before the April 2015 release of Coveo for Sitecore, the
where the item is the specific item or one of its subitems
filtering rule was generating a wildcard query on the_fullpath
field as in the previous example.
Resolution
- Low performance hardware: see with your IT administrator.
- High network latency: see with your IT administrator.
- Overly complex query expressions:
- Whenever possible, avoid using wildcards in query expressions. Instead, use exact match expressions (e.g.,
@field=="value"
) or basic “contains” expressions (e.g.,@field="value"
) for better performance. - If you’re using a release earlier than Coveo for Sitecore April 2015 Monthly Release (3.0.1000) and the
where the item is the specific item or one of its subitems
filtering rule:- The best solution is to upgrade Coveo for Sitecore to the April 2015 release or newer. These releases aren’t using the wildcard query expressions anymore in the
where the item is the specific item or one of its subitems
filtering rule. Coveo for Sitecore now uses an exact match query on the_path
field. - If an upgrade isn’t possible, you can stop using the
where the item is the specific item or one of its subitems
rules and convert them towhere specific field compares to specific value
rules:- Ensure that the
_path
field is configured as a multi-value facet field:- Open your
Coveo.SearchProvider.config
file in a text editor. -
Ensure that the
<fieldType fieldName="_path"... />
element is present and has theisFacet="true"
andisMultiValue="true"
attributes and values in the<fieldNames ...>
element like the example below.-
If the element is missing, create it.
-
If its
isFacet
andisMultiValue
attributes aren’t set totrue
, set them totrue
like in the example below.<fieldMap type="Coveo.SearchProvider.CoveoFieldMap, Coveo.SearchProvider"> ... <fieldNames hint="raw:AddFieldByFieldName"> ... <fieldType fieldName="_path" isFacet="true" isMultiValue="true" settingType="Coveo.Framework.Configuration.FieldConfiguration, Coveo.Framework" /> ... </fieldNames> ... </fieldMap>
-
-
Save and close the file.
- If you created the field or changed its configuration, rebuild the Sitecore indexes to synchronize the field configuration with CES.
- Open your
- Replace any use of the
where the item is the specific item or one of its subitems
filtering rule with thewhere specific field compares to specific value
filtering rule:- Field:
_path
- Compares to: is equal to
- Specific value: short GUID of the root item to display
- Field:
- If you have a
where the item is the Home item or one of its subitems
filtering rule, you should change it for awhere _path field is equal to 110D559FDEA542EA9C1C8A5DF7E70EF9
filtering rule where the Home item short GUID is 110D559FDEA542EA9C1C8A5DF7E70EF9.
- Ensure that the
- The best solution is to upgrade Coveo for Sitecore to the April 2015 release or newer. These releases aren’t using the wildcard query expressions anymore in the
- Whenever possible, avoid using wildcards in query expressions. Instead, use exact match expressions (e.g.,