RESOLVED: Connection error to search provider [Solr] : Unable to connect to , Core: [index_name]

If you are working with Solr provider for Sitecore 8, I'm sure you have already read this article regarding changes to the Schema.xml that must be applied.

In a recent Solr integration with Sitecore 8 Update 5 (rev. 150812), I ran into the following error(s):

Connection error to search provider [Solr] : Unable to connect to <solr service address>, Core: [index_name]

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Sitecore.ContentSearch.Exceptions.SearchProviderConnectionException: Connection error to search provider [Solr] : Unable to connect to [http://ocomp-sc-solr:8080/solr], Core: [social_messages_master]

Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SearchProviderConnectionException: Connection error to search provider [Solr] : Unable to connect to <address> , Core: <index_name>
   Sitecore.ContentSearch.SolrProvider.SolrSearchIndex.Initialize() +1165
   Sitecore.ContentSearch.SolrProvider.SolrContentSearchManager.Initialize() +168
   Sitecore.ContentSearch.SolrProvider.CastleWindsorIntegration.WindsorSolrStartUp.Initialize() +866

[HttpException (0x80004005): Connection error to search provider [Solr] : Unable to connect to <address> , Core: <index_name>
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12601645
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475

[HttpException (0x80004005): Connection error to search provider [Solr] : Unable to connect to  <address> , Core: <index_name>
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12618692
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12458309


Apparently, the default index configuration for Sitecore 8 update 5 (rev. 150812) there are several new indexes that have been configured and for each of them you need to configure a separate cores in your Solr instance.

Here are the indexes for which you need individual cores:

§  Core
§  Master
§  Web
§  Analytics
§  Testing
§  sitecore_suggested_test_index
§  sitecore_fxm_master_index
§  sitecore_fxm_web_index
§  sitecore_list_index
§  social_messages_master

§  social_messages_web

Another way around would be to change the following element in all Solr configs to have the same core name (maybe the good old itembuckets) instead of $(id):

<param desc="core">$(id)</param>

Solve: Add new cores in your Solr instance for each of index "id" found in http://sitecore.oconnells.com/sitecore/admin/showconfig.aspx

Comments

Popular posts from this blog

RESOLVED: Sitecore Solr provider error: Value cannot be null. Parameter name: fieldNameTranslator.

Solr Error: Plugin init failure for [schema.xml] fieldType "x": Error loading class 'solr.xfield'