OWSTimer Increasing Memory Usage >> No Errors
I recently installed and configured our a SharePoint 2007 SP2 environment, as I have done many times before. However, for some reason the OWSTimer continues to increase in memory usage and within 3-4 days it is requiring up to 1.5 - 1.8 GBs of memory.No errors are thrown, all jobs are successful in central admin, the credentials are correct on the Timer service, started happening oob (before any custom code implementation) ** Only error is a deadlock when the OWSTimer has reached 1.5 - 1.8 GBs because simply the Admin job can't runI searched all over this site as well as searched other locations on the web and haven't found anything that has helped, or reasons this might have happened. Any suggestions on where start looking or what I can try would be great.Here are the server specs:* Virtual (not an option to change this)* Windows Server 2003 SP2 x64* 4 GB of RAM* 2 CPUSharePoint specs:* SharePoint 2007 SP2 >> 12.0.0.6421* Indexer Performance = Reduced* Database on Separate Server
February 17th, 2010 1:23am

Hi junioratm, Did you try IIS reset and computer reboot? For virtualizing SharePoint Server 2007, I suggest you read the article below: http://blogs.msdn.com/uksharepoint/archive/2009/03/04/topic-1-recommendations-for-optimizing-the-performance-of-a-virtualized-sharepoint-environment.aspx There are many different causes of this issue. You can try to create a new search database as sometimes it may cause the owstimer taking high memory. Do you use IIS 6.0? If so, please refer to KB 887696 http://support.microsoft.com/default.aspx/kb/887696/en-us Stefan has concluded some common issue related to memory leak, please read it: http://blogs.technet.com/stefan_gossner/archive/2007/11/26/dealing-with-memory-pressure-problems-in-moss-wss.aspx For more information, pelase refer to: http://blogs.msdn.com/steveshe/archive/2007/12/18/overlapped-recycling-and-sharepoint-memory-based-recycling.aspx http://support.microsoft.com/kb/938276 Hope this helps. Lu Zou
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2010 11:38am

Hi Lu Zou,Thanks for the information. I took a look at it and here is what I have done and the results: 1) The server has been rebooted multiple times and I have made sure it has the latest and greatest updates from Microsoft. 2) Restarting IIS didn't affect the OWSTimer memory usage. I actually have to manually stop/start the WSS Timer service in order for it to release the memory. 3) I looked over the IIS KB you mentioned, 887696, but it said that this issue was corrected in W2K3 SP2, which we have on the server, so unfortunately I don't think that will help. 4) We only have one custom SharePoint solution on the server which has all the SPWeb and SPSite objects being disposed of properly and I can't seem to find where a memory leak would come from that would affect the WSS Timer service since the everything else is part of the OOB SharePoint installation. 5) I have created new a new WSS Help Search DB and I have completely over-hauled the SSP and created new DBs for it, including a new Search DB. Once that was comlpeted I stopped/started the WSS Timer service (which reset the OWSTimer memory usage) and ran a full crawl. However, after re-creating the Search Databases (rebuilding the SSP) I left it alone over the weekend. Unfortunately the OWSTimer process has once again crept up to using 1+ GB of RAM. For all our other SharePoint servers this process seems to hover around 100 - 200 MBs.I don't know if I missed something in the other articles you sent, but if there is anything else you can think of to look at (try), please let me know. The only other option I can fathom is to create a timer job to restart the WSS Timer service on a nightly basis, but that is a hack, not a fix so trying to hold off on that for now.Thanks!Justin
February 22nd, 2010 6:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics