Re: High CPU Utilization for INETINFO.EXE

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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

Date: Sun, 23 May 2004 22:28:14 -0700

Basically, it looks like MDAC is not behaving especially well. I would
start by upgrading to the latest MDAC (www.microsoft.com/data) and see if
that helps.

Pat

"Mathew Lee" <mathew.lee@atosorigin.com> wrote in message
news:ur2QCZUQEHA.3944@tk2msftngp13.phx.gbl...
> Pat,
>
> IISState had downloaded the symbols and problem had happened again. I
> have extract the threads with more than one minute user or kernal times.
> Please see below for the IISState.log. Is the lock mentioned in the log
> file related to database locking? Thanks a lot.
>
> ***********************
> Starting new log output
> IISState version 3.2
>
> Mon May 24 10:59:25 2004
>
> OS = Windows 2000
> Executable: inetinfo.exe
> PID = 1336
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
>
>
> Thread ID: 29
> System Thread ID: 92c
> Kernel Time: 0:1:4.734
> User Time: 0:4:44.890
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
> for C:\Program Files\Common Files\System\OLE DB\oledb32.dll -
> Thread Type: Other
> # ChildEBP RetAddr
> 00 02f3ea6c 77db810b ntdll!NtClose+0xb
> 01 02f3ea7c 77db80d1 ADVAPI32!BaseRegCloseKeyInternal+0x4f
> 02 02f3ea84 77db819a ADVAPI32!LocalBaseRegCloseKey+0x9
> 03 02f3ea8c 1f89da57 ADVAPI32!RegCloseKey+0x74
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 04 02f3eb4c 77a98a25 oledb32!DllGetClassObject+0xbd2d
> 05 00000078 00000000 ole32!GetCurrentApartmentId+0x42
>
>
>
>
> Thread ID: 49
> System Thread ID: 188
> Kernel Time: 0:2:1.15
> User Time: 0:6:54.375
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
> for C:\Program Files\Common Files\System\ADO\msado15.dll -
> 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 0af2e948 77f8f1e5 ntdll!NtWaitForSingleObject+0xb
> 01 0af2e9bc 77f87e86 ntdll!RtlpWaitForCriticalSection+0x9e
> 02 0af2e9c4 77fc8d7e ntdll!RtlEnterCriticalSection+0x46
> 03 0af2eb68 77a652d2 ntdll!RtlAllocateHeap+0xfe
> 04 0af2eb78 77a0f8cd ole32!CRetailMalloc_Alloc+0x12
> 05 0af2eb88 779d90f0 OLEAUT32!APP_DATA::AllocCachedMem+0x42
> 06 0af2eba0 779d907f OLEAUT32!SysAllocStringLen+0x60
> 07 0af2ebb0 1f8a6ae4 OLEAUT32!SysAllocString+0x1f
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 08 0af2f3dc 1f46edd8 oledb32!DllCanUnloadNow+0x1da0
> 09 0af2f3f8 1f45f484 msado15!DllCanUnloadNow+0x1283f
> 0a 0af2f50c 000c0003 msado15!DllCanUnloadNow+0x2eeb
> 0b 00000409 00000000 0xc0003
>
>
>
>
> Thread ID: 51
> System Thread ID: 5e8
> Kernel Time: 0:2:22.578
> User Time: 0:4:57.296
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
> for C:\WINNT\System32\vbscript.dll -
> 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: ASP
> Executing Page:
>
> # ChildEBP RetAddr
> 00 0b1dea28 77f8f1e5 ntdll!NtWaitForSingleObject+0xb
> 01 0b1dea9c 77f87e86 ntdll!RtlpWaitForCriticalSection+0x9e
> 02 0b1deaa4 77fc8d7e ntdll!RtlEnterCriticalSection+0x46
> 03 0b1dec48 77a652d2 ntdll!RtlAllocateHeap+0xfe
> 04 0b1dec58 77a0f8cd ole32!CRetailMalloc_Alloc+0x12
> 05 0b1dec68 779d90f0 OLEAUT32!APP_DATA::AllocCachedMem+0x42
> 06 0b1dec80 779d907f OLEAUT32!SysAllocStringLen+0x60
> 07 0b1dec90 1f8b6df7 OLEAUT32!SysAllocString+0x1f
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 08 0b1decb8 1f46ede5 oledb32!DllMain+0xd769
> 09 0b1decd4 1f45fa04 msado15!DllCanUnloadNow+0x1284c
> 0a 0b1df0fc 73595fef msado15!DllCanUnloadNow+0x346b
> 0b 0b1df150 73589530 vbscript!DllRegisterServer+0x3ec5
> 0c 0b1df19c 73573e07 vbscript!DllGetClassObject+0x110b4
> 0d 0b1df2b0 73573936 vbscript!DllCanUnloadNow+0x2794
> 0e 0b1df2d4 73575877 vbscript!DllCanUnloadNow+0x22c3
> 0f 0b1df5b0 73574380 vbscript!DllCanUnloadNow+0x4204
> 10 0b1df6b4 7357c7c1 vbscript!DllCanUnloadNow+0x2d0d
> 11 0b1df988 73574380 vbscript!DllGetClassObject+0x4345
> 12 0b1dfa8c 7357444c vbscript!DllCanUnloadNow+0x2d0d
> 13 0b1dfaf0 73574746 vbscript!DllCanUnloadNow+0x2dd9
> 14 0b1dfb40 735747b3 vbscript!DllCanUnloadNow+0x30d3
> 15 0b1dfb5c 749f6140 vbscript!DllCanUnloadNow+0x3140
> 16 0b1dfb8c 74a22af3 asp!CActiveScriptEngine::TryCall+0x15
> 17 0b1dfbd0 749f60cd asp!CActiveScriptEngine::Call+0x4d
> 18 0b1dfbdc 749f6982 asp!CallScriptFunctionOfEngine+0x48
> 19 0b1dfc18 749f377d asp!ExecuteRequest+0x19e
> 1a 0b1dfc60 749f8e0e asp!Execute+0x17e
> 1b 0b1dfcb0 749f8ab2 asp!CHitObj::ViperAsyncCallback+0x452
> 1c 0b1dfcc8 695707da asp!CViperAsyncRequest::OnCall+0x3f
> 1d 0b1dfcd0 77aa1dc5 comsvcs!STAActivityWorkHelper+0xa
> 1e 0b1dfd14 77aa1be9 ole32!EnterForCallback+0x6a
> 1f 0b1dfe40 77aa1aac ole32!SwitchForCallback+0x12b
> 20 0b1dfe68 77aa64f4 ole32!PerformCallback+0x50
> 21 0b1dfed4 77aa634d ole32!CObjectContext::InternalContextCallback+0x10d
> 22 0b1dfef4 6956d7f3 ole32!CObjectContext::DoCallback+0x1a
> 23 0b1dff24 6956f6c3 comsvcs!STAActivityWork::DoWork+0x73
> 24 0b1dffb4 77e8758a comsvcs!STAThread::STAThreadWorker+0x2bb
> 25 0b1dffec 00000000 KERNEL32!BaseThreadStart+0x52
>
>
>
>
> Thread ID: 55
> System Thread ID: 83c
> Kernel Time: 0:2:13.390
> User Time: 0:4:39.312
> Thread Type: ASP
> Executing Page:
>
> # ChildEBP RetAddr
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 00 0e9aeaf0 779d1145 oledb32!DllGetClassObject+0x38a
> 01 0e9aeb04 1f49e27f OLEAUT32!SetErrorInfo+0x25
> 02 0e9aeb68 1f46ead2 msado15!DllRegisterServer+0x2a02
> 03 0e9aecc0 1f46246e msado15!DllCanUnloadNow+0x12539
> 04 0e9aecd4 1f45fa04 msado15!DllCanUnloadNow+0x5ed5
> 05 0e9af0fc 73595fef msado15!DllCanUnloadNow+0x346b
> 06 0e9af150 73589530 vbscript!DllRegisterServer+0x3ec5
> 07 0e9af19c 73573e07 vbscript!DllGetClassObject+0x110b4
> 08 0e9af2b0 73573936 vbscript!DllCanUnloadNow+0x2794
> 09 0e9af2d4 73575877 vbscript!DllCanUnloadNow+0x22c3
> 0a 0e9af5b0 73574380 vbscript!DllCanUnloadNow+0x4204
> 0b 0e9af6b4 7357c7c1 vbscript!DllCanUnloadNow+0x2d0d
> 0c 0e9af988 73574380 vbscript!DllGetClassObject+0x4345
> 0d 0e9afa8c 7357444c vbscript!DllCanUnloadNow+0x2d0d
> 0e 0e9afaf0 73574746 vbscript!DllCanUnloadNow+0x2dd9
> 0f 0e9afb40 735747b3 vbscript!DllCanUnloadNow+0x30d3
> 10 0e9afb5c 749f6140 vbscript!DllCanUnloadNow+0x3140
> 11 0e9afb8c 74a22af3 asp!CActiveScriptEngine::TryCall+0x15
> 12 0e9afbd0 749f60cd asp!CActiveScriptEngine::Call+0x4d
> 13 0e9afbdc 749f6982 asp!CallScriptFunctionOfEngine+0x48
> 14 0e9afc18 749f377d asp!ExecuteRequest+0x19e
> 15 0e9afc60 749f8e0e asp!Execute+0x17e
> 16 0e9afcb0 749f8ab2 asp!CHitObj::ViperAsyncCallback+0x452
> 17 0e9afcc8 695707da asp!CViperAsyncRequest::OnCall+0x3f
> 18 0e9afcd0 77aa1dc5 comsvcs!STAActivityWorkHelper+0xa
> 19 0e9afd14 77aa1be9 ole32!EnterForCallback+0x6a
> 1a 0e9afe40 77aa1aac ole32!SwitchForCallback+0x12b
> 1b 0e9afe68 77aa64f4 ole32!PerformCallback+0x50
> 1c 0e9afed4 77aa634d ole32!CObjectContext::InternalContextCallback+0x10d
> 1d 0e9afef4 6956d7f3 ole32!CObjectContext::DoCallback+0x1a
> 1e 0e9aff24 6956f6c3 comsvcs!STAActivityWork::DoWork+0x73
> 1f 0e9affb4 77e8758a comsvcs!STAThread::STAThreadWorker+0x2bb
> 20 0e9affec 00000000 KERNEL32!BaseThreadStart+0x52
>
>
>
>
> Thread ID: 57
> System Thread ID: 990
> Kernel Time: 0:1:20.656
> User Time: 0:1:51.921
> 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: ASP
> Executing Page:
>
> # ChildEBP RetAddr
> 00 0f50f444 77f8f1e5 ntdll!NtWaitForSingleObject+0xb
> 01 0f50f4b8 77f87e86 ntdll!RtlpWaitForCriticalSection+0x9e
> 02 0f50f4c0 77fa4c82 ntdll!RtlEnterCriticalSection+0x46
> 03 0f50f64c 77a69220 ntdll!RtlReAllocateHeap+0xf2
> 04 0f50f668 779da0a7 ole32!CRetailMalloc_Realloc+0x23
> 05 0f50f69c 735ac7c0 OLEAUT32!SafeArrayRedim+0x1c7
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 06 0f50f6bc 73572740 vbscript!DllRegisterServer+0x1a696
> 07 0f50f988 73574380 vbscript!DllCanUnloadNow+0x10cd
> 08 0f50fa8c 7357444c vbscript!DllCanUnloadNow+0x2d0d
> 09 0f50faf0 73574746 vbscript!DllCanUnloadNow+0x2dd9
> 0a 0f50fb40 735747b3 vbscript!DllCanUnloadNow+0x30d3
> 0b 0f50fb5c 749f6140 vbscript!DllCanUnloadNow+0x3140
> 0c 0f50fb8c 74a22af3 asp!CActiveScriptEngine::TryCall+0x15
> 0d 0f50fbd0 749f60cd asp!CActiveScriptEngine::Call+0x4d
> 0e 0f50fbdc 749f6982 asp!CallScriptFunctionOfEngine+0x48
> 0f 0f50fc18 749f377d asp!ExecuteRequest+0x19e
> 10 0f50fc60 749f8e0e asp!Execute+0x17e
> 11 0f50fcb0 749f8ab2 asp!CHitObj::ViperAsyncCallback+0x452
> 12 0f50fcc8 695707da asp!CViperAsyncRequest::OnCall+0x3f
> 13 0f50fcd0 77aa1dc5 comsvcs!STAActivityWorkHelper+0xa
> 14 0f50fd14 77aa1be9 ole32!EnterForCallback+0x6a
> 15 0f50fe40 77aa1aac ole32!SwitchForCallback+0x12b
> 16 0f50fe68 77aa64f4 ole32!PerformCallback+0x50
> 17 0f50fed4 77aa634d ole32!CObjectContext::InternalContextCallback+0x10d
> 18 0f50fef4 6956d7f3 ole32!CObjectContext::DoCallback+0x1a
> 19 0f50ff24 6956f6c3 comsvcs!STAActivityWork::DoWork+0x73
> 1a 0f50ffb4 77e8758a comsvcs!STAThread::STAThreadWorker+0x2bb
> 1b 0f50ffec 00000000 KERNEL32!BaseThreadStart+0x52
>
>
>
>
> *****
>
> Dump name is formatted as: PID-Timestamp.dmp
>
> Creating Y:\app\iisstate\output\1336-1085367592.dmp - mini user dump
>
> *****
>
> Closing open log file Y:\app\iisstate\output\IISState-1336.log
>
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

Relevant Pages

  • IISState log help
    ... I do notice that quite a few threads have this message: "Thread is waiting ... Looking for lock owner. ... System Thread ID: 8a8 ... Stack unwind information not available. ...
    (microsoft.public.inetserver.iis)
  • Re: High CPU Utilization for INETINFO.EXE
    ... WARNING: Stack unwind information not available. ... Following frames may be ... Thread is waiting for a lock to be released. ...
    (microsoft.public.inetserver.iis)
  • Re: IISState any idease what some of the following might indicate? - page4
    ... Thread is waiting for a lock to be released. ... > # ChildEBP RetAddr ... Stack unwind information not available. ... > System Thread ID: cb8 ...
    (microsoft.public.inetserver.iis)
  • Re: major iis5 asp performance problems
    ... WARNING: Stack unwind information not available. ... Following frames may be ... Kernel Time: 0:0:0.0 ...
    (microsoft.public.inetserver.iis)
  • Re: High CPU Utilization for INETINFO.EXE
    ... > System Thread ID: 538 ... > WARNING: Stack unwind information not available. ... > frames may be wrong. ...
    (microsoft.public.inetserver.iis)