Bookmark and Share Karthik Murugesan
home | gallery | pbase | blog

« DCLauncher issues while configuring Document Conversion in MOSS 2007 | Main | SSP Creation stuck at Provisioning in Progress »

SharePoint Services Timer Service File System Cache

Reseting the file system cache have resolved many issues I had in my SharePoint farm. Microsoft tech support gave me this resolution to fix some issues I had with Usage Analysis. I perform this operation fisrt if I get stuck with any issues related to timer jobs. Good times!

So, how to clear the file system cache?

File system cache should be cleared on all servers in the server farm on which the Windows SharePoint Services Timer service is running. To do this, follow these steps:

1. Stop the Timer service.
To do this, follow these steps:
a. Click Start, point to Administrative Tools, and then click Services.
b. Right-click Windows SharePoint Services Timer, and then click Stop.
 
2. Delete or move the contents of the following folder:
a. %ALLUSERSPROFILE% \Application Data\Microsoft\SharePoint\Config\GUID
b. Leave the cache.ini alone
c. Delete all other files (all guid.xml) these are all timer job definitions
d. Open cache.ini in notepad and change whatever number you see there to 0


3. Start the Timer service:
To do this, follow these steps:
a. Click Start, point to Administrative Tools, and then click Services.
b. Right-click Windows SharePoint Services Timer, and then click Start.
 
Note: The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm on which the Timer service is running.

Go back to the %ALLUSERSPROFILE% \Application Data\Microsoft\SharePoint\Config\GUID folder and make sure you see a bunch of xml files.

Open the cache.ini and see if the 0 is replaced by a higher value.

You have just synched all your servers with the same timer job definitions from the config db.

TrackBack

TrackBack URL for this entry:
http://camantrix.com/blog-mt/mt-tb.fcgi/25

Comments

Thanks! I was having the same problem while provisioning a new SSP!!!!

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)