Could not create instance of type: Sitecore.ContentSearch.Azure.CloudSearchProviderIndex. No matching constructor was found

-

A. Scenario

Open Indexing Manager in Sitecore dashboard, the error below appears


B. Triaging

My Sitecore instance was deployed on Azure by another party. It was configured to used SOLR cloud as search engine. I want to switch to Azure Cognitive Search. 

It was supposed to be a simple switch by updating the app setting value in the web.config from 

<add key="search:define" value="Solr"/> to <add key="search:define" value="Azure"/>

But it was not.

C. Debugging

Step 1: Understand basic knowledge

For each of the indexes found in the Indexing Manager, it is created from a config file. For example, the sitecore_testing_index is configured with either Sitecore.ContentTesting.Solr.IndexConfiguration.config or Sitecore.ContentTesting.Azure.IndexConfiguration.config

Depending on whether we use the search:define value as Solr/Azure, one file will be activated and the other one will be deactivated accordingly.

Looking at the sitecore_testing_index section in the file Sitecore.ContentTesting.Azure.IndexConfiguration.config


This mean if Azure Cognitive Search is enabled, Sitecore will need to initialize the class Sitecore.ContentSearch.Azure.CloudSearchProviderIndex with the 4 params: name, connectionStringName, totalParallelServices, propertyStore

I learned it the hard way by decompiling the Sitecore.ContentSearch.Azure.dll

Switching to the file Sitecore.ContentTesting.Solr.IndexConfiguration.config, the  sitecore_testing_index section look like this:



This mean if SOLR is enabled, Sitecore will need to initialize the class Sitecore.ContentSearch.SolrProvider.SolrSearchIndex with the 3 params: name, core,  propertyStore

Step 2: Fix bug

From the above investigation, it is understood that each search index class accepts a different set of parameters during initialization.

Above error screenshot tell me that my class Sitecore.ContentSearch.Azure.CloudSearchProviderIndex is now are getting some odd parameter other than the 4 above mentioned

With the help of showconfig.aspx page, I managed to drill down to the culprit sitecore_testing_index section (after checking through many other "normal" indexes) and it shows an additional core param. It was inserted by some patch configuration file from the party in charge of installation. They obviously add it to work with SOLR but forget about Azure Cognitive Search. 

Disable that patch file and everything works as usual.

D. Conclusion

It is not likely you will get this error from Sitecore OOTB installation. However be careful when adding additional configuration. You need to consider the differences between SolrSearchIndex & CloudSearchProviderIndex as I mentioned.

Happy Sitecoring!


Comments

Post a Comment

Popular posts from this blog

Sitecore XP 9.2 - Scaling with Dedicated CD - Quick Installation [part 2]

-
Image
Warning:  The post here contains the author's own opinions and suggestions. They may not conform with best practices from Sitecore. Apply them at your own risks. If you have not read part 1, check out the link here first . Otherwise, delve down to the steps below. 1. Install DB server with MS SQL & SOLR The installation of MS SQL 2016 and SOLR 7.5.0 need no introduction. You can easily find the guide here: https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server?view=sql-server-ver15 or there: https://lucene.apache.org/solr/guide/7_5/installing-solr.html To install SOLR as a service, check out step 5 in here: https://blogs.perficient.com/2017/10/26/setup-and-basic-preparation-for-sitecore-9-installation/ Assuming that you will use the default port 8983 for installing SOLR in this step (and subsequent steps) Make sure that when installing MS SQL server, you are installing in mixed authentication mode so you will have SQL admin...
Read more

Troubleshooting Sitecore XP 9.2 - Experience Analytics error - Exception System.ArgumentNullException: typeKey should not be null.

-
Image
It isn't uncommon when you open up the Experience Analytics dashboard hoping to see some beautiful graphs and charts showing analytics data and boom! It welcomes you with the ugly red lines: I am usually very calm when dealing with errors in this dashboard because I have seen many root causes and found the fixes for them. Usually they are caused by certificate issues here or there . But this time looking at the log in the website, it shows a brand new error: 30240 10:24:37 ERROR [Sitecore Services]: HTTP GET URL http://mydomain.dev.local/sitecore/api/ao/aggregates/all/0751EFD8564F40A38083EF5C6E194247/-3191897772735422194?&dateGrouping=by-auto&&dateFrom=18-01-2020&dateTo=16-04-2020&keyGrouping=by-key Exception System.ArgumentNullException: typeKey should not be null. Parameter name: typeKey at Sitecore.Framework.Conditions.RequiresValidator`1.ThrowExceptionCore(String condition, String additionalMessage, ConstraintViolationType type) at Sitecor...
Read more

CI/CD with TeamCity + Sitecore 9.2 + Unicorn

-
Image
In this post, I will tell you how to setup CI/CD for Sitecore 9.2 with TeamCity. Solution Update Prerequisites: - Sitecore 9.2 project/solution created Firstly you would want to be able to synchronize Sitecore items between environments. I choose to use Unicorn which can be installed to your solution via Nuget. The version that I am using are 4.1.1. You will need to install both Unicorn & Unicorn Core packages: You can notice that the target framework for Unicorn packages are .NET Framework 4.7.2 which I use for my Sitecore 9.2 solution. Assuming that you have already known how to use Unicorn, the only place that you need to change to enable automatic deployment of Sitecore items is in Unicorn.Configs.Default.config By default, the value is false, you will need to update the above value to true. However I would not want to touch the default config file. I will create a transformed configuration file and update this value. I prefer using profile configuration ...
Read more