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

Post a Comment

Popular posts from this blog

First look at Sitecore XM Cloud: Part 4 - Creating a new Site

Image
 Once you have successfully create an environment, you can go ahead and create your first site. In order to create a new Site, you need to launch the Sitecore Launchpad by clicking on the "XM Cloud Launchpad": Click on "Sites" menu to create a new Site: Click on "Add your first website" button to start the wizard. I chose the "Basic Site" template: Enter a Site name and pick a language and click on "Create website" button. You will see the following screen while your Site is being created: Once the Site is created, you can edit it in Pages or Explorer using the context menu: Explorer view of the Site: 1. "Details" view of page. 2. "Content" view of page: Unfortunately, trying to load the new Site in pages gives "Unable to connect to remote server"
Read more

RESOLVED: Solr Exceptions - Document contains at least one immense term in field

If you implemented Solr with Sitecore using Solr 5.x, you may run into the following error when indexing extremely large content in string fields: org.apache.solr.common.SolrException: Exception writing document id <xxxuniqueid> to the index; possible analysis error. Caused by: java.lang.IllegalArgumentException: Document contains at least one immense term in field="<xxxfieldname>" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[10, 9, 9, 10, 32, 32, 32, 32, 32, 32, 82, 84, 82, 83, 32, 70, 97, 99, 105, 108, 105, 116, 121, 32, 10, 32, 32, 32, 32, 84]...', original message: bytes can be at most 32766 in length; got <intgreaterthan32766> Caused by: org.apache.lucene.util.BytesRefHash$MaxBytesLengthExceededException: bytes can be at most 32766 in length; got <intgreaterthan32766> This is due to the fa...
Read more

First look at Sitecore XM Cloud: Part 1 - Getting started with Sitecore Cloud Portal and XM Cloud Deploy

Image
The biggest news of the year in the Sitecore community has been the arrival of Sitecore XM Cloud. In this blog series, I will be showing partner's access to XM Cloud. To get started, one needs to be invited to Sitecore Portal. You can access it at https://portal.sitecorecloud.io/.  Once you create an account and sign-in, you arrive at the following screen which has two main actions: Invite members  Managed projects (Sitecore XM Deploy) If you look closely you will see Sitecore Cloud Portal and XM Cloud Deploy. Invite team members opens up the following screen: "Manage My Projects" option launches the following window In the Part 2 , I will take us through deploying our first XM Cloud instance.
Read more