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=184.108.40.206, 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
Coveo for Sitecore Security Cache Refresh Issues
When Refreshing the Security Cache, the process goes on and eventually stops with some or all of your securities not being updated on your documents.
In addition, you see one of these error messages in your CES System Log (
WARNING\|20XX-XX-XX\|00:00:00\|0\|Error while expanding group (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: The operation has timed out
WARNING\|20XX-XX-XX\|00:00:00\|0\|Error while expanding group (class CSP::SecurityException: Call to b\_\_6 was aborted because no progress had been reported for X seconds.)
- Coveo for Sitecore 558+
- Security Cache, Security Cache Refresh
- From your CES Server, open a Web Browser and connect to your Sitecore instance Home Page.
- Are you able to connect to your Sitecore instance? If yes, proceed to Diagnostic Step 2.
- If you can’t connect to your Sitecore Instance Home Page from your CES Server, contact your IT department.
Coveo for Sitecore Security Provider must be able to connect to your Sitecore Server from your CES Server. Otherwise, the Refresh of the Security Cache will fail.
Following the documentation on How To Modify the Coveo for Sitecore Security Provider Refreshing Parameters,
- Open the CES Console.
- Set the MaxAllowedTimeWithoutProgress parameter to 10800.
- Refresh the Security Cache.
- Do you see the error in the Console during the Refresh? If yes, proceed to point 5.
- Set the NumberOfUsersPerRequest parameter to 50000.
- Refresh the Security Cache.
- Do you see the error in the Console during the Refresh? If yes, proceed to point 8.
- Set the Timeout parameter to 3600.
- Refresh the Security Cache.
- Do you see the error in the Console during the Refresh? If yes, proceed to Diagnostic Step 3 below.
Factors like the amount of users and groups, the size of each groups, the speed of your Sitecore instance and the latency on your Network can cause the Security Provider to fail.
The main reason is that Security Provider has default configurations that works in most environments and it sometime needs to be modified.
- Open the Windows Event Viewer(https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc766042(v=ws.11)) Application Logs.
Around the same time as the error message occurs in your System Log, do you see this error:
Process information:Process ID: 36604Process name: w3wp.exeAccount name: NT AUTHORITY\\NETWORK SERVICEException information:Exception type: HttpExceptionException message: Request timed out.Request information:Request URL: http://serverName.org/sitecore \[^\]modules/web/coveo/webservice/SitecoreWebService.asmxRequest path: /sitecore modules/web/coveo/webservice/SitecoreWebService.asmxUser host address: xx.xx.xx.xUser: sitecore\\CoveoCrawlerIs authenticated: TrueAuthentication Type:Thread account name: NT AUTHORITY\\NETWORK SERVICEThread information:Thread ID: 9Thread account name: NT AUTHORITY\\NETWORK SERVICEIs impersonating: False
- If yes, proceed to Diagnostic Step 4.
- If you don’t see the error, contact Coveo Support.
This message is stating that the SitecoreWebService itself timeout following a request.
Since the Event happens at the same time than the Refreshing of the Security Cache, it means that the request from the Coveo for Sitecore Security Provider caused the service to timeout.
There are two possible reasons for this:
- Too many users/roles on a Sitecore role. Takes more time to expand it.
- Slow Sitecore server. May be due to hardware of the server or its load.
- Open the
- Locate the
<httpRuntime maxRequestLength="512000" executionTimeout="600" enableKernelOutputCache="false" relaxedUrlToFileSystemMapping="true"/>node.
executionTimeoutto a higher number, like 3600.
The solution is to increase the maximum amount of time that the SitecoreWebServices is allowed to take in order to complete the request.