Re: IISState any idease what some of the following might indicate? - page4

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Pat [MSFT] (patfilot_at_online.microsoft.com)
Date: 04/30/04 

Date: Fri, 30 Apr 2004 16:25:20 -0700

Pretty much everything is blocked on thread 50. Evidently an error occurred
and the lock was leaked. Most likely a bug in MDAC. I would recommend
upgrading to the latest build.

Pat

"mko" <anonymous@discussions.microsoft.com> wrote in message
news:8AD79487-2538-40CA-9760-E4ABD3178374@microsoft.com...
>
>
>
> Thread ID: 42
> System Thread ID: 160
> Kernel Time: 0:0:0.15
> User Time: 0:0:57.312
> Other information: Thread is waiting for a lock to be released. Looking
>
> for lock owner.
> The owning thread is 0. This usually indicates that the lock has either
>
> been leaked or is in a 'convoy' state
> Thread Type: Other
> # ChildEBP RetAddr
> 00 04e7fa20 1f441295 ntdll!RtlEnterCriticalSection+0xbc
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 01 04e7fa4c 1f448851 msado15+0x1295
> 02 00000000 00000000 msado15!DllCanUnloadNow+0x6cd
>
>
>
>
> Thread ID: 43
> System Thread ID: cb8
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.171
> Thread Status: Thread is in a WAIT state.
> Other information: Thread is waiting for a lock to be released. Looking
>
> for lock owner.
> Owning thread System ID: 880
> Thread Type: Other
> # ChildEBP RetAddr
> 00 04ebea08 77f92387 ntdll!NtWaitForSingleObject+0xb
> 01 04ebea7c 77f922f8 ntdll!RtlpWaitForCriticalSection+0x9e
> 02 04ebea84 6b741269 ntdll!RtlEnterCriticalSection+0x46
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 03 04ebeaa0 6b7411ec MSDART32!MPInitializeCriticalSection+0x98
> 04 00000002 00000000 MSDART32!MPInitializeCriticalSection+0x1b
>
>
>
>
> Thread ID: 44
> System Thread ID: 608
> Kernel Time: 0:0:0.296
> User Time: 0:0:0.437
> Thread Status: Thread is in a WAIT state.
> Other information: Thread is waiting for a lock to be released. Looking
>
> for lock owner.
> Owning thread System ID: cb0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 04efe874 77f92387 ntdll!NtWaitForSingleObject+0xb
> 01 04efe8e8 77f922f8 ntdll!RtlpWaitForCriticalSection+0x9e
> 02 04efe8f0 6b741269 ntdll!RtlEnterCriticalSection+0x46
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 03 04efe90c 6b7411ec MSDART32!MPInitializeCriticalSection+0x98
> 04 00000000 00000000 MSDART32!MPInitializeCriticalSection+0x1b
>
>
>
>
> Thread ID: 45
> System Thread ID: c4c
> Kernel Time: 0:0:0.187
> User Time: 0:0:0.125
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 04f3fe28 7c4ebdd7 ntdll!ZwWaitForMultipleObjects+0xb
> 01 04f3fe78 77e13990 KERNEL32!WaitForMultipleObjectsEx+0xea
> 02 04f3fed4 77e13a5c USER32!MsgWaitForMultipleObjectsEx+0x153
> 03 04f3fef0 787c2885 USER32!MsgWaitForMultipleObjects+0x1d
> 04 04f3ff1c 787c1daa COMSVCS!STAThread::WaitForWork+0x37
> 05 04f3ffb4 7c4e987c COMSVCS!STAThread::STAThreadWorker+0x4b2
> 06 04f3ffec 00000000 KERNEL32!BaseThreadStart+0x52
>
>
>
>
> Thread ID: 46
> System Thread ID: 74c
> Kernel Time: 0:0:0.78
> User Time: 0:0:58.0
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>
> for C:\winnt\system32\lbs\lbs.dll -
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>
> for C:\WINNT\system32\OLEAUT32.dll -
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>
> for C:\WINNT\system32\MSVBVM60.DLL -
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>
> for -
> Other information: Thread is waiting for a lock to be released. Looking
>
> for lock owner.
> The owning thread is 0. This usually indicates that the lock has either
>
> been leaked or is in a 'convoy' state
> Thread Type: ASP
> Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> Continuing with other analysis.
>
> # ChildEBP RetAddr
> 00 04f7e75c 1f441295 ntdll!RtlEnterCriticalSection+0xb8
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 01 04f7e788 1f443668 msado15+0x1295
> 02 04f7e7ac 1f443515 msado15+0x3668
> 03 04f7e7d4 1f44844a msado15+0x3515
> 04 04f7e7f0 1f4483b5 msado15!DllCanUnloadNow+0x2c6
> 05 04f7e828 117632f4 msado15!DllCanUnloadNow+0x231
> 06 04f7e98c 11762201 lbs!DllCanUnloadNow+0x5d208a
> 07 04f7ead8 11761e67 lbs!DllCanUnloadNow+0x5d0f97
> 08 04f7ebe0 117606f0 lbs!DllCanUnloadNow+0x5d0bfd
> 09 04f7ed08 779d7d5d lbs!DllCanUnloadNow+0x5cf486
> 0a 04f7ed2c 6a9fa2fb OLEAUT32!DispCallFunc+0x15d
> 0b 04f7f688 6a9fa0f4 MSVBVM60!BASIC_CLASS_Invoke+0x259
> 0c 04f7f6e4 75a4c29c MSVBVM60!BASIC_CLASS_Invoke+0x52
> 0d 04f7f74c 75a4f45c vbscript!DllRegisterServer+0x7feb
> 0e 00000000 00000000 vbscript!DllRegisterServer+0xb1ab
>
>
>
>
> Thread ID: 47
> System Thread ID: c90
> Kernel Time: 0:0:0.375
> User Time: 0:0:0.187
> Thread Status: Thread is in a WAIT state.
> Other information: Thread is waiting for a lock to be released. Looking
>
> for lock owner.
> Owning thread System ID: cb0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 04fbea04 77f92387 ntdll!NtWaitForSingleObject+0xb
> 01 04fbea78 77f922f8 ntdll!RtlpWaitForCriticalSection+0x9e
> 02 04fbea80 6b741269 ntdll!RtlEnterCriticalSection+0x46
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 03 04fbea9c 6b7411ec MSDART32!MPInitializeCriticalSection+0x98
> 04 00000000 00000000 MSDART32!MPInitializeCriticalSection+0x1b
>
>
>
>
> Thread ID: 48
> System Thread ID: cb4
> Kernel Time: 0:0:0.156
> User Time: 0:0:0.406
> Thread Status: Thread is in a WAIT state.
> Other information: Thread is waiting for a lock to be released. Looking
>
> for lock owner.
> The owning thread is 0. This usually indicates that the lock has either
>
> been leaked or is in a 'convoy' state
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0533e224 77f92387 ntdll!NtWaitForSingleObject+0xb
> 01 0533e298 77f922f8 ntdll!RtlpWaitForCriticalSection+0x9e
> 02 0533e2a0 1f6b2008 ntdll!RtlEnterCriticalSection+0x46
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 03 0533e2c4 1f6b676f msdasql!DllGetClassObject+0x313
> 04 0533e300 1f6b65a7 msdasql!DllGetClassObject+0x4a7a
> 05 0533e3a4 1f4616c8 msdasql!DllGetClassObject+0x48b2
> 06 0533e3e4 1f454025 msado15!DllGetClassObject+0x181fc
> 07 02b86cb8 1f444720 msado15!DllGetClassObject+0xab59
> 08 1f444730 1f47e6db msado15+0x4720
> 09 1f471e12 f99ee904 msado15!com_ms_wfc_data_Field_setDataDate+0x46af
> 0a 04246c83 00000000 0xf99ee904
>
>
>
>
> Thread ID: 49
> System Thread ID: 6d0
> Kernel Time: 0:0:0.93
> User Time: 0:0:0.203
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>
> for C:\WINNT\System32\inetsrv\wam.dll -
> Thread Type: ISAPI Extension
> # ChildEBP RetAddr
> 00 0558faec 7c4ebdd7 ntdll!ZwWaitForMultipleObjects+0xb
> 01 0558fb3c 77e13990 KERNEL32!WaitForMultipleObjectsEx+0xea
> 02 0558fb98 77a5319f USER32!MsgWaitForMultipleObjectsEx+0x153
> 03 0558fbc0 77ad38fa ole32!CCliModalLoop::BlockFn+0x80
> 04 0558fc24 77ad46a0 ole32!CoWaitForMultipleHandles+0xee
> 05 0558fc74 65d85fdf ole32!CGIPTable::RevokeInterfaceFromGlobal+0xb3
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 06 0558fcc8 787c2b7a wam!BUFFER::QuerySize+0x617
> 07 0558fcd0 77acc540 COMSVCS!STAActivityWorkHelper+0xa
> 08 0558fd14 77acc3ee ole32!EnterForCallback+0x6a
> 09 0558fe40 77acc2b3 ole32!SwitchForCallback+0x12b
> 0a 0558fe68 77aaa7f9 ole32!PerformCallback+0x50
> 0b 0558fed4 77ad0404 ole32!CObjectContext::InternalContextCallback+0x10d
> 0c 0558fef4 787bfb93 ole32!CObjectContext::DoCallback+0x1a
> 0d 0558ff24 787c1bb7 COMSVCS!STAActivityWork::DoWork+0x73
> 0e 0558ffb4 7c4e987c COMSVCS!STAThread::STAThreadWorker+0x2bf
> 0f 0558ffec 00000000 KERNEL32!BaseThreadStart+0x52
>
>
>
>
> Thread ID: 50
> System Thread ID: 880
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.109
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 055cfe28 7c4ebdd7 ntdll!ZwWaitForMultipleObjects+0xb
> 01 055cfe78 77e13990 KERNEL32!WaitForMultipleObjectsEx+0xea
> 02 055cfed4 77e13a5c USER32!MsgWaitForMultipleObjectsEx+0x153
> 03 055cfef0 787c2885 USER32!MsgWaitForMultipleObjects+0x1d
> 04 055cff1c 787c1daa COMSVCS!STAThread::WaitForWork+0x37
> 05 055cffb4 7c4e987c COMSVCS!STAThread::STAThreadWorker+0x4b2
> 06 055cffec 00000000 KERNEL32!BaseThreadStart+0x52
>
>
>
>
> Thread ID: 51
> System Thread ID: b10
> Kernel Time: 0:0:0.421
> User Time: 0:0:0.375
> Thread Status: Thread is in a WAIT state.
> Other information: Thread is waiting for a lock to be released. Looking
>
> for lock owner.
> Owning thread System ID: cb0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0560e0c4 77f92387 ntdll!NtWaitForSingleObject+0xb
> 01 0560e138 77f922f8 ntdll!RtlpWaitForCriticalSection+0x9e
> 02 0560e140 6b741269 ntdll!RtlEnterCriticalSection+0x46
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 03 0560e15c 6b7411ec MSDART32!MPInitializeCriticalSection+0x98
> 04 00000000 00000000 MSDART32!MPInitializeCriticalSection+0x1b
>
>
>
>
> Thread ID: 52
> System Thread ID: 484
> Kernel Time: 0:0:0.93
> User Time: 0:0:59.171
> Other information: Thread is waiting for a lock to be released. Looking
>
> for lock owner.
> The owning thread is 0. This usually indicates that the lock has either
>
> been leaked or is in a 'convoy' state
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0564e674 1f441295 ntdll!RtlEnterCriticalSection+0xb8
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 01 0564e680 1f441959 msado15+0x1295
> 02 02c00e28 1f454de0 msado15+0x1959
> 03 02c00e28 1f454de0 msado15!DllGetClassObject+0xb914
> 04 1f454e08 1f46869b msado15!DllGetClassObject+0xb914
> 05 1f45479e 00000015 msado15!DllGetClassObject+0x1f1cf
>
>
>
>
> Thread ID: 53
> System Thread ID: b8c
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.93
> Thread Status: Thread is in a WAIT state.
> Other information: Thread is waiting for a lock to be released. Looking
>
> for lock owner.
> Owning thread System ID: 880
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0568e0c4 77f92387 ntdll!NtWaitForSingleObject+0xb
> 01 0568e138 77f922f8 ntdll!RtlpWaitForCriticalSection+0x9e
> 02 0568e140 6b741269 ntdll!RtlEnterCriticalSection+0x46
> WARNING: Stack unwind information not available. Following frames may be
>
> wrong.
> 03 0568e15c 6b7411ec MSDART32!MPInitializeCriticalSection+0x98
> 04 00000002 00000000 MSDART32!MPInitializeCriticalSection+0x1b
>
>
>
>
> Thread ID: 54
> System Thread ID: b88
> Kernel Time: 0:0:0.46
> User Time: 0:0:0.78
> Thre
>

Relevant Pages

  • Re: IISState Analysis - Many Locks
    ... The lock that is owned is the LoaderLock so, any thread that is trying to ... > System Thread ID: 6f8 ... > Thread Type: Other ... > # ChildEBP RetAddr ...
    (microsoft.public.inetserver.iis)
  • Re: IISstate issues...
    ... > System Thread ID: 5dc ... > Thread Type: HTTP Compression Thread ... > # ChildEBP RetAddr ... Thread is waiting for a lock to be released. ...
    (microsoft.public.inetserver.iis)
  • Re: IISstate log
    ... > Thread Type: Other ... > # ChildEBP RetAddr ... > System Thread ID: c50 ... Thread is waiting for a lock to be released. ...
    (microsoft.public.inetserver.iis)
  • Re: ASP.NET Application Hanging
    ... can't release the lock until thread 27 releases its lock. ... > System Thread ID: 678 ... > Thread Type: HTTP Compression Thread ... > # ChildEBP RetAddr ...
    (microsoft.public.inetserver.iis)
  • Re: IISState log help
    ... > System Thread ID: 6c4 ... > Thread Type: Other ... > # ChildEBP RetAddr ... >> lock owner. ...
    (microsoft.public.inetserver.iis)