This is the second posting I’ve put together regarding OWSTimer. In a previous post I had a client who simply pegged the timer by running a batch update against thousands of list items subsequently kicking off thousands of workflows. In a more recent encounter, one of my clients called me with the OWSTimer again going mad, but for a completely different reason. Problem OWSTimer.exe taking 100% CPU and/or creating Gigabyte sized log files. Solution Below are the steps...