Since the windows update yesterday on Win2003 Server, I found a W3WP.EXE
process using 99% of the CPU and the site needed to be reset. Anyone else
find this? I think Microsoft has a bug, but if there is something else I
should look at, someone please let me know.
They've had this type of bug before. See
http://support.microsoft.com/kb/900243
On Aug 15, 8:41 pm, "K. Abit"
> Since the windows update yesterday on Win2003 Server, I found a W3WP.EXE
> process using 99% of the CPU and the site needed to be reset. Anyone else
> find this? I think Microsoft has a bug, but if there is something else I
> should look at, someone please let me know.
>
> They've had this type of bug before. Seehttp://support.microsoft.com/kb/900243
I doubt Windows Update would introduce a bug like that because Windows
does not come with any built-in Web Applications.
You need to start with what web applications are running on your
server that could be using the CPU. The KB you found is an example of
an application with a bug in an web application running on top of
Windows, which does not support your claim that Microsoft has a bug
introduced by Windows update that results in 100% CPU.
It is certainly useless to try to assign blame before troubleshooting
the issue. At least 90% of all reported issues on IIS are caused by
the users or their applications. This means that for every KB you see,
there are 9 other issues UNDOCUMENTED by any KB because they are
issues in user applications.
So, is it reasonable to focus on the KB just because the nine others
are not documented? Hardly.
I realize that some of these numbers and perceptions are completely
unknown to most users, but when you want to vent or accuse, you better
have your details straight.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
"David Wang"
news:1187252827.891576.76270@i13g2000prf.googlegroups.com...
> On Aug 15, 8:41 pm, "K. Abit"
>> Since the windows update yesterday on Win2003 Server, I found a W3WP.EXE
>> process using 99% of the CPU and the site needed to be reset. Anyone
>> else
>> find this? I think Microsoft has a bug, but if there is something else I
>> should look at, someone please let me know.
>>
>> They've had this type of bug before.
>> Seehttp://support.microsoft.com/kb/900243
>
>
> I doubt Windows Update would introduce a bug like that because Windows
> does not come with any built-in Web Applications.
>
> You need to start with what web applications are running on your
> server that could be using the CPU. The KB you found is an example of
> an application with a bug in an web application running on top of
> Windows, which does not support your claim that Microsoft has a bug
> introduced by Windows update that results in 100% CPU.
>
> It is certainly useless to try to assign blame before troubleshooting
> the issue. At least 90% of all reported issues on IIS are caused by
> the users or their applications. This means that for every KB you see,
> there are 9 other issues UNDOCUMENTED by any KB because they are
> issues in user applications.
>
> So, is it reasonable to focus on the KB just because the nine others
> are not documented? Hardly.
>
> I realize that some of these numbers and perceptions are completely
> unknown to most users, but when you want to vent or accuse, you better
> have your details straight.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
I hardly vented or accused. Re-read what I wrote.
And Windows Updates does update IIS components, and just 6 to 12 months ago
we saw another WU which actually created a slowness problem in websites, and
that patch was subsequently re-released a few days later with full
acknowledgement that the original patch had a bug.
I am keeping an open mind but as you said, I'd be foolish not to consider
all possibilities, including a WU bug, and that is why I'm posting here (to
see if anyone else experiences the same).
On Aug 16, 8:27 am, "K. Abit"
> "David Wang"
>
> news:1187252827.891576.76270@i13g2000prf.googlegroups.com...
>
>
>
>
>
> > On Aug 15, 8:41 pm, "K. Abit"
> >> Since the windows update yesterday on Win2003 Server, I found a W3WP.EXE
> >> process using 99% of the CPU and the site needed to be reset. Anyone
> >> else
> >> find this? I think Microsoft has a bug, but if there is something else I
> >> should look at, someone please let me know.
>
> >> They've had this type of bug before.
> >> Seehttp://support.microsoft.com/kb/900243
>
> > I doubt Windows Update would introduce a bug like that because Windows
> > does not come with any built-in Web Applications.
>
> > You need to start with what web applications are running on your
> > server that could be using the CPU. The KB you found is an example of
> > an application with a bug in an web application running on top of
> > Windows, which does not support your claim that Microsoft has a bug
> > introduced by Windows update that results in 100% CPU.
>
> > It is certainly useless to try to assign blame before troubleshooting
> > the issue. At least 90% of all reported issues on IIS are caused by
> > the users or their applications. This means that for every KB you see,
> > there are 9 other issues UNDOCUMENTED by any KB because they are
> > issues in user applications.
>
> > So, is it reasonable to focus on the KB just because the nine others
> > are not documented? Hardly.
>
> > I realize that some of these numbers and perceptions are completely
> > unknown to most users, but when you want to vent or accuse, you better
> > have your details straight.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //
>
> I hardly vented or accused. Re-read what I wrote.
>
> And Windows Updates does update IIS components, and just 6 to 12 months ago
> we saw another WU which actually created a slowness problem in websites, and
> that patch was subsequently re-released a few days later with full
> acknowledgement that the original patch had a bug.
>
> I am keeping an open mind but as you said, I'd be foolish not to consider
> all possibilities, including a WU bug, and that is why I'm posting here (to
> see if anyone else experiences the same).- Hide quoted text -
>
> - Show quoted text -
Run DebugDiag on the process the next time you see the 100% CPU and
post its report.
http://blogs.msdn.com/david.wang/archive/2005/12/31/HOWTO_Ba sics_of_IIS6_Troubleshooting.aspx
I realize from your perspective it looks like exactly what you
describe, but your symptoms are so generic that one can hardly make
the logical connection that this issue is related to Windows Update.
You are simply projecting your assumptions onto someone else's search
for "W3WP.EXE using all CPU" and then making them suspect Windows
Update.
After all, it is but one of an infinite number of possibilities. But
since it is a well-named one, people assume it is the cause. That is
why it is "accusing".
The problem here is that we are all human and humans are not perfect,
yet we continue to expect perfection. It is the same psychology
against Doctors, Lawyers. It is the same psychology with patches.
People only remember the one single patch failure and discount the
millions of success, and they ignore the billions of self-inflicted
failures from their own custom applications.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//