Timer Job shocker (yes’ it’s still out there)

Was at a client’s place today and saw this for the first time in ages – IIS would not start, error ID’s 6398, 6482 and 7076 in the event log, emails not being sent, etc.

"Wait just a doggone minute, here – I am certain this was fixed in WSS SP1" – but even though the client was running a more recent version of WSS & MOSS than SP1, the issue still existed – and the errors and symptoms were exactly the same.

It turns out that there is another hotfix now available for this – but it’s not a part of SharePoint code, so it’s a separate one that needs to be applied if you are seeing any of these issues (in other words, it’s unlikely to be a part of WSS / MOSS SP2 due out in a couple of months).

Hotfix can be requested here – http://support.microsoft.com/kb/946517/en-us – Articles discussing the fact that the issue still exists can be found here and here… It only seems to occur in IIS 6, and is more likely to occur when you have more app pools running under the same account as the Timer service.

Now where’s the Change Request form…

Good luck 🙂

About Brad Saide

I'm a SharePoint consultant. I'm also slowly going bald, seem to have a permanent spare tyre around my waist and enjoy socialising with friends over a beer or 10. The last 2 may possibly be related. Started working with SharePoint when the first version was in limited beta release (participated in the Technology Adoption Program while at Woolworths) and have been committed to the adoption of the technology as a business enabler ever since.
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a comment