Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • It looks like the offending process is OWSTIMER.EXE, how can I delete a corrupt workflow? Commented Jun 20, 2012 at 19:23
  • 1
    The three times I've encountered this, it was relatively easy to identify the problematic workflow by simply asking the people who create workflows which ones they have modified in the past month or so. From there you need to go to the suspected list settings and stop and workflows in process and then delete the workflow from the list itself. After that, restart OWSTimer and give it about 5 minutes. If it is back to 100% CPU again then there is another corrupt workflow. Microsoft has some tools that can make it a bit easier to troubleshoot this so you might want to open a call with them. Commented Jun 20, 2012 at 20:02
  • You are a legend! Really appreciate it, the issue has been resolved. Commented Jun 22, 2012 at 12:48