After logging to the Sitecore content tree, getting the below error while performing the search.

An error occured while searching. Rephrase the query.

Could not resolve type name: Sitecore.Pipelines.Search.SearchSystemIndex, Sitecore.Kernel (method: Sitecore.Configuration.DefaultFactory.CreateFromTypeName(XmlNode configNode, String[] parameters, Boolean assert)).

The search is working fine when we perform search in web site. Using SOLR 5.1 version for search.

  • Which version of Sitecore do you use? – Peter Procházka Mar 5 '18 at 15:40
  • @chorpo ...Sitecore 8.2 version. – Pushpendra Vats Mar 5 '18 at 15:42
  • 1
    did you upgrade your site from 7? – Vlad Iobagiu Mar 5 '18 at 17:52
  • yes we have upgraded from 7.2 version. – Pushpendra Vats Mar 5 '18 at 17:58

In Sitecore 7.2 you have bellow configurations into \Website\App_Config\Include\Sitecore.ContentSearch.config file :

             This processor executes search expressions that use the Sitecore.ContentSearch indexes when the Search.UseLegacySearchEngine setting is set to false.
        <processor patch:before="*[@type='Sitecore.Pipelines.Search.SearchSystemIndex, Sitecore.Kernel']" type="Sitecore.ContentSearch.Client.Pipelines.Search.SearchContentSearchIndex, Sitecore.ContentSearch.Client" />

and into web.config

    <!-- other processors -->
    <processor type="Sitecore.Pipelines.Search.SearchSystemIndex, Sitecore.Kernel" />
    <!-- other processors -->       

In Sitecore 8 these configurations doesn't exist.

Please comment these lines of code for a short fix. Please compare your config files with config files from a clean Sitecore solution which has same release with your version.

| improve this answer | |
  • Thanks for your suggestion. By doing what is suggested above, the error vanished but the search is not happening. For every search even if item is present in content tree, it show message as "There is no Match" – Pushpendra Vats Mar 5 '18 at 18:40
  • Like i said in answer, please compare config files with a clean instalation, looks like your config files were not upgraded correctly – Vlad Iobagiu Mar 5 '18 at 19:11
  • Thanks for your support. The search is happening now. Only changes I had done is commented the tag mentioned by you in web.config – Pushpendra Vats Mar 6 '18 at 11:40
  • please mark the answer as correct if it solved your issue – Vlad Iobagiu Mar 6 '18 at 11:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.