Project Server Help, FAQs, Blogs, and HowTos
This is The Header Then

Are your timer jobs inexplicably failing to complete?

posted January 24th, 2008 by Stephen Sanderlin
1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5 out of 5)
Loading ... Loading ...

I recently encountered a situation where I would see literally hundreds of errors in the ULS logs like this:

01/18/2008 10:22:59.99 OWSTIMER.EXE (0×0600) 0×08F8 Windows SharePoint Services Timer 5uuf Monitorable The previous instance of the timer job ‘Config Refresh’, id ‘{3F51D43C-C7DD-403D-A63B-1163EA9B46A6}’ for service ‘{2F8D95DC-ECBF-4661-83AD-92CA4162CD4E}’ is still running, so the current instance will be skipped. Consider increasing the interval between jobs.

Every single Timer Job Definition was throwing these errors (sometimes hundreds of them) every time it was invoked. There were no other errors in the Application Log or ULS Logs, even with verbosity cranked all the way up. Alerts weren’t going out, the cube build was failing, and literally everything that relied on a timer job was nonfunctional. Restarting the Timer service alleviated the problem temporarily, but it would inevitably come back after the first invocation of the timer job.

Discuss this post on the EPMFAQ Blog Posts Forum.

Related Posts

The opinions expressed on this site by the authors and those providing comments are theirs alone, and do not reflect the opinions of the respective employers of the authors or any employee thereof. Our respective employers are not responsible for the accuracy of any of the information supplied by on this site.

Terms of Use | Privacy Policy | Publishers

All content on this website is covered by the
Creative Commons Attribution-Share Alike 3.0 United States License.
Theme ©2007 The Heckerped WordPress Theme created by JTk of Doc5 under the Creative Commons Attribution License.