Re: IIS6 problems with ASP and ASP.NET

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Stefan Rodich (s.rodich_at_log-it-gmbh.de)
Date: 09/06/04 

Date: Mon, 6 Sep 2004 09:23:00 +0200

Hello Pat,

thank you for your help.

Best regards
Stefan

"Pat [MSFT]" <patfilot@online.microsoft.com> schrieb im Newsbeitrag
news:OUpyCJFkEHA.2412@TK2MSFTNGP10.phx.gbl...
> It looks like you are experiencing multiple problems.
>
> The first log shows a crash inside managed code. IISState did not dump
the
> managed stack (it has to 'guess' sometimes and doesn't always get it
right),
> but the managed stack can be recovered from the dump file.
>
> A later log clearly shows the Jet bug. There is a hotfix for that, but
you
> will need to contact MS-Support to get it (Q838306).
>
> To read the .dmp file yourself, you will need WinDBG from the debugger
pack
> (www.microsoft.com/ddk/debugging).
>
> Here's a previous post on the reading your own:
>
> >> >> To read your own .dmp file:
> >> >>
> >> >> Download and install WinDBG onto a workstation w/Internet access
> >> >>
> >> >> Create a directory called c:\symbols (or some other easily
remembered
> >> >> location)
> >> >>
> >> >> Copy the .dmp file to the workstation
> >> >>
> >> >> Open the .dmp file with WinDBG
> >> >>
> >> >> Type .symfix c:\symbols <enter>
> >> >>
> >> >> Type .reload <enter>
> >> >>
> >> >> Type ~20s <enter>
> >> >> -This will Set the debugger to thread 20 (where the crash happened)
> >> >>
> >> >> Type !.\clr10\sos.ClrStack <enter>
> >> >>
> >> >> That should dump the faulting stack.
> >> >>
> >> >> You can post the output to the group.
> >> >>
> >> >>
> >> >> Pat
>
>
>
>