Owstimer exe high cpu

Reproduce the error, get the correlation id and filter the log by it. Look for the Unexpected or Critical Level events. These are the errors that have occurred. This will give you the idea of what actual error you are facing. You can also go to Central Admin and check out the timer job status page and see if you've got any jobs that are failing repeatedly around the time of the memory usage or looping all the time.

Graham, all though it is a good idea to do so, it is nearly impossible to reach any page within sharepoint at that moment. It takes up to 15 minutes to load the homepage You need to stop the SPTimer Service first.

After that you can use the uls. Add a comment. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Improve this question. Eric Alexander Sepaka Sepaka 2 2 gold badges 12 12 silver badges 25 25 bronze badges. Is it a custom workflow using VS? Do you have custom timer jobs? I developed it using VS Do you have any idea what might be the issue? The timer service actually runs the workflows, and if you have some leaky code, it'll flood your basement.

Not disposing it to code — Sepaka. Add a comment. Active Oldest Votes. Improve this answer. Dave Wise Dave Wise How were you able to determine when the XML duplication was happening? Thanks Ronx. Does this apply to SharePoint or is it only for wss? I ran this script: [System. GetType -eq [Microsoft. Hope that helps! My first instinct was to kill the process and by default, Windows will restart the process. My immediate thoughts were, this is most likely a once off and boy was I wrong!

After restarting the server a second time later that day, I ran into the same issue. Next area of investigation was analysing the SharePoint Logs fun, fun, fun … however, everything seemed to be in order there too.