Fixing the Name of your sitecore_testing_index and sitecore_suggested_test_index Indexes July 21, 2020
AzureSitecoreSitecore 9Solr
0 Comment

I was combing through our log files this afternoon and came across the following errors filling the sucker up:

21044 16:31:43 ERROR ActionRunner: Execution is failed.
Exception: SolrNet.Exceptions.SolrConnectionException
Message: <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 404 Not Found</title>
</head>
<body><h2>HTTP ERROR 404</h2>
<p>Problem accessing /solr/Sitecore-sitecore_testing_index/schema. Reason:
<pre>    Not Found</pre></p>
</body>
</html>

Source: SolrNet
   at SolrNet.Impl.SolrConnection.Get(String relativeUrl, IEnumerable`1 parameters)
   at Sitecore.ContentSearch.SolrNetExtension.Impl.SolrBasicServerEx`1.GetManagedSchema()
   at Sitecore.ContentSearch.SolrProvider.Schema.DefaultSolrIndexSchemaClient`1.RequestSchema(String coreName)
   at Sitecore.ContentSearch.SolrProvider.SolrSearchIndex.RefreshSchema()
   at Sitecore.ContentSearch.SolrProvider.SolrSearchIndex.InitializeFromService()
   at Sitecore.ContentSearch.SolrProvider.Initialization.DefaultSolrSearchIndexesInitializer.<>c__DisplayClass16_0.<InitializeIndexes>b__0(SolrSearchIndex index)
   at Sitecore.ContentSearch.Maintenance.ActionRunner`1.ExecuteSafe(TItem item, Action`1 itemAction)

Nested Exception

Exception: System.Net.WebException
Message: The remote server returned an error: (404) Not Found.
Source: System
   at System.Net.HttpWebRequest.GetResponse()
   at HttpWebAdapters.Adapters.HttpWebRequestAdapter.GetResponse()
   at SolrNet.Impl.SolrConnection.GetResponse(IHttpWebRequest request)
   at SolrNet.Impl.SolrConnection.Get(String relativeUrl, IEnumerable`1 parameters)

The key line in the error was “Problem accessing /solr/Sitecore-sitecore_testing_index/schema”. That sure as heck doesn’t look like an index name I’ve ever heard of. Of course it isn’t a valid index name. Sitecore, for their credit, does have a KB out that addresses the issue, but in an “UnSitecore” way. Their approach is to modify the config file directly and update the name. Mmmmm let’s do it the way we know how, ok?

KEEP CALM AND Stick to the Script Poster | ct | Keep Calm-o-Matic
We got this!

The following config file can be dropped into your App_Config\Include folder and it should fix this Right as Rain:

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" xmlns:set="http://www.sitecore.net/xmlconfig/set/">
  <sitecore>
    <contentSearch>
      <configuration>
        <indexes>
          <index id="sitecore_suggested_test_index">
            <param  desc="core" patch:instead="param[@desc='core']">$(id)</param>
          </index>
          <index id="sitecore_testing_index">
            <param  desc="core" patch:instead="param[@desc='core']">$(id)</param>
          </index>
        </indexes>
      </configuration>
    </contentSearch>
  </sitecore>
</configuration>

After that, no more errors!