Solr can't be configured after upgrade to 23.241.2

Original Question

or Issue:

Environment:

• Product - On-premise
• Version - 23.1.1
• Platform - Windows
• Application - Solr

Dedicated server for Solr

Defect or

Enhancement Number:

Solr.xml misconfiguration

Resolution or

Workaround:

Verify if the "solr.xml" file content present under the path: C:\xampp\solr\server\solr is the same as the following file? solr.xml

If they are different, please follow the steps:

• Override the old solr.xml file by this new one that is attached to this comment.

• After, please make a copy of customer Core (the one which contains the indexed data) and move it to a different folder, leaving Solr with no cores available.

• Once the cores are not present in the folder C:\xampp\solr\server\solr the customer can restart the server and configure again the core in the admin portal, making the tokenizer upgrade and configuring OCR (if the user had it enabled previously).

• With the core configured in the admin portal, we should copy back the backup core with the data to the path C:\xampp\solr\server\solr and proceed with the following steps:

  • Get the file solrconfig.xml from the new empty core configured. Should be in a path like C:\xampp\solr\server\solr\fccore\conf and replace it in the old core, that should have a path that looks like C:\xampp\solr\server\solr\backupcore\config
  • Repeat the same process for the file managed-schema.xml
  • After this delete the new core and rename the backup one to the same name as the other had. In the example here would be deleting "fccore" and renaming "backupcore" to "fccore".
  • With the backupcore renamed and with the fixed files inside it, you can restart the Content Search service again.