I think most of you have heard about the SharePoint Cache. This is a directory full of cached objects, wrapped in XML. Sometimes this cache can become corrupted. Usually you can face problems when developing Timer Jobs for SharePoint. These definitions use this cache, so keep in mind every time you deploy new versions of the assemblies; we have to clear the cache.
Another example is sometimes you see some odd errors occurring when we change settings in SharePoint Server 2007, such as when we try to modify an alternate access mapping. We have a KB article also http://support.microsoft.com/kb/939308. Sometimes we might notice some issues when changing settings concerning search. A work around seems to be clearing the SharePoint configuration cache. The configuration cache is where we cache configuration information on each server in the farm. Caching the data on each server prevents us from having to make SQL calls to pull this information from the configuration database. Sometime this data can become corrupted and needs to be cleared out and recreated. If we have issues with a single server, clear the config cache on that server, we do not need to clear the cache on the entire farm. To do a single server, follow the steps below on just the problem server.
Server 2003 location: Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID and delete all the XML files from the directory.
Server 2008 location: Drive:\ProgramData\Microsoft\SharePoint\Config\GUID and delete all the XML files from the directory.
Please note: ONLY THE XML FILES, NOT THE .INI FILE.
You need to be a premium member to use this feature. To access it, you'll have to upgrade your membership.
Become a sharper developer and jumpstart your career.
$0
$
. 00
monthly
For Basic members:
$20
For Premium members:
$45
For Elite members: