IIs Worker Process encountered a problem and needed to close defned <denfed[ at ]gmail.com> 5/14/2007 1:58:39 PM I am getting the same error on a Windows 2003 server. Happens on a reboot when logging in. Other than that WSUS seems to work fine.

Re: IIs Worker Process encountered a problem and needed to close "Ed" <no.spam[ at ]nospam.com> 5/15/2007 10:58:30 AM Yes, I can confirm this as well. This is with a clean install of WSUS 3.0 on Windows Server 2003 R2 Standard x64 - SP1 Ed "defned" <denfed[ at ]gmail.com> wrote in message news:1179151119.118677.266960[ at ]q75g2000hsh.googlegroups.com... [Quoted Text] >I am getting the same error on a Windows 2003 server. Happens on a > reboot when logging in. Other than that WSUS seems to work fine. >

Re: IIs Worker Process encountered a problem and needed to close "Cecils\(MSFT\)" <cecils[ at ]online.microsoft.com> 5/15/2007 9:19:26 PM If this appears to happen on a fairly regular, roughly 29 hour, cycle then have a look at this article (http://support.microsoft.com/kb/918041/en-us) for a potential work-around. We have seen this in very random situations. If someone has this happening on a regular basis, please attach a copy of your latest IIS logs. Thanks -- Cecil [MSFT] Deployment, WSUS Microsoft This posting is provided "As Is" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "defned" <denfed[ at ]gmail.com> wrote in message news:1179151119.118677.266960[ at ]q75g2000hsh.googlegroups.com... [Quoted Text] >I am getting the same error on a Windows 2003 server. Happens on a > reboot when logging in. Other than that WSUS seems to work fine. >

Re: IIs Worker Process encountered a problem and needed to close "Ed" <no.spam[ at ]nospam.com> 5/16/2007 8:40:39 AM Hi Cecil, Yes, I can confirm this "29 hour" sequence. This probably is related to the "Recycle worker processes (in minutes)" setting? We did follow the Method 3 from KB918041 (because it is a domain controller), so now we have to wait for 29 hours to see the result. In the meantime, I am willing to send you the latest IIS logs (not in this newsgroup, but I can send them directly by E-mail). Exactly which logs do you need? Regards, Ed "Cecils(MSFT)" <cecils[ at ]online.microsoft.com> wrote in message news:OcGR4azlHHA.3736[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > If this appears to happen on a fairly regular, roughly 29 hour, cycle then > have a look at this article (http://support.microsoft.com/kb/918041/en-us) > for a potential work-around. We have seen this in very random situations. > If someone has this happening on a regular basis, please attach a copy of > your latest IIS logs. > > Thanks > -- > Cecil [MSFT] > Deployment, WSUS > Microsoft > > This posting is provided "As Is" with no warranties, and confers no > rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm > > "defned" <denfed[ at ]gmail.com> wrote in message > news:1179151119.118677.266960[ at ]q75g2000hsh.googlegroups.com... >>I am getting the same error on a Windows 2003 server. Happens on a >> reboot when logging in. Other than that WSUS seems to work fine. >> >

Re: IIs Worker Process encountered a problem and needed to close "Ed" <no.spam[ at ]nospam.com> 5/23/2007 8:23:44 AM I can now confirm that the Method 3 solution of KB918041 did solve this problem for us. Regards, Ed "Ed" <no.spam[ at ]nospam.com> wrote in message news:uIp7lX5lHHA.1624[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] > Hi Cecil, > > Yes, I can confirm this "29 hour" sequence. This probably is related to > the "Recycle worker processes (in minutes)" setting? > We did follow the Method 3 from KB918041 (because it is a domain > controller), so now we have to wait for 29 hours to see the result. > In the meantime, I am willing to send you the latest IIS logs (not in this > newsgroup, but I can send them directly by E-mail). Exactly which logs do > you need? > > Regards, > > Ed > > "Cecils(MSFT)" <cecils[ at ]online.microsoft.com> wrote in message > news:OcGR4azlHHA.3736[ at ]TK2MSFTNGP03.phx.gbl... >> If this appears to happen on a fairly regular, roughly 29 hour, cycle >> then have a look at this article >> (http://support.microsoft.com/kb/918041/en-us) for a potential >> work-around. We have seen this in very random situations. If someone has >> this happening on a regular basis, please attach a copy of your latest >> IIS logs. >> >> Thanks >> -- >> Cecil [MSFT] >> Deployment, WSUS >> Microsoft >>