Tom -
Thanks for the quick response - but I don't think any of
those articles are relevant. I'm not throwing friendly
HTTP errors, and I'm running ASPX pages, not ASP. In
fact, ASP and HTML files run just fine.
Specifically, I'm doing .NET development with most of the
generation being done in a presentation layer hooked in
to the behind code of the .ASPX pages. Most importantly,
everything runs fine until I apply the latest IE6
cummulative patch (822925) - after I apply it, I get the
500 error and nothing else.
Since this patch is so new, I figured someone else
might've encountered the issue. I've uninstalled it, and
can continue working; I guess I'll have to dig deeper
into what, precisely, the patch is changing (most obvious
culprit being the security model) that would cause my web
application to force IIS to throw the 500 error.
>-----Original Message-----
>"Jonathan A. Hochberg" <jah.DeleteThis@cbord.com> wrote in message
>news:031e01c368e0$1d0ba010$a301280a@phx.gbl...
>> I've done the install and uninstall of 822925 a couple
of
>> times now, and have determined that a patched Windows
XP
>> Professional used for web application development
throws
>> a 500 error in IIS GET process.
>>
>> Anyone else seen this? Ideas as to cause/solution?
>
>FAQ. Start here:
>http://www.aspfaq.com/show.asp?id=2109
>http://support.microsoft.com/?id=311766
>http://support.microsoft.com/?id=309051
>
>--
>Tom Kaminski IIS MVP
>http://www.iistoolshed.com/ - tools, scripts, and
utilities for running IIS
>http://mvp.support.microsoft.com/
>http://www.microsoft.com/windowsserver2003/community/cent
ers/iis/
>
>
>
>.
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: IIS 500 error on aspx pages after q822925.exe