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 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 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
- Could not Load File or Assembly log4net, Version=220.127.116.11, culture=neutral
- 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
How to Modify the Coveo for Sitecore Security Provider Refreshing Parameters
The Security Provider is what Coveo uses to get the permissions from a source and map it to the indexed documents. That information is stored in the Security Cache. CES will periodically Refresh the Security Cache to ensure all permissions on documents are up to date. To do so, the Security Cache will use the Security Provider attributed to each sources.
With Coveo for Sitecore, it can be useful or even necessary to modify the defaults refreshing parameters on your Coveo for Sitecore Security Provider. This article explains how to do it.
- Coveo for Sitecore 863+
- Security Cache, Security Cache Refresh, Security Provider
There are 3 main components that control the Coveo for Sitecore Security Provider refreshing process:
What it does: The maximum amount of time in seconds that the Security Provider will wait for an update on the progress of its requests from Sitecore (300 seconds by default)
Why it’s useful: During the Security Cache refresh process, if the Coveo for Sitecore Security provider does not receive updates from Sitecore within the time specified by
MaxAllowedTimeWithoutProgress, it will abort the refresh.
Sample Error Message:
class CSP::SecurityException: Call to b__6 was aborted because no progress had been reported
What it does: The maximum number of users in a Sitecore Group that the Security provider can handle (2 000 by default)
Why it’s useful: During the refresh of the Security Cache, the Coveo for Sitecore Security provider expands the Sitecore Groups. To do so, it calls the Coveo Web Service in Site and asks for batches of users. However, if the number of users in a single batch (group) exceeds the
NumberOfUsersPerRequest, the refreshing process will be aborted.
Sample Error Message:
class CSP::SecurityException: Call to b\_\_6 was aborted because no progress had been reported
What it does: The maximum amount of time in seconds that the Security Provider will wait for a content web service request to complete (100 seconds by default)
Why it’s useful: During the Refresh of the Security Cache, the Coveo for Sitecore Security provider sends requests to Sitecore. If the Security provider doesn’t receive a response to its request before the time specified in
Timeout, it will abort the refresh.
Sample Error Message:
class CSP::SecurityException: Unexpected exception in method 'GetMembersAndMappings': System.Net.WebException: The request was aborted: The operation has timed out. ---> System.Net.WebException: The request was aborted
To change these Coveo for Sitecore Security Provider parameters:
- Open the CES Administration Tool.
- Go to Configuration > Security > Security Provider > Sitecore Security Provider for [YourMachine]
- In the Parameters section, click on Add Parameter.
Enter the name of each parameter and their respective values.