If you have classic schema factory configured, then Solr will not write the schema.xml file out. So either something's strange with SiteCore or someone inadvertently hand-edited the schema. I suggest contacting the SiteCore people to see how it would get that way.
You should be able to shut Solr/SiteCore down, hand-edit all your schema.xml files to fix the problem and start things back up though. Best, Erick On Tue, May 23, 2017 at 5:08 AM, LAD, SAGAR <sagar....@capgemini.com> wrote: > Hi SOLR team, > > We are using SOLR 4.6.0 with sitecore CMS 7.2 . > > > > It is observed that search indexes and some time schema.xml file get > corrupted. Schema.xml field tag got extra forward slash and it result into > stopping of SOLR. > > We have “ <schemaFactory class="ClassicIndexSchemaFactory"/>” therefore > only manual update is allowed. > > > > Please guide us in this issue and let us know any detail required. > > > > > > Regards > > *_____________________________________________* > > [image: Email_CBE.gif]Sagar Lad | Capgemini Technology Services India > Limited | Pune > > Schlumberger, Sogeti India > > Main: +91 20 2760 1000 extn 2012331 <+91%2020%202760%201000> | Cell: +91 > 8983724089 <+91%2089837%2024089> +91 98 199 64738 > > www.capgemini.com > > *People matter, results count.* > > *_______________________________________________________________* > > [image: 50years] > > > > *Connect with Capgemini:* > [image: Picto_Blog] > <http://www.capgemini.com/insights-and-resources/blogs>[image: > Picto_Twitter] <http://www.twitter.com/capgemini>[image: Picto_Facebook] > <http://www.facebook.com/capgemini>[image: Picto_LinkedIn] > <http://www.linkedin.com/company/capgemini>[image: Picto_Slideshare] > <http://www.slideshare.net/capgemini>[image: Picto_YouTube] > <http://www.youtube.com/capgeminimedia> > > > > > > > > > > > > > > > > This message contains information that may be privileged or confidential > and is the property of the Capgemini Group. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, you > are not authorized to read, print, retain, copy, disseminate, distribute, > or use this message or any part thereof. If you receive this message in > error, please notify the sender immediately and delete all copies of this > message. >
