IIS 6 stops responding about once a day

I have a new server running Windows 2003 Server and IIS 6. There are two
active websites on the server. With the frequency of approximately once
every 20 or so hours the sites become inaccessible. The are no errors
in the Windows event log or in the IIS log files.

But if I visit one of the sites directly on the server itself it will
come up fine and from that point on the sites are accessible again. I
don't have to restart IIS or anything else.

I ran the Isstate utility against inetinfo.exe when its in the state
where the sites are inaccessible.

The iisstate log file follows.

Opened log file 'C:\iisstate\output\IISState-1832.log'

***********************
Starting new log output
IISState version 3.3.1

Tue Jan 31 10:42:09 2006

OS = Windows 2003 Server
Executable: inetinfo.exe
PID = 1832

Note: Thread times are formatted as HH:MM:SS.ms

***********************




Thread ID: 0
System Thread ID: c70
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0006f99c 7c821b84 ntdll!KiFastSystemCallRet
01 0006f9a0 77e41942 ntdll!NtReadFile+0xc
02 0006fa08 77f795ab kernel32!ReadFile+0x16c
03 0006fa34 77f7943c ADVAPI32!ScGetPipeInput+0x2a
04 0006faa8 77fb2ec9 ADVAPI32!ScDispatcherLoop+0x51
05 0006fcec 010027be ADVAPI32!StartServiceCtrlDispatcherA+0x93
06 0006fe1c 01002969 inetinfo!StartDispatchTable+0x277
07 0006ff44 0100339d inetinfo!main+0x117
08 0006ffc0 77e523cd inetinfo!mainCRTStartup+0x12f
09 0006fff0 00000000 kernel32!BaseProcessStart+0x23




Thread ID: 1
System Thread ID: bec
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0082fe14 7c822124 ntdll!KiFastSystemCallRet
01 0082fe18 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0082fe88 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0082fe9c 01002ebf kernel32!WaitForSingleObject+0x12
04 0082ffb8 77e66063 inetinfo!W3SVCThreadEntry+0x3d
05 0082ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 2
System Thread ID: bf0
Kernel Time: 0:0:0.31
User Time: 0:0:0.31
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0086fcb8 7c822124 ntdll!KiFastSystemCallRet
01 0086fcbc 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0086fd2c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0086fd40 649f26a4 kernel32!WaitForSingleObject+0x12
04 0086fd68 010024b3 iisadmin!ServiceEntry+0x28a
05 0086ffa4 77f79348 inetinfo!InetinfoStartService+0x2cc
06 0086ffb8 77e66063 ADVAPI32!ScSvcctrlThreadA+0x21
07 0086ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 3
System Thread ID: cd4
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00c3ff9c 7c821364 ntdll!KiFastSystemCallRet
01 00c3ffa0 7c81fe26 ntdll!NtDelayExecution+0xc
02 00c3ffb8 77e66063 ntdll!RtlpTimerThread+0x47
03 00c3ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 4
System Thread ID: ce8
Kernel Time: 0:0:0.0
User Time: 0:0:0.15
Thread Type: Other
# ChildEBP RetAddr
00 00c7ff70 7c821bf4 ntdll!KiFastSystemCallRet
01 00c7ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
02 00c7ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
03 00c7ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 5
System Thread ID: 6f8
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 00d4feac 7c822114 ntdll!KiFastSystemCallRet
01 00d4feb0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 00d4ff58 77e61075 kernel32!WaitForMultipleObjectsEx+0x11a
03 00d4ff74 56f951ef kernel32!WaitForMultipleObjects+0x18
04 00d4ffa0 56f96a06 COADMIN!NOTIFY_CONTEXT::GetNextContext+0x67
05 00d4ffb8 77e66063 COADMIN!NOTIFY_CONTEXT::NotifyThreadProc+0x5f
06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 6
System Thread ID: c50
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0178fcec 7c822114 ntdll!KiFastSystemCallRet
01 0178fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
02 0178ffb8 77e66063 ntdll!RtlpWaitThread+0x161
03 0178ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 7
System Thread ID: 72c
Kernel Time: 0:0:0.62
User Time: 0:0:0.62
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

No remote call being made

# ChildEBP RetAddr
00 016cfe18 7c821c54 ntdll!KiFastSystemCallRet
01 016cfe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
02 016cff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
03 016cff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
04 016cffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
05 016cffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
06 016cffec 00000000 kernel32!BaseThreadStart+0x34

*****

Dump name is formatted as: PID-Timestamp.dmp

Creating C:\iisstate\output\1832-1138725731.dmp - mini user dump

*****

Closing open log file C:\iisstate\output\IISState-1832.log

Ken
Tue Jan 31 20:58:32 CST 2006

You probably need to run this against the w3wp.exe process that is hosting
your web application/web site, not InetInfo.exe

Cheers
Ken

"kloodge" <kloodge@yahoo.com> wrote in message
news:YGODf.15338$jO.10047@tornado.texas.rr.com...
:I have a new server running Windows 2003 Server and IIS 6. There are two
: active websites on the server. With the frequency of approximately once
: every 20 or so hours the sites become inaccessible. The are no errors
: in the Windows event log or in the IIS log files.
:
: But if I visit one of the sites directly on the server itself it will
: come up fine and from that point on the sites are accessible again. I
: don't have to restart IIS or anything else.
:
: I ran the Isstate utility against inetinfo.exe when its in the state
: where the sites are inaccessible.
:
: The iisstate log file follows.
:
: Opened log file 'C:\iisstate\output\IISState-1832.log'
:
: ***********************
: Starting new log output
: IISState version 3.3.1
:
: Tue Jan 31 10:42:09 2006
:
: OS = Windows 2003 Server
: Executable: inetinfo.exe
: PID = 1832
:
: Note: Thread times are formatted as HH:MM:SS.ms
:
: ***********************
:
:
:
:
: Thread ID: 0
: System Thread ID: c70
: Kernel Time: 0:0:0.0
: User Time: 0:0:0.0
: Thread Type: Other
: # ChildEBP RetAddr
: 00 0006f99c 7c821b84 ntdll!KiFastSystemCallRet
: 01 0006f9a0 77e41942 ntdll!NtReadFile+0xc
: 02 0006fa08 77f795ab kernel32!ReadFile+0x16c
: 03 0006fa34 77f7943c ADVAPI32!ScGetPipeInput+0x2a
: 04 0006faa8 77fb2ec9 ADVAPI32!ScDispatcherLoop+0x51
: 05 0006fcec 010027be ADVAPI32!StartServiceCtrlDispatcherA+0x93
: 06 0006fe1c 01002969 inetinfo!StartDispatchTable+0x277
: 07 0006ff44 0100339d inetinfo!main+0x117
: 08 0006ffc0 77e523cd inetinfo!mainCRTStartup+0x12f
: 09 0006fff0 00000000 kernel32!BaseProcessStart+0x23
:
:
:
:
: Thread ID: 1
: System Thread ID: bec
: Kernel Time: 0:0:0.0
: User Time: 0:0:0.0
: Thread Status: Thread is in a WAIT state.
: Thread Type: Other
: # ChildEBP RetAddr
: 00 0082fe14 7c822124 ntdll!KiFastSystemCallRet
: 01 0082fe18 77e6baa8 ntdll!NtWaitForSingleObject+0xc
: 02 0082fe88 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
: 03 0082fe9c 01002ebf kernel32!WaitForSingleObject+0x12
: 04 0082ffb8 77e66063 inetinfo!W3SVCThreadEntry+0x3d
: 05 0082ffec 00000000 kernel32!BaseThreadStart+0x34
:
:
:
:
: Thread ID: 2
: System Thread ID: bf0
: Kernel Time: 0:0:0.31
: User Time: 0:0:0.31
: Thread Status: Thread is in a WAIT state.
: Thread Type: Other
: # ChildEBP RetAddr
: 00 0086fcb8 7c822124 ntdll!KiFastSystemCallRet
: 01 0086fcbc 77e6baa8 ntdll!NtWaitForSingleObject+0xc
: 02 0086fd2c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
: 03 0086fd40 649f26a4 kernel32!WaitForSingleObject+0x12
: 04 0086fd68 010024b3 iisadmin!ServiceEntry+0x28a
: 05 0086ffa4 77f79348 inetinfo!InetinfoStartService+0x2cc
: 06 0086ffb8 77e66063 ADVAPI32!ScSvcctrlThreadA+0x21
: 07 0086ffec 00000000 kernel32!BaseThreadStart+0x34
:
:
:
:
: Thread ID: 3
: System Thread ID: cd4
: Kernel Time: 0:0:0.0
: User Time: 0:0:0.0
: Thread Type: Other
: # ChildEBP RetAddr
: 00 00c3ff9c 7c821364 ntdll!KiFastSystemCallRet
: 01 00c3ffa0 7c81fe26 ntdll!NtDelayExecution+0xc
: 02 00c3ffb8 77e66063 ntdll!RtlpTimerThread+0x47
: 03 00c3ffec 00000000 kernel32!BaseThreadStart+0x34
:
:
:
:
: Thread ID: 4
: System Thread ID: ce8
: Kernel Time: 0:0:0.0
: User Time: 0:0:0.15
: Thread Type: Other
: # ChildEBP RetAddr
: 00 00c7ff70 7c821bf4 ntdll!KiFastSystemCallRet
: 01 00c7ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
: 02 00c7ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
: 03 00c7ffec 00000000 kernel32!BaseThreadStart+0x34
:
:
:
:
: Thread ID: 5
: System Thread ID: 6f8
: Kernel Time: 0:0:0.0
: User Time: 0:0:0.0
: Thread Status: Thread is in a WAIT state.
: Thread Type: Other
: # ChildEBP RetAddr
: 00 00d4feac 7c822114 ntdll!KiFastSystemCallRet
: 01 00d4feb0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
: 02 00d4ff58 77e61075 kernel32!WaitForMultipleObjectsEx+0x11a
: 03 00d4ff74 56f951ef kernel32!WaitForMultipleObjects+0x18
: 04 00d4ffa0 56f96a06 COADMIN!NOTIFY_CONTEXT::GetNextContext+0x67
: 05 00d4ffb8 77e66063 COADMIN!NOTIFY_CONTEXT::NotifyThreadProc+0x5f
: 06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34
:
:
:
:
: Thread ID: 6
: System Thread ID: c50
: Kernel Time: 0:0:0.0
: User Time: 0:0:0.0
: Thread Status: Thread is in a WAIT state.
: Thread Type: Other
: # ChildEBP RetAddr
: 00 0178fcec 7c822114 ntdll!KiFastSystemCallRet
: 01 0178fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
: 02 0178ffb8 77e66063 ntdll!RtlpWaitThread+0x161
: 03 0178ffec 00000000 kernel32!BaseThreadStart+0x34
:
:
:
:
: Thread ID: 7
: System Thread ID: 72c
: Kernel Time: 0:0:0.62
: User Time: 0:0:0.62
: Thread Type: Possible ASP page. Possible DCOM activity
: Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
: Continuing with other analysis.
:
: No remote call being made
:
: # ChildEBP RetAddr
: 00 016cfe18 7c821c54 ntdll!KiFastSystemCallRet
: 01 016cfe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
: 02 016cff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
: 03 016cff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
: 04 016cffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
: 05 016cffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
: 06 016cffec 00000000 kernel32!BaseThreadStart+0x34
:
: *****
:
: Dump name is formatted as: PID-Timestamp.dmp
:
: Creating C:\iisstate\output\1832-1138725731.dmp - mini user dump
:
: *****
:
: Closing open log file C:\iisstate\output\IISState-1832.log

David
Tue Jan 31 22:44:15 CST 2006

This sounds like an issue at the networking layer.

Your application pool did not crash nor become unavailable (you did not have
to restart anything), and you can access IIS just fine from the local
machine.

When the sites are not accessible, check if there are any w3wp.exe running,
and "netstat -ano" probably show that port 80 is listened on. And if you
make a local request to the server, a w3wp.exe should spin up.

If the above is true, it seems like you have something else halting network
traffic to the server itself, which is something outside of IIS. I'm not
certain why; maybe you have a daily network recycle or such "cleanup" taking
place?

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"kloodge" <kloodge@yahoo.com> wrote in message
news:YGODf.15338$jO.10047@tornado.texas.rr.com...
>I have a new server running Windows 2003 Server and IIS 6. There are two
>active websites on the server. With the frequency of approximately once
>every 20 or so hours the sites become inaccessible. The are no errors in
>the Windows event log or in the IIS log files.
>
> But if I visit one of the sites directly on the server itself it will come
> up fine and from that point on the sites are accessible again. I don't
> have to restart IIS or anything else.
>
> I ran the Isstate utility against inetinfo.exe when its in the state where
> the sites are inaccessible.
>
> The iisstate log file follows.
>
> Opened log file 'C:\iisstate\output\IISState-1832.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Tue Jan 31 10:42:09 2006
>
> OS = Windows 2003 Server
> Executable: inetinfo.exe
> PID = 1832
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
>
>
> Thread ID: 0
> System Thread ID: c70
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0006f99c 7c821b84 ntdll!KiFastSystemCallRet
> 01 0006f9a0 77e41942 ntdll!NtReadFile+0xc
> 02 0006fa08 77f795ab kernel32!ReadFile+0x16c
> 03 0006fa34 77f7943c ADVAPI32!ScGetPipeInput+0x2a
> 04 0006faa8 77fb2ec9 ADVAPI32!ScDispatcherLoop+0x51
> 05 0006fcec 010027be ADVAPI32!StartServiceCtrlDispatcherA+0x93
> 06 0006fe1c 01002969 inetinfo!StartDispatchTable+0x277
> 07 0006ff44 0100339d inetinfo!main+0x117
> 08 0006ffc0 77e523cd inetinfo!mainCRTStartup+0x12f
> 09 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
>
>
>
> Thread ID: 1
> System Thread ID: bec
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0082fe14 7c822124 ntdll!KiFastSystemCallRet
> 01 0082fe18 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0082fe88 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0082fe9c 01002ebf kernel32!WaitForSingleObject+0x12
> 04 0082ffb8 77e66063 inetinfo!W3SVCThreadEntry+0x3d
> 05 0082ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 2
> System Thread ID: bf0
> Kernel Time: 0:0:0.31
> User Time: 0:0:0.31
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0086fcb8 7c822124 ntdll!KiFastSystemCallRet
> 01 0086fcbc 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0086fd2c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0086fd40 649f26a4 kernel32!WaitForSingleObject+0x12
> 04 0086fd68 010024b3 iisadmin!ServiceEntry+0x28a
> 05 0086ffa4 77f79348 inetinfo!InetinfoStartService+0x2cc
> 06 0086ffb8 77e66063 ADVAPI32!ScSvcctrlThreadA+0x21
> 07 0086ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 3
> System Thread ID: cd4
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00c3ff9c 7c821364 ntdll!KiFastSystemCallRet
> 01 00c3ffa0 7c81fe26 ntdll!NtDelayExecution+0xc
> 02 00c3ffb8 77e66063 ntdll!RtlpTimerThread+0x47
> 03 00c3ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 4
> System Thread ID: ce8
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.15
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00c7ff70 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00c7ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
> 02 00c7ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
> 03 00c7ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 5
> System Thread ID: 6f8
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00d4feac 7c822114 ntdll!KiFastSystemCallRet
> 01 00d4feb0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
> 02 00d4ff58 77e61075 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 00d4ff74 56f951ef kernel32!WaitForMultipleObjects+0x18
> 04 00d4ffa0 56f96a06 COADMIN!NOTIFY_CONTEXT::GetNextContext+0x67
> 05 00d4ffb8 77e66063 COADMIN!NOTIFY_CONTEXT::NotifyThreadProc+0x5f
> 06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 6
> System Thread ID: c50
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0178fcec 7c822114 ntdll!KiFastSystemCallRet
> 01 0178fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
> 02 0178ffb8 77e66063 ntdll!RtlpWaitThread+0x161
> 03 0178ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 7
> System Thread ID: 72c
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.62
> Thread Type: Possible ASP page. Possible DCOM activity
> Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> Continuing with other analysis.
>
> No remote call being made
>
> # ChildEBP RetAddr
> 00 016cfe18 7c821c54 ntdll!KiFastSystemCallRet
> 01 016cfe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
> 02 016cff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> 03 016cff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
> 04 016cffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
> 05 016cffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
> 06 016cffec 00000000 kernel32!BaseThreadStart+0x34
>
> *****
>
> Dump name is formatted as: PID-Timestamp.dmp
>
> Creating C:\iisstate\output\1832-1138725731.dmp - mini user dump
>
> *****
>
> Closing open log file C:\iisstate\output\IISState-1832.log

kloodge
Fri Feb 03 08:38:27 CST 2006

kloodge wrote:
> I have a new server running Windows 2003 Server and IIS 6. There are two
> active websites on the server. With the frequency of approximately once
> every 20 or so hours the sites become inaccessible. The are no errors
> in the Windows event log or in the IIS log files.
>
> But if I visit one of the sites directly on the server itself it will
> come up fine and from that point on the sites are accessible again. I
> don't have to restart IIS or anything else.
>
> I ran the Isstate utility against inetinfo.exe when its in the state
> where the sites are inaccessible.
>
> The iisstate log file follows.
>
> Opened log file 'C:\iisstate\output\IISState-1832.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Tue Jan 31 10:42:09 2006
>
> OS = Windows 2003 Server
> Executable: inetinfo.exe
> PID = 1832
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
>
>
> Thread ID: 0
> System Thread ID: c70
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0006f99c 7c821b84 ntdll!KiFastSystemCallRet
> 01 0006f9a0 77e41942 ntdll!NtReadFile+0xc
> 02 0006fa08 77f795ab kernel32!ReadFile+0x16c
> 03 0006fa34 77f7943c ADVAPI32!ScGetPipeInput+0x2a
> 04 0006faa8 77fb2ec9 ADVAPI32!ScDispatcherLoop+0x51
> 05 0006fcec 010027be ADVAPI32!StartServiceCtrlDispatcherA+0x93
> 06 0006fe1c 01002969 inetinfo!StartDispatchTable+0x277
> 07 0006ff44 0100339d inetinfo!main+0x117
> 08 0006ffc0 77e523cd inetinfo!mainCRTStartup+0x12f
> 09 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
>
>
>
> Thread ID: 1
> System Thread ID: bec
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0082fe14 7c822124 ntdll!KiFastSystemCallRet
> 01 0082fe18 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0082fe88 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0082fe9c 01002ebf kernel32!WaitForSingleObject+0x12
> 04 0082ffb8 77e66063 inetinfo!W3SVCThreadEntry+0x3d
> 05 0082ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 2
> System Thread ID: bf0
> Kernel Time: 0:0:0.31
> User Time: 0:0:0.31
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0086fcb8 7c822124 ntdll!KiFastSystemCallRet
> 01 0086fcbc 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0086fd2c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0086fd40 649f26a4 kernel32!WaitForSingleObject+0x12
> 04 0086fd68 010024b3 iisadmin!ServiceEntry+0x28a
> 05 0086ffa4 77f79348 inetinfo!InetinfoStartService+0x2cc
> 06 0086ffb8 77e66063 ADVAPI32!ScSvcctrlThreadA+0x21
> 07 0086ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 3
> System Thread ID: cd4
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00c3ff9c 7c821364 ntdll!KiFastSystemCallRet
> 01 00c3ffa0 7c81fe26 ntdll!NtDelayExecution+0xc
> 02 00c3ffb8 77e66063 ntdll!RtlpTimerThread+0x47
> 03 00c3ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 4
> System Thread ID: ce8
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.15
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00c7ff70 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00c7ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
> 02 00c7ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
> 03 00c7ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 5
> System Thread ID: 6f8
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00d4feac 7c822114 ntdll!KiFastSystemCallRet
> 01 00d4feb0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
> 02 00d4ff58 77e61075 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 00d4ff74 56f951ef kernel32!WaitForMultipleObjects+0x18
> 04 00d4ffa0 56f96a06 COADMIN!NOTIFY_CONTEXT::GetNextContext+0x67
> 05 00d4ffb8 77e66063 COADMIN!NOTIFY_CONTEXT::NotifyThreadProc+0x5f
> 06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 6
> System Thread ID: c50
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0178fcec 7c822114 ntdll!KiFastSystemCallRet
> 01 0178fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
> 02 0178ffb8 77e66063 ntdll!RtlpWaitThread+0x161
> 03 0178ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 7
> System Thread ID: 72c
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.62
> Thread Type: Possible ASP page. Possible DCOM activity
> Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> Continuing with other analysis.
>
> No remote call being made
>
> # ChildEBP RetAddr
> 00 016cfe18 7c821c54 ntdll!KiFastSystemCallRet
> 01 016cfe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
> 02 016cff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> 03 016cff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
> 04 016cffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
> 05 016cffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
> 06 016cffec 00000000 kernel32!BaseThreadStart+0x34
>
> *****
>
> Dump name is formatted as: PID-Timestamp.dmp
>
> Creating C:\iisstate\output\1832-1138725731.dmp - mini user dump
>
> *****
>
> Closing open log file C:\iisstate\output\IISState-1832.log


I haven't solved the problem but I have discovered that it's not an IIS
issue.

The network interface on the server is arbitrarily going down. Once I
disable/enable the interface everything works correctly.

kloodge
Tue Feb 07 15:26:44 CST 2006

kloodge wrote:
> I have a new server running Windows 2003 Server and IIS 6. There are two
> active websites on the server. With the frequency of approximately once
> every 20 or so hours the sites become inaccessible. The are no errors
> in the Windows event log or in the IIS log files.
>
> But if I visit one of the sites directly on the server itself it will
> come up fine and from that point on the sites are accessible again. I
> don't have to restart IIS or anything else.
>
> I ran the Isstate utility against inetinfo.exe when its in the state
> where the sites are inaccessible.
>
> The iisstate log file follows.
>
> Opened log file 'C:\iisstate\output\IISState-1832.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Tue Jan 31 10:42:09 2006
>
> OS = Windows 2003 Server
> Executable: inetinfo.exe
> PID = 1832
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
>
>
> Thread ID: 0
> System Thread ID: c70
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0006f99c 7c821b84 ntdll!KiFastSystemCallRet
> 01 0006f9a0 77e41942 ntdll!NtReadFile+0xc
> 02 0006fa08 77f795ab kernel32!ReadFile+0x16c
> 03 0006fa34 77f7943c ADVAPI32!ScGetPipeInput+0x2a
> 04 0006faa8 77fb2ec9 ADVAPI32!ScDispatcherLoop+0x51
> 05 0006fcec 010027be ADVAPI32!StartServiceCtrlDispatcherA+0x93
> 06 0006fe1c 01002969 inetinfo!StartDispatchTable+0x277
> 07 0006ff44 0100339d inetinfo!main+0x117
> 08 0006ffc0 77e523cd inetinfo!mainCRTStartup+0x12f
> 09 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
>
>
>
> Thread ID: 1
> System Thread ID: bec
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0082fe14 7c822124 ntdll!KiFastSystemCallRet
> 01 0082fe18 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0082fe88 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0082fe9c 01002ebf kernel32!WaitForSingleObject+0x12
> 04 0082ffb8 77e66063 inetinfo!W3SVCThreadEntry+0x3d
> 05 0082ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 2
> System Thread ID: bf0
> Kernel Time: 0:0:0.31
> User Time: 0:0:0.31
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0086fcb8 7c822124 ntdll!KiFastSystemCallRet
> 01 0086fcbc 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0086fd2c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0086fd40 649f26a4 kernel32!WaitForSingleObject+0x12
> 04 0086fd68 010024b3 iisadmin!ServiceEntry+0x28a
> 05 0086ffa4 77f79348 inetinfo!InetinfoStartService+0x2cc
> 06 0086ffb8 77e66063 ADVAPI32!ScSvcctrlThreadA+0x21
> 07 0086ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 3
> System Thread ID: cd4
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00c3ff9c 7c821364 ntdll!KiFastSystemCallRet
> 01 00c3ffa0 7c81fe26 ntdll!NtDelayExecution+0xc
> 02 00c3ffb8 77e66063 ntdll!RtlpTimerThread+0x47
> 03 00c3ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 4
> System Thread ID: ce8
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.15
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00c7ff70 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00c7ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
> 02 00c7ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
> 03 00c7ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 5
> System Thread ID: 6f8
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00d4feac 7c822114 ntdll!KiFastSystemCallRet
> 01 00d4feb0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
> 02 00d4ff58 77e61075 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 00d4ff74 56f951ef kernel32!WaitForMultipleObjects+0x18
> 04 00d4ffa0 56f96a06 COADMIN!NOTIFY_CONTEXT::GetNextContext+0x67
> 05 00d4ffb8 77e66063 COADMIN!NOTIFY_CONTEXT::NotifyThreadProc+0x5f
> 06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 6
> System Thread ID: c50
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0178fcec 7c822114 ntdll!KiFastSystemCallRet
> 01 0178fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
> 02 0178ffb8 77e66063 ntdll!RtlpWaitThread+0x161
> 03 0178ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 7
> System Thread ID: 72c
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.62
> Thread Type: Possible ASP page. Possible DCOM activity
> Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> Continuing with other analysis.
>
> No remote call being made
>
> # ChildEBP RetAddr
> 00 016cfe18 7c821c54 ntdll!KiFastSystemCallRet
> 01 016cfe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
> 02 016cff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> 03 016cff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
> 04 016cffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
> 05 016cffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
> 06 016cffec 00000000 kernel32!BaseThreadStart+0x34
>
> *****
>
> Dump name is formatted as: PID-Timestamp.dmp
>
> Creating C:\iisstate\output\1832-1138725731.dmp - mini user dump
>
> *****
>
> Closing open log file C:\iisstate\output\IISState-1832.log


It turns out that my problem was a basic connectivity problem caused by
specifying a default gateway on both NICs in the server.

I found this information on Microsoft's site:

"When configuring a computer to be multihomed on two disjoint networks,
the best practice is to configure the default gateway on the interface
connected to the largest and least-known network, in which the default
route summarizes the most destinations. Then, either add static routes
or use a routing protocol to provide connectivity to the hosts on the
smaller or better-known network. Avoid configuring a different default
gateway on each side; this can result in unpredictable behavior and loss
of connectivity. For more information, see Default Gateway Behavior for
Windows TCP/IP."