Re: IISState, need help finding info
From: Scott Forsyth (scottnewsgroups_at_orcsweb.com)
Date: 06/25/04
- Next message: Peter Yohe: "Directory Names with Executable Extensions..."
- Previous message: Ken Schaefer: "Re: NTFS deny permissions"
- In reply to: Pat [MSFT]: "Re: IISState, need help finding info"
- Next in thread: Pat [MSFT]: "Re: IISState, need help finding info"
- Reply: Pat [MSFT]: "Re: IISState, need help finding info"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Jun 2004 22:21:42 -0400
Hi Pat,
Thanks for the reply! I tried to get a dump but I get the following error.
When I installed iisstate on this server, I used the .msi so I'm not sure
what I need to do to be able to get a proper dump.
Symbol search path is:
SRV*D:\iisstate\symbols*http://msdl.microsoft.com/downloa
d/symbols
Microsoft (R) Windows Debugger Version 6.2.0013.1
Copyright (c) Microsoft Corporation. All rights reserved.
*** wait with pending attach
Symbol search path is:
SRV*D:\iisstate\symbols*http://msdl.microsoft.com/downloa
d/symbols
Executable search path is:
WARNING: Process 3568 is not attached as a debuggee
The process can be examined but debug events will not be received
............................................................................
....
.........................
The call to LoadLibrary(exts) failed, Win32 error 2
"The system cannot find the file specified."
Please check your debugger configuration and/or network access.
(df0.d04): Wake debugger - code 80000007 (first chance)
Opened log file 'D:\iisstate\output\IISState-3568.log'
-- Thanks, Scott Forsyth Microsoft MVP - ASP/ASP.NET ASPInsider Member - MCP http://www.orcsweb.com/ Powerful Web Hosting Solutions #1 in Service and Support "Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message news:evghqblWEHA.4092@TK2MSFTNGP11.phx.gbl... > Thread 10 is the culprit. Unfortunately, it is a managed thread and > IISState did not figure that out, so it did not identify the page. So, > basically, you have a bug in a .Net page that is causing the problem. > > You can try running IISState again the next time it happens and we may get a > better idea of the specific page. Otherwise, you can have IISState create a > .dmp file and use the debuggers (www.microsoft.com/ddk/debugging) to > identify the page. > > > Pat > > "Scott Forsyth" <scottnewsgroups@orcsweb.com> wrote in message > news:u2$duHTWEHA.1380@TK2MSFTNGP12.phx.gbl... > > Hi, > > > > I'm starting to try to use IISState. I was able to find and address a > > 100%CPU issue yesterday which was great! I still have many situations > > though where I can't determine the relevant information from the memory > > dumps. I'll include a memory dump I just got from the w3wp process that > was > > using up all available CPU on the server. > > > > Can anyone offer any advice on what I should take note of? > > > > Thanks, > > > > Scott > > > > ---------------- > > > > Opened log file 'D:\iisstate\output\IISState-8504.log' > > > > *********************** > > Starting new log output > > IISState version 3.3.1 > > > > Wed Jun 23 10:49:37 2004 > > > > OS = Windows 2003 Server > > Executable: w3wp.exe > > PID = 8504 > > > > Note: Thread times are formatted as HH:MM:SS.ms > > > > *********************** > > > > > > > > > > Thread ID: 0 > > System Thread ID: b78 > > Kernel Time: 0:0:0.31 > > User Time: 0:0:0.62 > > Thread Type: HTTP Compression Thread > > # ChildEBP RetAddr > > 00 0006fe58 77f43741 SharedUserData!SystemCallStub+0x4 > > 01 0006fe5c 77e41817 ntdll!ZwWaitForSingleObject+0xc > > 02 0006fecc 77e4168f kernel32!WaitForSingleObjectEx+0xac > > 03 0006fedc 5a3635ae kernel32!WaitForSingleObject+0xf > > 04 0006feec 5a364d7d w3dt!WP_CONTEXT::RunMainThreadLoop+0xe > > 05 0006fef4 5a3a1d98 w3dt!UlAtqStartListen+0x2d > > 06 0006ff00 5a3a5d54 w3core!W3_SERVER::StartListen+0x8e > > 07 0006ff0c 010017af w3core!UlW3Start+0xea > > 08 0006ff44 0100195e w3wp!wmain+0x236 > > 09 0006ffc0 77e4f38c w3wp!wmainCRTStartup+0x12f > > 0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23 > > > > > > > > > > Thread ID: 1 > > System Thread ID: fac > > Kernel Time: 0:0:0.234 > > User Time: 0:0:0.93 > > Thread Type: Other > > # ChildEBP RetAddr > > 00 009bff9c 77f4262b SharedUserData!SystemCallStub+0x4 > > 01 009bffa0 77f6b5b2 ntdll!NtDelayExecution+0xc > > 02 009bffb8 77e4a990 ntdll!RtlpTimerThread+0x45 > > 03 009bffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 2 > > System Thread ID: 213c > > Kernel Time: 0:0:0.203 > > User Time: 0:0:0.265 > > Thread Type: HTTP Listener > > # ChildEBP RetAddr > > 00 00cbff28 77f430c7 SharedUserData!SystemCallStub+0x4 > > 01 00cbff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc > > 02 00cbff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27 > > 03 00cbff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31 > > 04 00cbffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21 > > 05 00cbffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35 > > 06 00cbffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 3 > > System Thread ID: 1f48 > > Kernel Time: 0:0:1.437 > > User Time: 0:0:1.484 > > Thread Type: HTTP Listener > > # ChildEBP RetAddr > > 00 00cfff28 77f430c7 SharedUserData!SystemCallStub+0x4 > > 01 00cfff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc > > 02 00cfff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27 > > 03 00cfff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31 > > 04 00cfffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21 > > 05 00cfffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35 > > 06 00cfffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 4 > > System Thread ID: bf8 > > Kernel Time: 0:0:4.765 > > User Time: 0:0:4.640 > > Thread Type: HTTP Listener > > # ChildEBP RetAddr > > 00 00d3ff28 77f430c7 SharedUserData!SystemCallStub+0x4 > > 01 00d3ff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc > > 02 00d3ff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27 > > 03 00d3ff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31 > > 04 00d3ffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21 > > 05 00d3ffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35 > > 06 00d3ffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 5 > > System Thread ID: f04 > > Kernel Time: 0:0:7.843 > > User Time: 0:0:7.515 > > Thread Type: HTTP Listener > > # ChildEBP RetAddr > > 00 00d7ff28 77f430c7 SharedUserData!SystemCallStub+0x4 > > 01 00d7ff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc > > 02 00d7ff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27 > > 03 00d7ff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31 > > 04 00d7ffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21 > > 05 00d7ffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35 > > 06 00d7ffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 6 > > System Thread ID: 8f0 > > Kernel Time: 0:0:0.62 > > User Time: 0:0:0.0 > > Thread Status: Thread is in a WAIT state. > > Thread Type: Other > > # ChildEBP RetAddr > > 00 00e3fcec 77f4372d SharedUserData!SystemCallStub+0x4 > > 01 00e3fcf0 77f75297 ntdll!NtWaitForMultipleObjects+0xc > > 02 00e3ffb8 77e4a990 ntdll!RtlpWaitThread+0x158 > > 03 00e3ffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 7 > > System Thread ID: 2080 > > Kernel Time: 0:0:0.0 > > User Time: 0:0:0.0 > > Thread Type: HTTP Compression Thread > > # ChildEBP RetAddr > > 00 0170ff14 77f43741 SharedUserData!SystemCallStub+0x4 > > 01 0170ff18 77e41817 ntdll!ZwWaitForSingleObject+0xc > > 02 0170ff88 77e4168f kernel32!WaitForSingleObjectEx+0xac > > 03 0170ff98 5a3a51f7 kernel32!WaitForSingleObject+0xf > > 04 0170ffb8 77e4a990 w3core!HTTP_COMPRESSION::CompressionThread+0x85 > > 05 0170ffc4 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 8 > > System Thread ID: dd4 > > Kernel Time: 0:0:0.0 > > User Time: 0:0:0.0 > > Thread Type: Other > > # ChildEBP RetAddr > > 00 0178ff8c 77f4262b SharedUserData!SystemCallStub+0x4 > > 01 0178ff90 77f6f0fc ntdll!NtDelayExecution+0xc > > 02 0178ffb8 77e4a990 ntdll!RtlpIOWorkerThread+0x3d > > 03 0178ffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 9 > > System Thread ID: 8d4 > > Kernel Time: 0:0:0.687 > > User Time: 0:0:0.734 > > Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker > > succeeded > > Loaded Son of Strike data table version 5 from > > "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll" > > Thread 9 > > Not a managed thread. > > > > > > Begin System Thread Information > > > > # ChildEBP RetAddr > > 00 0187fee4 77f4262b SharedUserData!SystemCallStub+0x4 > > 01 0187fee8 77e418ea ntdll!NtDelayExecution+0xc > > 02 0187ff50 77e416ee kernel32!SleepEx+0x68 > > 03 0187ff5c 792e9ebe kernel32!Sleep+0xb > > 04 0187ffb8 77e4a990 mscorwks!ThreadpoolMgr::GateThreadStart+0x54 > > 05 0187ffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 10 > > System Thread ID: 1ff4 > > Kernel Time: 0:1:31.515 > > User Time: 0:12:4.265 > > Thread Type: Other > > # ChildEBP RetAddr > > WARNING: Frame IP not in any known module. Following frames may be wrong. > > 00 018bf888 080b29de 0x87d1d8d > > 01 00000001 00000000 0x80b29de > > > > > > > > > > Thread ID: 11 > > System Thread ID: 1a6c > > Kernel Time: 0:0:0.0 > > User Time: 0:0:0.0 > > Thread Status: Thread is in a WAIT state. > > Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker > > Thread 11 > > Not a managed thread. > > > > > > Begin System Thread Information > > > > # ChildEBP RetAddr > > 00 019afe74 77f4372d SharedUserData!SystemCallStub+0x4 > > 01 019afe78 77e41bfa ntdll!NtWaitForMultipleObjects+0xc > > 02 019aff20 77e4b0e4 kernel32!WaitForMultipleObjectsEx+0x11a > > 03 019aff38 791d25d5 kernel32!WaitForMultipleObjects+0x17 > > 04 019affa0 791d254c mscorwks!DebuggerRCThread::MainLoop+0x90 > > 05 019affb0 791d4d50 mscorwks!DebuggerRCThread::ThreadProc+0x68 > > 06 019affb8 77e4a990 mscorwks!DebuggerRCThread::ThreadProcStatic+0xb > > 07 019affec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 12 > > System Thread ID: ab4 > > Kernel Time: 0:0:0.15 > > User Time: 0:0:1.31 > > Thread Status: Thread is in a WAIT state. > > Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker > > Thread 12 > > ESP EIP > > > > > > Begin System Thread Information > > > > # ChildEBP RetAddr > > 00 01a8fe90 77f4372d SharedUserData!SystemCallStub+0x4 > > 01 01a8fe94 77e41bfa ntdll!NtWaitForMultipleObjects+0xc > > 02 01a8ff3c 77e4b0e4 kernel32!WaitForMultipleObjectsEx+0x11a > > 03 01a8ff54 79262a5f kernel32!WaitForMultipleObjects+0x17 > > 04 01a8ff74 791bbea4 mscorwks!WaitForFinalizerEvent+0x5a > > 05 01a8ffb8 77e4a990 mscorwks!GCHeap::FinalizerThreadStart+0x96 > > 06 01a8ffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 13 > > System Thread ID: 2640 > > Kernel Time: 0:0:0.500 > > User Time: 0:0:0.578 > > Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker > > Thread 13 > > Not a managed thread. > > > > > > Begin System Thread Information > > > > # ChildEBP RetAddr > > 00 01d6ff38 77f4262b SharedUserData!SystemCallStub+0x4 > > 01 01d6ff3c 77e418ea ntdll!NtDelayExecution+0xc > > 02 01d6ffa4 792ea483 kernel32!SleepEx+0x68 > > 03 01d6ffb8 77e4a990 mscorwks!ThreadpoolMgr::TimerThreadStart+0x30 > > 04 01d6ffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 14 > > System Thread ID: b3c > > Kernel Time: 0:1:34.140 > > User Time: 0:2:48.640 > > Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker > > Thread 14 > > ESP EIP > > > > > > Begin System Thread Information > > > > # ChildEBP RetAddr > > 00 01ecff10 77f43741 SharedUserData!SystemCallStub+0x4 > > 01 01ecff14 77e41817 ntdll!ZwWaitForSingleObject+0xc > > 02 01ecff84 77e4168f kernel32!WaitForSingleObjectEx+0xac > > 03 01ecff94 792e91e0 kernel32!WaitForSingleObject+0xf > > 04 01ecffb8 77e4a990 mscorwks!ThreadpoolMgr::WorkerThreadStart+0x3a > > 05 01ecffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 15 > > System Thread ID: dc0 > > Kernel Time: 0:0:0.0 > > User Time: 0:0:0.0 > > Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker > > Thread 15 > > ESP EIP > > > > > > Begin System Thread Information > > > > # ChildEBP RetAddr > > 00 089bff24 77f4262b SharedUserData!SystemCallStub+0x4 > > 01 089bff28 77e418ea ntdll!NtDelayExecution+0xc > > 02 089bff90 792ea315 kernel32!SleepEx+0x68 > > 03 089bffb8 77e4a990 mscorwks!ThreadpoolMgr::WaitThreadStart+0x22 > > 04 089bffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 16 > > System Thread ID: 18a4 > > Kernel Time: 0:0:0.46 > > User Time: 0:0:0.0 > > Thread Type: Other > > # ChildEBP RetAddr > > 00 0911ff14 77d06718 SharedUserData!SystemCallStub+0x4 > > 01 0911ff34 771b2711 USER32!NtUserGetMessage+0xc > > 02 0911ff74 771b268f ole32!CDllHost::STAWorkerLoop+0x70 > > 03 0911ff90 771b25da ole32!CDllHost::WorkerThread+0xc6 > > 04 0911ff94 771625ea ole32!DLLHostThreadEntry+0x9 > > 05 0911ff9c 77160000 ole32!CRpcThread::WorkerLoop+0x1e > > 06 0911ffac 77162653 ole32!_imp__InstallApplication <PERF> (ole32+0x0) > > 07 0911ffb8 77e4a990 ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1f > > 08 0911ffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 17 > > System Thread ID: d7c > > Kernel Time: 0:0:0.937 > > User Time: 0:0:0.281 > > Thread Type: Other > > # ChildEBP RetAddr > > 00 092aff70 77f430c7 SharedUserData!SystemCallStub+0x4 > > 01 092aff74 77f7e6ae ntdll!ZwRemoveIoCompletion+0xc > > 02 092affb8 77e4a990 ntdll!RtlpWorkerThread+0x3b > > 03 092affec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 18 > > System Thread ID: 1978 > > 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 0942fe20 77f4313f SharedUserData!SystemCallStub+0x4 > > 01 0942fe24 77c57b85 ntdll!NtReplyWaitReceivePortEx+0xc > > 02 0942ff8c 77c60829 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x193 > > 03 0942ff90 77c60771 RPCRT4!RecvLotsaCallsWrapper+0x9 > > 04 0942ffb0 77c60857 RPCRT4!BaseCachedThreadRoutine+0x9c > > 05 0942ffb8 77e4a990 RPCRT4!ThreadStartRoutine+0x17 > > 06 0942ffec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 19 > > System Thread ID: 201c > > Kernel Time: 0:0:0.125 > > User Time: 0:0:0.421 > > Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker > > Thread 19 > > ESP EIP > > > > > > Begin System Thread Information > > > > # ChildEBP RetAddr > > 00 091aff10 77f43741 SharedUserData!SystemCallStub+0x4 > > 01 091aff14 77e41817 ntdll!ZwWaitForSingleObject+0xc > > 02 091aff84 77e4168f kernel32!WaitForSingleObjectEx+0xac > > 03 091aff94 792e91e0 kernel32!WaitForSingleObject+0xf > > 04 091affb8 77e4a990 mscorwks!ThreadpoolMgr::WorkerThreadStart+0x3a > > 05 091affec 00000000 kernel32!BaseThreadStart+0x34 > > > > > > > > > > Thread ID: 20 > > System Thread ID: 454 > > Kernel Time: 0:0:0.0 > > User Time: 0:0:0.0 > > Thread Type: Other > > # ChildEBP RetAddr > > 00 0a8fff7c 77f430c7 SharedUserData!SystemCallStub+0x4 > > 01 0a8fff80 71b246f7 ntdll!ZwRemoveIoCompletion+0xc > > 02 0a8fffb8 77e4a990 mswsock!SockAsyncThread+0x67 > > 03 0a8fffec 00000000 kernel32!BaseThreadStart+0x34 > > > > Closing open log file D:\iisstate\output\IISState-8504.log > > > > > >
- Next message: Peter Yohe: "Directory Names with Executable Extensions..."
- Previous message: Ken Schaefer: "Re: NTFS deny permissions"
- In reply to: Pat [MSFT]: "Re: IISState, need help finding info"
- Next in thread: Pat [MSFT]: "Re: IISState, need help finding info"
- Reply: Pat [MSFT]: "Re: IISState, need help finding info"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|