Coveo reindex error: The parameter 'p_Communication' must not be null

I was getting the following error when try to re-index Coveo in a new environment.
The parameter 'p_Communication' must not be null

This was fixed by setting the Sitecore username/password needed for communication between Coveo and Sitecore. You can do this by going to the Control panel in Sitecore. Under the Coveo search section, click on "Configuration" and then the "Configure" button under the Sitecore Credentials heading.

This is not an issue in a lower environment like your local since Coveo uses the default admin b password to authenticate. But this becomes an issue in any higher environment that doesn't use the default admin password. Hope this helps someone else.

Comments

Using Okta Authentication for a Sitecore client site

I recently had a project where we had to add a new Sitecore site to an already multi site Sitecore 8.2 Update 7 instance. This new site had to integrate with Okta to manage user authentication. I found many articles online that integrated Okta and Sitecore's admin interface but I could not find one that just integrated Okta with a client Sitecore site. My first step was to use Okta's available ASP.NET MVC projects on their Dev site and test them out. This worked very well with the first Authenticated method I tried which was WS-Fed. But when I tried to use the same authentication method with a site in Sitecore I got errors in my logs like the following: Sitecore.Security.Principal.SitecoreIdentity does not contain a definition for Claims Claims are available in HttpContext.User.Identity but not in Sitecore.Security.Principal.SitecoreIdentity, and since we are using a Sitecore site we could not read the claims. I tried to make claims work in Sitecore using various online a

Un Lock Sitecore admin account

There are times when you - Upgrade Sitecore locally - Restore databases in your local Sitecore instance. And you are no longer able to login to the Sitecore admin interface with the default admin username and password b. When this happens you can unlock the Sitecore admin account and reset the password back to b. To do this copy this aspx file to your Website\sitecore\admin folder (and overwrite existing file) Next make sure your local web.config (in the root Website) folder has the following settings minRequiredPasswordLength="1" minRequiredNonalphanumericCharacters="0" Lastly go to the following page https://YourSitecore.com/sitecore/admin/unlock_admin.aspx And click the Unlock Administrator button. That's it, you can now login to your local Sitecore instance. Happy Sitecoreing!

Sitecore media RequestExtension for images and pdfs

On your Sitecore site what is the media file extension you see? If you see .ashx for all your media (images, pdfs) read on. Ideally the IIS application pool for your website should be configured to use Integrated mode instead of classic mode. If that is the case, there is one default Sitecore 8 setting that you should change in your Sitecore.config FROM: <setting name="Media.RequestExtension" value="ashx"/> TO: <setting name="Media.RequestExtension" value=""/> This configures Sitecore to use the original file extensions rather than .ashx extension. So images would be jpg, gif, png's while pdfs would have the pdf extension. I also notice that Sitecore themselves have this configured on their website, so we should be good making this change. There are multiple benefits to the end user. They know the file types of media like pdfs before clicking on the download link CDN have cache settings that will be honoured

SITECOREing

Search This Blog