Problem: One of our environments was not running timer jobs and had 17 timer jobs in a status of "paused".
Initial Hypothesis: I replicated the pause timer jobs on a dev machine. I removed the cache and the paused jobs were still present. Performing a PSConfig fixed the timer job issue but broke my User Profile Service (UPS). So not a viable fix.
Resolution: One of the engineers worked out that another engineer had played with the OWSTIMER.EXE configuration had been changed and once corrected, the time jobs flushed themselves out.
Initial Hypothesis: I replicated the pause timer jobs on a dev machine. I removed the cache and the paused jobs were still present. Performing a PSConfig fixed the timer job issue but broke my User Profile Service (UPS). So not a viable fix.
Resolution: One of the engineers worked out that another engineer had played with the OWSTIMER.EXE configuration had been changed and once corrected, the time jobs flushed themselves out.
0 comments:
Post a Comment