Please help - ASP consitently hangs on W2003 / IIS6

TheMSsForum.com: The Microsoft Software Forum

Hi all,

Our problem is that ASP/COM+ hangs about twice a day. COM+ and the simplest
ASP pages do not respond. We can't even call CreateObject on this COM+ app or
open even the dumbest ASP in this app (other applications in the same
DefaultAppPool work fine). When we kill COM+ app (can't shutdown from the
Components MMC, it also hangs) - everything goes back to normal.

IISState log attached below.

More details:

We have several Windows 2003 computers (2 in QA and 1 production). We have a
large ASP/COM+/SQL Server application that's quite stable on Windows 2000.
The sameapplication was more than stable in QA with Windows 2003, except the
"object cannot be created" problem, which was fixed in SP1-Beta. Since
SP1-Beta we haven't experienced any problem with Windows 2003 till we have
installed the final release of Windows 2003 SP1. All 3 computers hang
consistently twice a day at least!!

PLEASE HELP!

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

***********************
Starting new log output
IISState version 3.4

Sun May 29 14:27:39 2005

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

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

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




Thread ID: 0
System Thread ID: b30
Kernel Time: 0:0:0.171
User Time: 0:0:0.31
Thread Status: Thread is in a WAIT state.
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 0006fc08 7c822124 ntdll!KiFastSystemCallRet
01 0006fc0c 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0006fc7c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0006fc90 5a36467a kernel32!WaitForSingleObject+0x12
04 0006fca0 5a366e63 w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
05 0006fca8 5a3af41d w3dt!UlAtqStartListen+0x2d
06 0006fcb8 5a3bc259 w3core!W3_SERVER::StartListen+0xbd
07 0006ff0c 0100187c w3core!UlW3Start+0x26e
08 0006ff44 01001a23 w3wp!wmain+0x22a
09 0006ffc0 77e523cd w3wp!wmainCRTStartup+0x12b
0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23




Thread ID: 1
System Thread ID: b00
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 009fff9c 7c821364 ntdll!KiFastSystemCallRet
01 009fffa0 7c81fe26 ntdll!NtDelayExecution+0xc
02 009fffb8 77e66063 ntdll!RtlpTimerThread+0x47
03 009fffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 2
System Thread ID: b14
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00a3ff70 7c821bf4 ntdll!KiFastSystemCallRet
01 00a3ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
02 00a3ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
03 00a3ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 3
System Thread ID: 2d0
Kernel Time: 0:0:0.62
User Time: 0:0:0.0
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00ccff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00ccff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00ccff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00ccff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 00ccffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 00ccffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 00ccffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 4
System Thread ID: db4
Kernel Time: 0:0:0.46
User Time: 0:0:0.0
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d0ff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00d0ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00d0ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00d0ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 00d0ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 00d0ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 00d0ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 5
System Thread ID: aa0
Kernel Time: 0:0:0.468
User Time: 0:0:0.62
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d4ff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00d4ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00d4ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00d4ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 00d4ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 00d4ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 6
System Thread ID: 740
Kernel Time: 0:0:0.218
User Time: 0:0:0.15
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d8ff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00d8ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00d8ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00d8ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 00d8ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 00d8ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 00d8ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 7
System Thread ID: 3f4
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 00e4fcec 7c822114 ntdll!KiFastSystemCallRet
01 00e4fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
02 00e4ffb8 77e66063 ntdll!RtlpWaitThread+0x161
03 00e4ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 8
System Thread ID: fa4
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 017dfa84 7c822124 ntdll!KiFastSystemCallRet
01 017dfa88 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 017dfaf8 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 017dfb0c 5a3b8147 kernel32!WaitForSingleObject+0x12
04 017dffb8 77e66063 w3core!HTTP_COMPRESSION::CompressionThread+0x126
05 017dffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 9
System Thread ID: ef0
Kernel Time: 0:0:0.15
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: Unable to locate ASP page

No remote call being made

# ChildEBP RetAddr
00 0181fe18 7c821c54 ntdll!KiFastSystemCallRet
01 0181fe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
02 0181ff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
03 0181ff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
04 0181ffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
05 0181ffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
06 0181ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 10
System Thread ID: 450
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0185ff8c 7c821364 ntdll!KiFastSystemCallRet
01 0185ff90 7c815267 ntdll!NtDelayExecution+0xc
02 0185ffb8 77e66063 ntdll!RtlpIOWorkerThread+0x3f
03 0185ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 11
System Thread ID: e00
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 018efee8 7c822124 ntdll!KiFastSystemCallRet
01 018efeec 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 018eff5c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 018eff70 75bd4dc8 kernel32!WaitForSingleObject+0x12
04 018eff84 77bcb530 comsvcs!CSTAThreadPool::LoadBalanceThreadControlLoop+0x29
05 018effb8 77e66063 msvcrt!_endthreadex+0xa3
06 018effec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 12
System Thread ID: 9d0
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0192fee0 7c822124 ntdll!KiFastSystemCallRet
01 0192fee4 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0192ff54 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0192ff68 75bd4843 kernel32!WaitForSingleObject+0x12
04 0192ff84 77bcb530 comsvcs!CSTAThreadPool::KillThreadControlLoop+0x25
05 0192ffb8 77e66063 msvcrt!_endthreadex+0xa3
06 0192ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 13
System Thread ID: b48
Kernel Time: 0:0:0.62
User Time: 0:0:0.62
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0196fe78 00000000 ntdll!KiFastSystemCallRet
GetContextState failed, 0x8007001F
GetContextState failed, 0x8007001F
GetContextState failed, 0x8007001F




Thread ID: 14
System Thread ID: 0
Kernel Time: 0:0:0.46
User Time: 0:0:0.62
GetContextState failed, 0x8007001F
Top

Re: Please help - ASP consitently hangs on W2003 / IIS6 by Pat

Pat
Mon May 30 00:07:33 CDT 2005

Looks like the process recycled before IISState could get the log. You'll
need to try again for a good reading.

pat

"Anton Bar" <AntonBar@discussions.microsoft.com> wrote in message
news:42F1E4B8-BC9B-4B1B-9DA7-5A68E5E03B35@microsoft.com...
> Hi all,
>
> Our problem is that ASP/COM+ hangs about twice a day. COM+ and the
> simplest
> ASP pages do not respond. We can't even call CreateObject on this COM+ app
> or
> open even the dumbest ASP in this app (other applications in the same
> DefaultAppPool work fine). When we kill COM+ app (can't shutdown from the
> Components MMC, it also hangs) - everything goes back to normal.
>
> IISState log attached below.
>
> More details:
>
> We have several Windows 2003 computers (2 in QA and 1 production). We have
> a
> large ASP/COM+/SQL Server application that's quite stable on Windows 2000.
> The sameapplication was more than stable in QA with Windows 2003, except
> the
> "object cannot be created" problem, which was fixed in SP1-Beta. Since
> SP1-Beta we haven't experienced any problem with Windows 2003 till we have
> installed the final release of Windows 2003 SP1. All 3 computers hang
> consistently twice a day at least!!
>
> PLEASE HELP!
>
> ============================================
> Opened log file 'C:\iisstate\output\IISState-3340.log'
>
> ***********************
> Starting new log output
> IISState version 3.4
>
> Sun May 29 14:27:39 2005
>
> OS = Windows 2003 Server
> Executable: w3wp.exe
> PID = 3340
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
>
>
> Thread ID: 0
> System Thread ID: b30
> Kernel Time: 0:0:0.171
> User Time: 0:0:0.31
> Thread Status: Thread is in a WAIT state.
> Thread Type: HTTP Compression Thread
> # ChildEBP RetAddr
> 00 0006fc08 7c822124 ntdll!KiFastSystemCallRet
> 01 0006fc0c 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0006fc7c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0006fc90 5a36467a kernel32!WaitForSingleObject+0x12
> 04 0006fca0 5a366e63 w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
> 05 0006fca8 5a3af41d w3dt!UlAtqStartListen+0x2d
> 06 0006fcb8 5a3bc259 w3core!W3_SERVER::StartListen+0xbd
> 07 0006ff0c 0100187c w3core!UlW3Start+0x26e
> 08 0006ff44 01001a23 w3wp!wmain+0x22a
> 09 0006ffc0 77e523cd w3wp!wmainCRTStartup+0x12b
> 0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
>
>
>
> Thread ID: 1
> System Thread ID: b00
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 009fff9c 7c821364 ntdll!KiFastSystemCallRet
> 01 009fffa0 7c81fe26 ntdll!NtDelayExecution+0xc
> 02 009fffb8 77e66063 ntdll!RtlpTimerThread+0x47
> 03 009fffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 2
> System Thread ID: b14
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00a3ff70 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00a3ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
> 02 00a3ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
> 03 00a3ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 3
> System Thread ID: 2d0
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.0
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00ccff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00ccff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00ccff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00ccff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00ccffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00ccffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00ccffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 4
> System Thread ID: db4
> Kernel Time: 0:0:0.46
> User Time: 0:0:0.0
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00d0ff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00d0ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00d0ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00d0ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00d0ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00d0ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00d0ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 5
> System Thread ID: aa0
> Kernel Time: 0:0:0.468
> User Time: 0:0:0.62
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00d4ff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00d4ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00d4ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00d4ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00d4ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00d4ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 6
> System Thread ID: 740
> Kernel Time: 0:0:0.218
> User Time: 0:0:0.15
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00d8ff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00d8ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00d8ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00d8ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00d8ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00d8ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00d8ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 7
> System Thread ID: 3f4
> 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 00e4fcec 7c822114 ntdll!KiFastSystemCallRet
> 01 00e4fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
> 02 00e4ffb8 77e66063 ntdll!RtlpWaitThread+0x161
> 03 00e4ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 8
> System Thread ID: fa4
> 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 017dfa84 7c822124 ntdll!KiFastSystemCallRet
> 01 017dfa88 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 017dfaf8 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 017dfb0c 5a3b8147 kernel32!WaitForSingleObject+0x12
> 04 017dffb8 77e66063 w3core!HTTP_COMPRESSION::CompressionThread+0x126
> 05 017dffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 9
> System Thread ID: ef0
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.0
> Thread Type: Possible ASP page. Possible DCOM activity
> Executing Page: Unable to locate ASP page
>
> No remote call being made
>
> # ChildEBP RetAddr
> 00 0181fe18 7c821c54 ntdll!KiFastSystemCallRet
> 01 0181fe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
> 02 0181ff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> 03 0181ff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
> 04 0181ffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
> 05 0181ffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
> 06 0181ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 10
> System Thread ID: 450
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0185ff8c 7c821364 ntdll!KiFastSystemCallRet
> 01 0185ff90 7c815267 ntdll!NtDelayExecution+0xc
> 02 0185ffb8 77e66063 ntdll!RtlpIOWorkerThread+0x3f
> 03 0185ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 11
> System Thread ID: e00
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 018efee8 7c822124 ntdll!KiFastSystemCallRet
> 01 018efeec 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 018eff5c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 018eff70 75bd4dc8 kernel32!WaitForSingleObject+0x12
> 04 018eff84 77bcb530
> comsvcs!CSTAThreadPool::LoadBalanceThreadControlLoop+0x29
> 05 018effb8 77e66063 msvcrt!_endthreadex+0xa3
> 06 018effec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 12
> System Thread ID: 9d0
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 0192fee0 7c822124 ntdll!KiFastSystemCallRet
> 01 0192fee4 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0192ff54 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0192ff68 75bd4843 kernel32!WaitForSingleObject+0x12
> 04 0192ff84 77bcb530 comsvcs!CSTAThreadPool::KillThreadControlLoop+0x25
> 05 0192ffb8 77e66063 msvcrt!_endthreadex+0xa3
> 06 0192ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 13
> System Thread ID: b48
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.62
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0196fe78 00000000 ntdll!KiFastSystemCallRet
> GetContextState failed, 0x8007001F
> GetContextState failed, 0x8007001F
> GetContextState failed, 0x8007001F
>
>
>
>
> Thread ID: 14
> System Thread ID: 0
> Kernel Time: 0:0:0.46
> User Time: 0:0:0.62
> GetContextState failed, 0x8007001F
>


Top

Re: Please help - ASP consitently hangs on W2003 / IIS6 by Dev

Dev
Fri Jun 03 13:01:55 CDT 2005


Anton,

While you are diagnosing the problem you might want to
take advantage of our server restarter, ReJuvin8. It's
free for the first 15-days. That's enough for some.
Its all software, you can download and use it today.

It monitors both websites and processes generally. It
sends out phone and e-mail alerts when things hang
up. It can also restart and optionally re-boot your
server. Also has neat HTML graphic status views.


For ReJuvin8, Version 4.1 of June 2005:
http://www.rejuvin8.net?ac=ch1




Also, see it, with ratings, at
http://www.hotscripts.com/Detailed/29029.html



ReJuvin8. Since 2002.

Keywords: hung server, server hangs, server crash,
website crash

==========================================
"Anton Bar" <AntonBar@discussions.microsoft.com> wrote in message
news:42F1E4B8-BC9B-4B1B-9DA7-5A68E5E03B35@microsoft.com...
> Hi all,
>
> Our problem is that ASP/COM+ hangs about twice a day. COM+ and the
simplest
> ASP pages do not respond. We can't even call CreateObject on this COM+ app
or
> open even the dumbest ASP in this app (other applications in the same
> DefaultAppPool work fine). When we kill COM+ app (can't shutdown from the
> Components MMC, it also hangs) - everything goes back to normal.
>
> IISState log attached below.
>
> More details:
>
> We have several Windows 2003 computers (2 in QA and 1 production). We have
a
> large ASP/COM+/SQL Server application that's quite stable on Windows 2000.
> The sameapplication was more than stable in QA with Windows 2003, except
the
> "object cannot be created" problem, which was fixed in SP1-Beta. Since
> SP1-Beta we haven't experienced any problem with Windows 2003 till we have
> installed the final release of Windows 2003 SP1. All 3 computers hang
> consistently twice a day at least!!
>
> PLEASE HELP!
>
> ============================================
> Opened log file 'C:\iisstate\output\IISState-3340.log'
>
> ***********************
> Starting new log output
> IISState version 3.4
>
> Sun May 29 14:27:39 2005
>
> OS = Windows 2003 Server
> Executable: w3wp.exe
> PID = 3340
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
>
>
> Thread ID: 0
> System Thread ID: b30
> Kernel Time: 0:0:0.171
> User Time: 0:0:0.31
> Thread Status: Thread is in a WAIT state.
> Thread Type: HTTP Compression Thread
> # ChildEBP RetAddr
> 00 0006fc08 7c822124 ntdll!KiFastSystemCallRet
> 01 0006fc0c 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0006fc7c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0006fc90 5a36467a kernel32!WaitForSingleObject+0x12
> 04 0006fca0 5a366e63 w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
> 05 0006fca8 5a3af41d w3dt!UlAtqStartListen+0x2d
> 06 0006fcb8 5a3bc259 w3core!W3_SERVER::StartListen+0xbd
> 07 0006ff0c 0100187c w3core!UlW3Start+0x26e
> 08 0006ff44 01001a23 w3wp!wmain+0x22a
> 09 0006ffc0 77e523cd w3wp!wmainCRTStartup+0x12b
> 0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
>
>
>
> Thread ID: 1
> System Thread ID: b00
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 009fff9c 7c821364 ntdll!KiFastSystemCallRet
> 01 009fffa0 7c81fe26 ntdll!NtDelayExecution+0xc
> 02 009fffb8 77e66063 ntdll!RtlpTimerThread+0x47
> 03 009fffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 2
> System Thread ID: b14
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00a3ff70 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00a3ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
> 02 00a3ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
> 03 00a3ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 3
> System Thread ID: 2d0
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.0
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00ccff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00ccff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00ccff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00ccff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00ccffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00ccffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00ccffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 4
> System Thread ID: db4
> Kernel Time: 0:0:0.46
> User Time: 0:0:0.0
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00d0ff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00d0ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00d0ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00d0ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00d0ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00d0ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00d0ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 5
> System Thread ID: aa0
> Kernel Time: 0:0:0.468
> User Time: 0:0:0.62
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00d4ff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00d4ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00d4ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00d4ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00d4ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00d4ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 6
> System Thread ID: 740
> Kernel Time: 0:0:0.218
> User Time: 0:0:0.15
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00d8ff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00d8ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00d8ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00d8ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00d8ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00d8ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00d8ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 7
> System Thread ID: 3f4
> 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 00e4fcec 7c822114 ntdll!KiFastSystemCallRet
> 01 00e4fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
> 02 00e4ffb8 77e66063 ntdll!RtlpWaitThread+0x161
> 03 00e4ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 8
> System Thread ID: fa4
> 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 017dfa84 7c822124 ntdll!KiFastSystemCallRet
> 01 017dfa88 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 017dfaf8 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 017dfb0c 5a3b8147 kernel32!WaitForSingleObject+0x12
> 04 017dffb8 77e66063 w3core!HTTP_COMPRESSION::CompressionThread+0x126
> 05 017dffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 9
> System Thread ID: ef0
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.0
> Thread Type: Possible ASP page. Possible DCOM activity
> Executing Page: Unable to locate ASP page
>
> No remote call being made
>
> # ChildEBP RetAddr
> 00 0181fe18 7c821c54 ntdll!KiFastSystemCallRet
> 01 0181fe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
> 02 0181ff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> 03 0181ff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
> 04 0181ffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
> 05 0181ffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
> 06 0181ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 10
> System Thread ID: 450
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0185ff8c 7c821364 ntdll!KiFastSystemCallRet
> 01 0185ff90 7c815267 ntdll!NtDelayExecution+0xc
> 02 0185ffb8 77e66063 ntdll!RtlpIOWorkerThread+0x3f
> 03 0185ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 11
> System Thread ID: e00
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 018efee8 7c822124 ntdll!KiFastSystemCallRet
> 01 018efeec 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 018eff5c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 018eff70 75bd4dc8 kernel32!WaitForSingleObject+0x12
> 04 018eff84 77bcb530
comsvcs!CSTAThreadPool::LoadBalanceThreadControlLoop+0x29
> 05 018effb8 77e66063 msvcrt!_endthreadex+0xa3
> 06 018effec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 12
> System Thread ID: 9d0
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 0192fee0 7c822124 ntdll!KiFastSystemCallRet
> 01 0192fee4 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0192ff54 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0192ff68 75bd4843 kernel32!WaitForSingleObject+0x12
> 04 0192ff84 77bcb530 comsvcs!CSTAThreadPool::KillThreadControlLoop+0x25
> 05 0192ffb8 77e66063 msvcrt!_endthreadex+0xa3
> 06 0192ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 13
> System Thread ID: b48
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.62
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0196fe78 00000000 ntdll!KiFastSystemCallRet
> GetContextState failed, 0x8007001F
> GetContextState failed, 0x8007001F
> GetContextState failed, 0x8007001F
>
>
>
>
> Thread ID: 14
> System Thread ID: 0
> Kernel Time: 0:0:0.46
> User Time: 0:0:0.62
> GetContextState failed, 0x8007001F
>


Top