Bize Ulaşın / Contact Us

SharePoint logo

SharePoint 2013 Index Reset Problem

I was getting warning sign for the index partition on one of our SharePoint 2013 Servers and experiencing SharePoint 2013 Index Reset Problem.

Services were up but crawling wasn’t working properly and our search driven pages were not working.

Full crawl didn’t help, I tried to index reset but it wasn’t able to complete the reset process, it stuck.

Restarted the SharePoint Server Search 15 service then started the index reset didn’t help, tried by restarting the Timer Service but it didn’t help as well. (But this could be solve your problem, try first.)

The procedure below helped me, hope it helps you too.

  1. Find the the folder named with a GUID which has cache.ini file under the C:\ProgramData\Microsoft\SharePoint\Config
  2. Stop SharePoint Server Search 15 and SharePoint Timer Services
  3. Backup the cache.ini file
  4. Delete all files except the cache.ini file
  5. Edit the cache.ini and make sure it has only 1
    Sp2013CacheIni
  6. Save and Close the file.
  7. Start SharePoint Server Search 15 and SharePoint Timer Services
  8. Start Index Reset from SharePoint Central Administration\Application Management\Manage Service Applications\SearchServiceApplication\Index Reset
  9. You will see your  C:\ProgramData\Microsoft\SharePoint\Config\YourGUID folder will be filled up new .xml files and your cache.ini file will be modified. Generally it ends up with the previous number. It was different in my case, probably due to unsuccessful attempts of resets and full crawls.
  10. Then wait, fingers crossed. It saved my day, hope saves yours too.

Then I started full crawl from Content Sources and it has crawled straight forward, I was able watch what was happening from SharePoint Central Administration\Application Management\Manage Service Applications\SearchServiceApplication\Crawl Log

Events I was getting:

Log Name: Microsoft-Office Server-Search/Operational
Source: Microsoft-Office Server-Search
Event ID: 28
Task Category: Common Processing
Level: Information
Description:
Component and System=Query1-6a39afa4-55db-4142-984c-75d06b9aaeaf, Correlation ID=2b230a9d-8e31-70aa-c8e4-c81fa272dd71, Tenant ID=00000000-0000-0000-0000-000000000000 Error code=0, Flow Name=Microsoft.SharePointSearchProviderFlow, Operator Name=ParserExecutor, Message=The processing of item fails with error Cannot plan query for index system SPfa792afb13bb. Index fragment ‘0’ has no available cells. Cell statuses: [Cell I.0.0 on node IndexComponent1: Cell status is set to ‘not available’ (cell out of sync or seeding)]
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=”Microsoft-Office Server-Search” Guid=”{6AA8A41D-229D-42E8-A45E-49DD4F7F6E09}” />
<EventID>28</EventID>
<Version>15</Version>
<Level>4</Level>
<Task>23</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime=”2015-05-26T11:40:12.924967000Z” />
<EventRecordID>60744</EventRecordID>
<Correlation ActivityID=”{2B230A9D-8E31-70AA-C8E4-C81FA272DD71}” />
<Execution ProcessID=”5720″ ThreadID=”7324″ />
<Channel>Microsoft-Office Server-Search/Operational</Channel>
</System>
<EventData>
<Data Name=”logSourceName”>Query1-6a39afa4-55db-4142-984c-75d06b9aaeaf</Data>
<Data Name=”correlationId”>2b230a9d-8e31-70aa-c8e4-c81fa272dd71</Data>
<Data Name=”tenantId”>00000000-0000-0000-0000-000000000000</Data>
<Data Name=”errorCode”>0</Data>
<Data Name=”flowName”>Microsoft.SharePointSearchProviderFlow</Data>
<Data Name=”operatorName”>ParserExecutor</Data>
<Data Name=”errorMessage”>Cannot plan query for index system SPfa792afb13bb. Index fragment ‘0’ has no available cells. Cell statuses: [Cell I.0.0 on node IndexComponent1: Cell status is set to ‘not available’ (cell out of sync or seeding)]</Data>
</EventData>
</Event>
Log Name: Microsoft-Office Server-Search/Operational
Source: Microsoft-Office Server-Search
Event ID: 45
Task Category: Index Lookup
Level: Error
Description:
Query1-6a39afa4-55db-4142-984c-75d06b9aaeaf: Index lookup failed to work since no active index cell was available.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=”Microsoft-Office Server-Search” Guid=”{6AA8A41D-229D-42E8-A45E-49DD4F7F6E09}” />
<EventID>45</EventID>
<Version>15</Version>
<Level>2</Level>
<Task>13</Task>
<Opcode>2</Opcode>
<Keywords>0x8000000000000000</Keywords>
<EventRecordID>60748</EventRecordID>
<Correlation ActivityID=”{2B230A9D-4E3D-70AA-C8E4-CDB1EA071EE2}” />
<Execution ProcessID=”5720″ ThreadID=”5168″ />
<Channel>Microsoft-Office Server-Search/Operational</Channel>
</System>
<EventData>
<Data Name=”string0″>Query1-6a39afa4-55db-4142-984c-75d06b9aaeaf</Data>
</EventData>
</Event>

 

One comment on “SharePoint 2013 Index Reset Problem

  1. on November 20, 2015
    Jorris says:

    Thanks, helped me out with the same problem.
    How did you start to reverse engineer the problem back to the Config folder? Did you check sharepoint assembly code with ilspy or something like that? This area is such a mystery.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">

*

Kontrol / Control * Time limit is exhausted. Please reload CAPTCHA.