tag:blogger.com,1999:blog-8451123064758809734.post4608769577258136794..comments2008-11-14T09:58:10.897-08:00Tyler Holmeshttp://www.blogger.com/profile/17433652947830098796noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8451123064758809734.post-32911914406226078052008-11-14T09:58:00.000-08:002008-11-14T09:58:00.000-08:00Depending on the timing this could definitely be the case. The sure fire bet is to stop the timer service and then reset IIS. After that, you should be good until you start the timer service again and it breaks IIS...this may happen immediately or only after a while (as long as weeks in some cases I've seen). Unfortunately on some machines it's intermittent and you never know how soon it will be until it rears it's head again. <BR/><BR/>That's one reason why if you can limp along I would suggest doing so until the fix is out of "hotfix" status. <BR/><BR/>The only consistent elements I've seen are the error codes/descriptions and the behavior from the IIS Console.Tyler Holmeshttp://www.blogger.com/profile/16288716879251803370noreply@blogger.comtag:blogger.com,1999:blog-8451123064758809734.post-26694454208771451012008-11-14T05:24:00.000-08:002008-11-14T05:24:00.000-08:00In my experience iisreset has not resolved the problem. Instead, I've had to restart the timer service itself.Matthew Chestnuthttp://www.blogger.com/profile/09009366947080442726noreply@blogger.com