Hi!

Lately, I’ve read about several issues with TFS management, considering TFS 2010 Beta 2 and SharePoint. As claimed Brian Harry, there’s been a problem with SharePoint log files reported by several users. The problem is that log files clog up memory which leads to errors. Joe Rogers, a SharePoint specialist has suggested the way to manage the issue by cleaning up the configuration cache of the server having issues. Here are the steps to follow:

• You need to stop the OWSTIMER service on ALL of the MOSS servers in the farm.
  On the Index server, navigate to:
  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.
• Delete all the .XML files (not the .INI files, it’s important) in the directory
• Open the cache.ini with Notepad and reset the number to 1. Save and close the file.
• Start the OWSTIMER service on the Index server and wait for XML files to begin to reappear in the directory.
• After you see XML files appearing on the Index server, repeat steps 2, 3 & 4 on each query server, waiting for XML files to appear before moving to subsequent servers.
• After all of the query servers have all been cleared and new .xml files have been generated, proceed to the WFE and Application servers in the farm, following steps 2, 3, 4 and 5 for each remaining server.

Now, we all understand, it’s a beta, and it remains beta even being “go-live”. There’ve already been lots of things improved about VSTS and TFS, and the guys seem to be eager for more improvements. Anyway, Beta 2 survey, enabled to collect feedbacks about TFS 2010 Beta 2 is available, so any user may share their opinion about the release, or pay attention to occurring issues. You may go and check at Brian Harry’s.