Suffering from IIS hangs. Can anyone help on the iisstate dump fil

am 08.04.2008 18:35:10 von Sean Zhang

Hi, I am really suffering the IIS hanging problem. The iis server hangs
several times a day. We are using asp.net 2.0 and Sql-server 2005.

According to the google result, I made iisstate dump file when crashing. But
cannot read it and get any useful information from this. Can anyone give a
clue?

Thanks in advance.
Sean

Following is the dump file information:

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

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

Fri Mar 28 16:08:57 2008

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 3052

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

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

IIS has crashed...
Beginning Analysis
DLL (!FunctionName) that failed:

Thread ID: 34
System Thread ID: db0
Kernel Time: 0:0:0.296
User Time: 0:0:1.109
Thread Type: Other
# ChildEBP RetAddr
WARNING: Frame IP not in any known module. Following frames may be wrong.
00 056ff054 0537194a 0x34921b4
01 144995d0 1805bb7c 0x537194a
02 04e7fae4 000001bc 0x1805bb7c
Closing open log file C:\iisstate\output\IISState-3052.log
Opened log file 'C:\iisstate\output\IISState-3052.log'

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

Fri Mar 28 16:08:57 2008

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 3052

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

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

Thread ID: 0
System Thread ID: d40
Kernel Time: 0:0:0.0
User Time: 0:0:0.62
Thread Status: Thread is in a WAIT state.
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 0006fc08 7c957d0b ntdll!KiFastSystemCallRet
01 0006fc0c 7c821d1e ntdll!NtWaitForSingleObject+0xc
02 0006fc7c 7c821c8d kernel32!WaitForSingleObjectEx+0xac
03 0006fc90 5a604662 kernel32!WaitForSingleObject+0x12
04 0006fca0 5a606e3f w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
05 0006fca8 5a64f42d w3dt!UlAtqStartListen+0x2d
06 0006fcb8 5a65c335 w3core!W3_SERVER::StartListen+0xbd
07 0006ff0c 0100187c w3core!UlW3Start+0x26e
08 0006ff44 01001a27 w3wp!wmain+0x22a
09 0006ffc0 7c82f23b w3wp!wmainCRTStartup+0x12f
0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23

Thread ID: 1
System Thread ID: 17dc
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 006afea0 7c957cfb ntdll!KiFastSystemCallRet
01 006afea4 7c93e5bb ntdll!NtWaitForMultipleObjects+0xc
02 006aff48 7c93e4a2 ntdll!EtwpWaitForMultipleObjectsEx+0xf7
03 006affb8 7c824829 ntdll!EtwpEventPump+0x27f
04 006affec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 2
System Thread ID: 13f8
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00fbff9c 7c956f4b ntdll!KiFastSystemCallRet
01 00fbffa0 7c96d424 ntdll!NtDelayExecution+0xc
02 00fbffb8 7c824829 ntdll!RtlpTimerThread+0x47
03 00fbffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 3
System Thread ID: 49c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00ffff70 7c9577db ntdll!KiFastSystemCallRet
01 00ffff74 7c969f38 ntdll!ZwRemoveIoCompletion+0xc
02 00ffffb8 7c824829 ntdll!RtlpWorkerThread+0x3d
03 00ffffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 4
System Thread ID: 14c0
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
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 0107fe18 7c95783b ntdll!KiFastSystemCallRet
01 0107fe1c 77c585ac ntdll!NtReplyWaitReceivePortEx+0xc
02 0107ff84 77c58792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
03 0107ff8c 77c5872d RPCRT4!RecvLotsaCallsWrapper+0xd
04 0107ffac 77c4b110 RPCRT4!BaseCachedThreadRoutine+0x9d
05 0107ffb8 7c824829 RPCRT4!ThreadStartRoutine+0x1b
06 0107ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 5
System Thread ID: 108c
Kernel Time: 0:0:0.656
User Time: 0:0:1.125
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 0127ff24 7c9577db ntdll!KiFastSystemCallRet
01 0127ff28 7c81bea2 ntdll!ZwRemoveIoCompletion+0xc
02 0127ff54 5a5a248e kernel32!GetQueuedCompletionStatus+0x29
03 0127ff8c 5a5a26ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 0127ffa0 5a5a1da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 0127ffb8 7c824829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 0127ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 6
System Thread ID: 1708
Kernel Time: 0:0:0.750
User Time: 0:0:1.296
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 012bff24 7c9577db ntdll!KiFastSystemCallRet
01 012bff28 7c81bea2 ntdll!ZwRemoveIoCompletion+0xc
02 012bff54 5a5a248e kernel32!GetQueuedCompletionStatus+0x29
03 012bff8c 5a5a26ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 012bffa0 5a5a1da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 012bffb8 7c824829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 012bffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 7
System Thread ID: 1474
Kernel Time: 0:0:0.406
User Time: 0:0:0.718
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 012fff24 7c9577db ntdll!KiFastSystemCallRet
01 012fff28 7c81bea2 ntdll!ZwRemoveIoCompletion+0xc
02 012fff54 5a5a248e kernel32!GetQueuedCompletionStatus+0x29
03 012fff8c 5a5a26ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 012fffa0 5a5a1da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 012fffb8 7c824829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 012fffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 8
System Thread ID: c2c
Kernel Time: 0:0:0.265
User Time: 0:0:0.328
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 0133ff24 7c9577db ntdll!KiFastSystemCallRet
01 0133ff28 7c81bea2 ntdll!ZwRemoveIoCompletion+0xc
02 0133ff54 5a5a248e kernel32!GetQueuedCompletionStatus+0x29
03 0133ff8c 5a5a26ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 0133ffa0 5a5a1da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 0133ffb8 7c824829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 0133ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 9
System Thread ID: e0c
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 013ffcec 7c957cfb ntdll!KiFastSystemCallRet
01 013ffcf0 7c96c78e ntdll!NtWaitForMultipleObjects+0xc
02 013fffb8 7c824829 ntdll!RtlpWaitThread+0x161
03 013fffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 10
System Thread ID: 110c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 01f1fa84 7c957d0b ntdll!KiFastSystemCallRet
01 01f1fa88 7c821d1e ntdll!NtWaitForSingleObject+0xc
02 01f1faf8 7c821c8d kernel32!WaitForSingleObjectEx+0xac
03 01f1fb0c 5a65820f kernel32!WaitForSingleObject+0x12
04 01f1ffb8 7c824829 w3core!HTTP_COMPRESSION::CompressionThread+0x126
05 01f1ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 11
System Thread ID: 1364
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
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 01f5fe18 7c95783b ntdll!KiFastSystemCallRet
01 01f5fe1c 77c585ac ntdll!NtReplyWaitReceivePortEx+0xc
02 01f5ff84 77c58792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
03 01f5ff8c 77c5872d RPCRT4!RecvLotsaCallsWrapper+0xd
04 01f5ffac 77c4b110 RPCRT4!BaseCachedThreadRoutine+0x9d
05 01f5ffb8 7c824829 RPCRT4!ThreadStartRoutine+0x1b
06 01f5ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 12
System Thread ID: 130c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 01f9ff8c 7c956f4b ntdll!KiFastSystemCallRet
01 01f9ff90 7c94943a ntdll!NtDelayExecution+0xc
02 01f9ffb8 7c824829 ntdll!RtlpIOWorkerThread+0x3f
03 01f9ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 13
System Thread ID: 177c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0

Re: Suffering from IIS hangs. Can anyone help on the iisstate dump fil

am 09.04.2008 03:49:53 von Ken Schaefer

Log file is incomplete. There isn't anything I can see in the threads below
that could indicate the cause.

Cheers
Ken

"Sean Zhang" wrote in message
news:9DD1DDB3-B15B-452E-AA09-51DD8464E690@microsoft.com...
> Hi, I am really suffering the IIS hanging problem. The iis server hangs
> several times a day. We are using asp.net 2.0 and Sql-server 2005.
>
> According to the google result, I made iisstate dump file when crashing.
> But
> cannot read it and get any useful information from this. Can anyone give a
> clue?
>
> Thanks in advance.
> Sean
>
> Following is the dump file information:
>
> Opened log file 'C:\iisstate\output\IISState-3052.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Fri Mar 28 16:08:57 2008
>
> OS = Windows 2003 Server
> Executable: w3wp.exe
> PID = 3052
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
> IIS has crashed...
> Beginning Analysis
> DLL (!FunctionName) that failed:
>
>
>
>
> Thread ID: 34
> System Thread ID: db0
> Kernel Time: 0:0:0.296
> User Time: 0:0:1.109
> Thread Type: Other
> # ChildEBP RetAddr
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> 00 056ff054 0537194a 0x34921b4
> 01 144995d0 1805bb7c 0x537194a
> 02 04e7fae4 000001bc 0x1805bb7c
> Closing open log file C:\iisstate\output\IISState-3052.log
> Opened log file 'C:\iisstate\output\IISState-3052.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Fri Mar 28 16:08:57 2008
>
> OS = Windows 2003 Server
> Executable: w3wp.exe
> PID = 3052
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
>
>
> Thread ID: 0
> System Thread ID: d40
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.62
> Thread Status: Thread is in a WAIT state.
> Thread Type: HTTP Compression Thread
> # ChildEBP RetAddr
> 00 0006fc08 7c957d0b ntdll!KiFastSystemCallRet
> 01 0006fc0c 7c821d1e ntdll!NtWaitForSingleObject+0xc
> 02 0006fc7c 7c821c8d kernel32!WaitForSingleObjectEx+0xac
> 03 0006fc90 5a604662 kernel32!WaitForSingleObject+0x12
> 04 0006fca0 5a606e3f w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
> 05 0006fca8 5a64f42d w3dt!UlAtqStartListen+0x2d
> 06 0006fcb8 5a65c335 w3core!W3_SERVER::StartListen+0xbd
> 07 0006ff0c 0100187c w3core!UlW3Start+0x26e
> 08 0006ff44 01001a27 w3wp!wmain+0x22a
> 09 0006ffc0 7c82f23b w3wp!wmainCRTStartup+0x12f
> 0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
>
>
>
> Thread ID: 1
> System Thread ID: 17dc
> 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 006afea0 7c957cfb ntdll!KiFastSystemCallRet
> 01 006afea4 7c93e5bb ntdll!NtWaitForMultipleObjects+0xc
> 02 006aff48 7c93e4a2 ntdll!EtwpWaitForMultipleObjectsEx+0xf7
> 03 006affb8 7c824829 ntdll!EtwpEventPump+0x27f
> 04 006affec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 2
> System Thread ID: 13f8
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00fbff9c 7c956f4b ntdll!KiFastSystemCallRet
> 01 00fbffa0 7c96d424 ntdll!NtDelayExecution+0xc
> 02 00fbffb8 7c824829 ntdll!RtlpTimerThread+0x47
> 03 00fbffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 3
> System Thread ID: 49c
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00ffff70 7c9577db ntdll!KiFastSystemCallRet
> 01 00ffff74 7c969f38 ntdll!ZwRemoveIoCompletion+0xc
> 02 00ffffb8 7c824829 ntdll!RtlpWorkerThread+0x3d
> 03 00ffffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 4
> System Thread ID: 14c0
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> 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 0107fe18 7c95783b ntdll!KiFastSystemCallRet
> 01 0107fe1c 77c585ac ntdll!NtReplyWaitReceivePortEx+0xc
> 02 0107ff84 77c58792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> 03 0107ff8c 77c5872d RPCRT4!RecvLotsaCallsWrapper+0xd
> 04 0107ffac 77c4b110 RPCRT4!BaseCachedThreadRoutine+0x9d
> 05 0107ffb8 7c824829 RPCRT4!ThreadStartRoutine+0x1b
> 06 0107ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 5
> System Thread ID: 108c
> Kernel Time: 0:0:0.656
> User Time: 0:0:1.125
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 0127ff24 7c9577db ntdll!KiFastSystemCallRet
> 01 0127ff28 7c81bea2 ntdll!ZwRemoveIoCompletion+0xc
> 02 0127ff54 5a5a248e kernel32!GetQueuedCompletionStatus+0x29
> 03 0127ff8c 5a5a26ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 0127ffa0 5a5a1da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 0127ffb8 7c824829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 0127ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 6
> System Thread ID: 1708
> Kernel Time: 0:0:0.750
> User Time: 0:0:1.296
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 012bff24 7c9577db ntdll!KiFastSystemCallRet
> 01 012bff28 7c81bea2 ntdll!ZwRemoveIoCompletion+0xc
> 02 012bff54 5a5a248e kernel32!GetQueuedCompletionStatus+0x29
> 03 012bff8c 5a5a26ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 012bffa0 5a5a1da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 012bffb8 7c824829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 012bffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 7
> System Thread ID: 1474
> Kernel Time: 0:0:0.406
> User Time: 0:0:0.718
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 012fff24 7c9577db ntdll!KiFastSystemCallRet
> 01 012fff28 7c81bea2 ntdll!ZwRemoveIoCompletion+0xc
> 02 012fff54 5a5a248e kernel32!GetQueuedCompletionStatus+0x29
> 03 012fff8c 5a5a26ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 012fffa0 5a5a1da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 012fffb8 7c824829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 012fffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 8
> System Thread ID: c2c
> Kernel Time: 0:0:0.265
> User Time: 0:0:0.328
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 0133ff24 7c9577db ntdll!KiFastSystemCallRet
> 01 0133ff28 7c81bea2 ntdll!ZwRemoveIoCompletion+0xc
> 02 0133ff54 5a5a248e kernel32!GetQueuedCompletionStatus+0x29
> 03 0133ff8c 5a5a26ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 0133ffa0 5a5a1da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 0133ffb8 7c824829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 0133ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 9
> System Thread ID: e0c
> 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 013ffcec 7c957cfb ntdll!KiFastSystemCallRet
> 01 013ffcf0 7c96c78e ntdll!NtWaitForMultipleObjects+0xc
> 02 013fffb8 7c824829 ntdll!RtlpWaitThread+0x161
> 03 013fffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 10
> System Thread ID: 110c
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: HTTP Compression Thread
> # ChildEBP RetAddr
> 00 01f1fa84 7c957d0b ntdll!KiFastSystemCallRet
> 01 01f1fa88 7c821d1e ntdll!NtWaitForSingleObject+0xc
> 02 01f1faf8 7c821c8d kernel32!WaitForSingleObjectEx+0xac
> 03 01f1fb0c 5a65820f kernel32!WaitForSingleObject+0x12
> 04 01f1ffb8 7c824829 w3core!HTTP_COMPRESSION::CompressionThread+0x126
> 05 01f1ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 11
> System Thread ID: 1364
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> 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 01f5fe18 7c95783b ntdll!KiFastSystemCallRet
> 01 01f5fe1c 77c585ac ntdll!NtReplyWaitReceivePortEx+0xc
> 02 01f5ff84 77c58792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> 03 01f5ff8c 77c5872d RPCRT4!RecvLotsaCallsWrapper+0xd
> 04 01f5ffac 77c4b110 RPCRT4!BaseCachedThreadRoutine+0x9d
> 05 01f5ffb8 7c824829 RPCRT4!ThreadStartRoutine+0x1b
> 06 01f5ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 12
> System Thread ID: 130c
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 01f9ff8c 7c956f4b ntdll!KiFastSystemCallRet
> 01 01f9ff90 7c94943a ntdll!NtDelayExecution+0xc
> 02 01f9ffb8 7c824829 ntdll!RtlpIOWorkerThread+0x3f
> 03 01f9ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 13
> System Thread ID: 177c
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
>