Our Great Posts

If you are seeing numerous errors in the Crawl logs, one step you may want to try is clearing the configuration cache. Here are two very good articles about this:

1. How To Reset a Corrupt Search Index in SharePoint 2013 in Case the Reset Index is not Working

– This article provides step-by-step directions on how to clear the configuration cache. These instructions are useful anytime you need to clear the configuration cache, not just when the reset index is not working.

2. What is the Configuration Cache?

– This article explains what the configuration cache is and how it works. If you are like me, you will probably want to know why you’d want to clear the configuration cache in the first place. This article provides very good background information.

In this blog post, I will explain how I cleared the configuration cache using the instructions in the first article above. I’ve added to these instructions as the Farm I was using had multiple servers.

Clearing the Configuration Cache

1. Remote into each of the SharePoint servers.

On each server:

2. Run services.msc. Find SharePoint Timer service, as you will need to stop it shortly.

Note that I do not stop the timer until I absolutely have to, in order to minimize down time.

3. Navigate to C:\ProgramData\Microsoft\SharePoint\Config. Do a “find” on cache.ini file in the Config folders. Open the location of cache.ini so you are seeing the folder where it is stored.

4. Back up the folder containing cache.ini on all four servers. Note the location where you backed up the folders.

I used the same location on all the servers, i.e., D:\Backup.

5. Stop the SharePoint timer on all the servers.

6. Delete all XML files inside the GUID folder (the one you backed up). Do NOT delete the GUID folder itself or the Cache.ini file inside the GUID folder.

7. Open up each cache file. Delete the content, replacing all the text with the number ‘1’. Save and close the file.

(I noted the original values, just in case I needed them. Example: 1940315)

8. Start the timer service on all the servers.

9. Open Central Administration and also the main web portal, just to make sure SharePoint is working as expected.

10. Open the cache.ini file and make sure there is some number in it other than “1,” example: 1940351.

At this point, you are finished clearing the configuration cache.

Check the search / crawl logs to see if clearing the configuration cache resolved the problem.


Leave a Reply