The WARN The given item URI is invalid (). The current item could not be loaded. message is normal when you manually load this URL. Normally, the Coveo for Sitecore UI components will call this URL with a sitecoreItemUri query string parameter containing the URI of the search page as stored by the index. The Coveo for Sitecore REST endpoint proxy use that URI to find the current context database.

I have some questions:

Are CES and Sitecore on the same machine or separate machines?

Which user is reported in the CES Console when you do the query?

Which security provider is reported in the CES Console when you do the query?

Does that security provider exist in CES?

In that security provider, what is the "Sitecore Server URL"?

Is this URL valid when typed in a browser on the CES machine? Can this machine access that URL?

In the CES index browser, when you expand the details of a Sitecore item, what are the permissions in the "Effective Combined Permissions"?

1 Reply

"No user or group to display" is not normal for the permission of indexed Sitecore items. It is supposed to list at least "Anonymous" with allowed to true for generic Sitecore items that should be publicly available. This means that the security is not correctly indexed for the Sitecore items. Thus, the secure queries return no search results.

Possible causes:

At the time of the first rebuild, CES was unable to contact the Coveo Security Service (web service inside Sitecore. Uses the Sitecore Server URL) to expand the Sitecore roles and users.

CES is still unable to contact the Coveo Security Service.

<IndexPermissions> is set to false in the Coveo for Sitecore Coveo.SearchProvider.config file.

The Sitecore API is unable to provide the Sitecore security of indexed items for an unknown reason.

Possible solution paths:

Ensure CES is able to access the Coveo Security Service by validating the Sitecore Server URL in the security provider (already done here).

Remove the <IndexPermissions> element from the Coveo.SearchProvider.config file to revert to the default value (true) and rebuild the Sitecore indexes.

Check the Sitecore logs when rebuilding the Sitecore indexes and refreshing the Coveo index security cache to identify problems with Sitecore security or Coveo for Sitecore.

If the above suggestions do not work, can you click on that "Effective Combined Permissions" dropdown menu and give me all the level and set names along with the permissions in those sets. Something like: