fbpx

Company News

Clearing the SharePoint Configuration Cache

May 21, 2013

I’m grabbing most of this content from the following link, http://latenightsp.wordpress.com/2011/03/16/sharepoint-config-cache/, just in case the blog disappears at some point in the future – I don’t want this information to get lost.  So many thanks to Mayank Malik over at Late Night SharePoint.

Reblogged from Late Night SharePoint

  1. What is the SharePoint Configuration Cache?
    The cache has many names – system cache, SharePoint cache, configuration cache, the cache, that folder with XML files,… you get the drift. It really is a cache of farm’s configuration objects. There is a timer job called “Config Refresh” that updates the cache on SharePoint servers in the farm. Like any other cache, config cache becomes stale over time. Therefore, clearing the cache is needed to get all the SharePoint servers up to date on the latest farm information.
  2. How to clear the SharePoint Configuration Cache?
    a)     Stop the SharePoint 2010 Timer service on ALL of SharePoint servers in the farm.
    b)     Log into your Index server.
    c)     Navigate to the directory: C:\ProgramData\Microsoft\SharePoint\Config\GUID.
    d)     Delete all the XML files from the directory.
    CAUTION: DELETE ONLY THE .XML FILES, NOT THE .INI FILE. IF YOU DELETED THE .INI file, see item 3.
    e)     Open the cache.ini with Notepad and reset the number to 1. Save and close the file.
    f)      Start the SharePoint 2010 Timer service on the Index server and wait for XML files to reappear in the directory.
    g)     After you see XML files appearing, repeat steps c, d & e on each query server (one server at a  time).
    h)     After all of the query servers have all been cleared, repeat steps c, d & e on each of the WFE and application servers in the farm (one server at a time).
  3. I deleted the entire configuration cache directory. Now What?
    a)     To recreate the directory, you need to know the directory name (which is a GUID). You can find this GUID in the registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14\Secure\ConfigDB. Copy the GUID from Id attribute and create the new directory: C:\ProgramData\Microsoft\SharePoint\Config\GUID.
    b)     In the directory you just created, create another file called cache.INI. Open the file using Notepad and enter the number “1″ without the quotes. Save and close the file.
    c)     Start the SharePoint 2010 Timer service on the Index server and wait for XML files to reappear in the directory.

I especially like #3, because I’ve [shamefully] done that before, and now I know how to fix it.  Winking smile

4 Responses

  1. Vinay says:

    thanks to your post. i also did the same thing as #3. 🙂

  2. Salva says:

    I am making a script that automatically clear the cache.
    Can you confirm:
    I have made a backup of Cache.ini and replaced the number with 1 and saved it.
    Now, If a delete ALL content in my GUID folder and let my script copy my Cache.ini file back in the GUID folder I should be good, right?

    thanks

    • mmman says:

      That sounds right to me, yes. So long as you don’t delete the directory. Would be interesting to see what you produce.

Leave a Reply

Colin Phillips

itgroove Alumni

Colin Phillips

Subscribe via Email

Categories

Powered by...

itgroove Corporate Profile
Connect With Us