Apparently it was according to
<a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?kbid=827214." target="_blank">http://support.microsoft.com/default.aspx?kbid=827214.</a> It is weird how it
suddenly started showing up.
"Pat [MSFT]" <patfilot.TakeThisOut@online.microsoft.com> wrote in message
news:OrTnzxHmEHA.3632@TK2MSFTNGP09.phx.gbl...
> This is most likely a bug in the SMTP Service. Please contact MS-Support.
>
> Pat
>
> "Brian Hoyt" <hoyty.TakeThisOut@hoyty.com> wrote in message
> news:O5GdnS3sO8vWHdzcRVn-ow@speakeasy.net...
> > My server has been rock solid for years until 9/6/04. At that point IIS
> > just started crashing over and over. It seems to do it multiple (50+)
> > times
> > and then will work for 12 hours or so and start up again. Thanks for
any
> > pointers. Here is what came out of IISState:
> > ***********************
> > Starting new log output
> > IISState version 3.3.1
> >
> > Fri Sep 10 03:32:08 2004
> >
> > OS = Windows 2003 Server
> > Executable: inetinfo.exe
> > PID = 5920
> >
> > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > ***********************
> >
> >
> > IIS has crashed...
> > Beginning Analysis
> > DLL (!FunctionName) that failed:
> >
> >
> >
> >
> > Thread ID: 9
> > System Thread ID: 220
> > Kernel Time: 0:0:0.265
> > User Time: 0:0:0.171
> > Thread Type: Other
> > # ChildEBP RetAddr
> > WARNING: Frame IP not in any known module. Following frames may be
wrong.
> > 00 0176fed8 d7df9645 0xd4df9645
> > 01 d3df9645 00000000 0xd7df9645
> > Closing open log file C:\iisstate\output\IISState-5920.log
> > Opened log file 'C:\iisstate\output\IISState-5920.log'
> >
> > ***********************
> > Starting new log output
> > IISState version 3.3.1
> >
> > Fri Sep 10 03:32:08 2004
> >
> > OS = Windows 2003 Server
> > Executable: inetinfo.exe
> > PID = 5920
> >
> > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > ***********************
> >
> >
> >
> >
> > Thread ID: 0
> > System Thread ID: 16a8
> > Kernel Time: 0:0:0.0
> > User Time: 0:0:0.0
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 0006f9a8 77f4303b SharedUserData!SystemCallStub+0x4
> > 01 0006f9ac 77e4905d ntdll!NtReadFile+0xc
> > 02 0006fa14 77db51f1 kernel32!ReadFile+0x16c
> > 03 0006fa40 77db5297 ADVAPI32!ScGetPipeInput+0x28
> > 04 0006fab0 77dfa7f1 ADVAPI32!ScDispatcherLoop+0x4c
> > 05 0006fcec 01002655 ADVAPI32!StartServiceCtrlDispatcherA+0x91
> > 06 0006fe1c 010027ea inetinfo!StartDispatchTable+0x214
> > 07 0006ff44 01003160 inetinfo!main+0x104
> > 08 0006ffc0 77e4f38c inetinfo!mainCRTStartup+0x12f
> > 09 0006fff0 00000000 kernel32!BaseProcessStart+0x23
> >
> >
> >
> >
> > Thread ID: 1
> > System Thread ID: 20e8
> > Kernel Time: 0:0:0.0
> > User Time: 0:0:0.0
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 0083fe18 77f43741 SharedUserData!SystemCallStub+0x4
> > 01 0083fe1c 77e41817 ntdll!ZwWaitForSingleObject+0xc
> > 02 0083fe8c 77e4168f kernel32!WaitForSingleObjectEx+0xac
> > 03 0083fe9c 01002cf9 kernel32!WaitForSingleObject+0xf
> > 04 0083ffb8 77e4a990 inetinfo!W3SVCThreadEntry+0x3b
> > 05 0083ffec 00000000 kernel32!BaseThreadStart+0x34
> >
> >
> >
> >
> > Thread ID: 2
> > System Thread ID: 89c
> > Kernel Time: 0:0:0.46
> > User Time: 0:0:0.250
> >
> > I am running it again to see if anything different comes out.
> >
> >
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: IISState log