IIS Hang

I've been having some issues with IIS where it pins the processor
until the app pool is recycled. This sequence of events from an IIS
State log seems to be the culprit every time:

Thread ID: 29
System Thread ID: 16d4
Kernel Time: 0:0:6.218
User Time: 1:45:8.500
Thread Type: ASP

# ChildEBP RetAddr
00 0b57df30 7357c7f6 MSVBVM60!
_COLE2TEMPLATE_vtbl::put__AUTOVERBMENUIPROP_CLIENT+0x7
01 0b57df98 7363bc3a MSVBVM60!VBDataObjectFiles::`vftable'+0x36
02 0b57e24c 735e2b6e MSVBVM60!EpiInvokeMethod+0x441
03 0b57e288 735e8642 MSVBVM60!FORM::LoadProp+0x1d
04 0b57e384 735e8226 MSVBVM60!CTLUSER::GetPropA+0x88
05 0b57e3c0 776b13af MSVBVM60!CTLUSER::SetPropA+0x26
06 0b57e4b0 776b1275 ole32!ICoCreateInstanceEx+0xcb
07 0b57e4d8 776b1244 ole32!CComActivator::DoCreateInstance+0x28
08 0b57e4fc 73653937 ole32!CoCreateInstanceEx+0x23
09 0b57e56c 73675e68 MSVBVM60!qsort+0xb7
0a 0b57e584 73675e98 MSVBVM60!Adjustor954
0b 0b57e5c4 73671ce7 MSVBVM60!Adjustor960
0c 0b57e6dc 77d06de9 MSVBVM60!lblEX_ThisVCallR8+0x4f
0d 0b57e6f8 73646a6f OLEAUT32!DispCallFunc+0x16a
0e 0b57f054 7363a0d4 MSVBVM60!VBStrToLong+0xcf
0f 0b57f0b0 70a146eb MSVBVM60!rtFindFirstFile+0x185
10 0b57f13c 70a14968 asp!CPageObject::TryInvokeMethod+0x73
11 0b57f188 70a01594 asp!CPageObject::InvokeMethod+0x4c
12 0b57f1d8 709ee237 asp!CPageComponentManager::OnStartPage+0x1a4
13 0b57f200 709f76ff asp!
CPageComponentManager::AddScopedUnnamedInstantiated+0xb6
14 0b57f24c 709ee04c asp!CTypelibCache::CreateComponent+0x13b
15 0b57f28c 77d06de9 asp!CServer::CreateObject+0x66
16 0b57f2ac 77d06c80 OLEAUT32!DispCallFunc+0x16a
17 0b57f33c 709edf7d OLEAUT32!CTypeInfo2::Invoke+0x234
18 0b57f364 73469f71 asp!CDispatchImpl<IServer>::Invoke+0x55
19 0b57f3b8 73468f37 vbscript!CatchIDispatchInvoke+0x46
1a 0b57f3f8 73468ea6 vbscript!IDispatchInvoke2+0xaf
1b 0b57f434 73469000 vbscript!IDispatchInvoke+0x59
1c 0b57f548 73467bb6 vbscript!InvokeDispatch+0x13a
1d 0b57f56c 73468fbd vbscript!InvokeByName+0x42
1e 0b57f848 73464940 vbscript!CScriptRuntime::Run+0x2581
1f 0b57f940 73464cd2 vbscript!CScriptEntryPoint::Call+0x5c
20 0b57f998 73465522 vbscript!CSession::Execute+0xb4
21 0b57f9e8 7346189b vbscript!COleScript::ExecutePendingScripts+0x13e
22 0b57fa04 709e2f5a vbscript!COleScript::SetScriptState+0x150
23 0b57fa30 709e2f1a asp!CActiveScriptEngine::TryCall+0x19
24 0b57fa6c 709e2e50 asp!CActiveScriptEngine::Call+0x31
25 0b57fa88 709e2d54 asp!CallScriptFunctionOfEngine+0x5b
26 0b57fadc 709e2c7f asp!ExecuteRequest+0x17e
27 0b57fb44 709e2a4d asp!Execute+0x249
28 0b57fb98 709e271a asp!CHitObj::ViperAsyncCallback+0x3e8
29 0b57fbb4 75bd72a5 asp!CViperAsyncRequest::OnCall+0x92
2a 0b57fbd0 7770f0eb comsvcs!CSTAActivityWork::STAActivityWorkHelper
+0x32
2b 0b57fc1c 7770fb38 ole32!EnterForCallback+0xc4
2c 0b57fd7c 77710042 ole32!SwitchForCallback+0x1a3
2d 0b57fda8 77694098 ole32!PerformCallback+0x54
2e 0b57fe40 777127fd ole32!CObjectContext::InternalContextCallback
+0x159
2f 0b57fe60 75bd7649 ole32!CObjectContext::DoCallback+0x1c
30 0b57fecc 75bd79a5 comsvcs!CSTAActivityWork::DoWork+0x12d
31 0b57fee4 75bd833e comsvcs!CSTAThread::DoWork+0x18

Does this look familiar to anyone? Thanks in advance.

Pat
Thu May 01 15:35:45 CDT 2008

The symbols for MSVBVM60.dll are wrong - so ignore the function names. That
said, it appears that one of two things is happening:

1) The ASP page is looping through a CreateObject/Server.CreateObject for a
VB COM dll (i.e. the bug is in the ASP script)

or

2) There is a bug in the VB runtime (MSVBVM60.dll) that is causing it to
loop during the COM initialization

Probably the easiest thing to try for isolating the issue would be to create
a Server Package and put the VB DLL in question there. This will 'split'
the execution between the two scenarios and may point to the culprit

Pat

<mikehix@gmail.com> wrote in message
news:9f76d9ee-2475-4ef5-8eda-d967562dc746@c65g2000hsa.googlegroups.com...
> I've been having some issues with IIS where it pins the processor
> until the app pool is recycled. This sequence of events from an IIS
> State log seems to be the culprit every time:
>
> Thread ID: 29
> System Thread ID: 16d4
> Kernel Time: 0:0:6.218
> User Time: 1:45:8.500
> Thread Type: ASP
>
> # ChildEBP RetAddr
> 00 0b57df30 7357c7f6 MSVBVM60!
> _COLE2TEMPLATE_vtbl::put__AUTOVERBMENUIPROP_CLIENT+0x7
> 01 0b57df98 7363bc3a MSVBVM60!VBDataObjectFiles::`vftable'+0x36
> 02 0b57e24c 735e2b6e MSVBVM60!EpiInvokeMethod+0x441
> 03 0b57e288 735e8642 MSVBVM60!FORM::LoadProp+0x1d
> 04 0b57e384 735e8226 MSVBVM60!CTLUSER::GetPropA+0x88
> 05 0b57e3c0 776b13af MSVBVM60!CTLUSER::SetPropA+0x26
> 06 0b57e4b0 776b1275 ole32!ICoCreateInstanceEx+0xcb
> 07 0b57e4d8 776b1244 ole32!CComActivator::DoCreateInstance+0x28
> 08 0b57e4fc 73653937 ole32!CoCreateInstanceEx+0x23
> 09 0b57e56c 73675e68 MSVBVM60!qsort+0xb7
> 0a 0b57e584 73675e98 MSVBVM60!Adjustor954
> 0b 0b57e5c4 73671ce7 MSVBVM60!Adjustor960
> 0c 0b57e6dc 77d06de9 MSVBVM60!lblEX_ThisVCallR8+0x4f
> 0d 0b57e6f8 73646a6f OLEAUT32!DispCallFunc+0x16a
> 0e 0b57f054 7363a0d4 MSVBVM60!VBStrToLong+0xcf
> 0f 0b57f0b0 70a146eb MSVBVM60!rtFindFirstFile+0x185
> 10 0b57f13c 70a14968 asp!CPageObject::TryInvokeMethod+0x73
> 11 0b57f188 70a01594 asp!CPageObject::InvokeMethod+0x4c
> 12 0b57f1d8 709ee237 asp!CPageComponentManager::OnStartPage+0x1a4
> 13 0b57f200 709f76ff asp!
> CPageComponentManager::AddScopedUnnamedInstantiated+0xb6
> 14 0b57f24c 709ee04c asp!CTypelibCache::CreateComponent+0x13b
> 15 0b57f28c 77d06de9 asp!CServer::CreateObject+0x66
> 16 0b57f2ac 77d06c80 OLEAUT32!DispCallFunc+0x16a
> 17 0b57f33c 709edf7d OLEAUT32!CTypeInfo2::Invoke+0x234
> 18 0b57f364 73469f71 asp!CDispatchImpl<IServer>::Invoke+0x55
> 19 0b57f3b8 73468f37 vbscript!CatchIDispatchInvoke+0x46
> 1a 0b57f3f8 73468ea6 vbscript!IDispatchInvoke2+0xaf
> 1b 0b57f434 73469000 vbscript!IDispatchInvoke+0x59
> 1c 0b57f548 73467bb6 vbscript!InvokeDispatch+0x13a
> 1d 0b57f56c 73468fbd vbscript!InvokeByName+0x42
> 1e 0b57f848 73464940 vbscript!CScriptRuntime::Run+0x2581
> 1f 0b57f940 73464cd2 vbscript!CScriptEntryPoint::Call+0x5c
> 20 0b57f998 73465522 vbscript!CSession::Execute+0xb4
> 21 0b57f9e8 7346189b vbscript!COleScript::ExecutePendingScripts+0x13e
> 22 0b57fa04 709e2f5a vbscript!COleScript::SetScriptState+0x150
> 23 0b57fa30 709e2f1a asp!CActiveScriptEngine::TryCall+0x19
> 24 0b57fa6c 709e2e50 asp!CActiveScriptEngine::Call+0x31
> 25 0b57fa88 709e2d54 asp!CallScriptFunctionOfEngine+0x5b
> 26 0b57fadc 709e2c7f asp!ExecuteRequest+0x17e
> 27 0b57fb44 709e2a4d asp!Execute+0x249
> 28 0b57fb98 709e271a asp!CHitObj::ViperAsyncCallback+0x3e8
> 29 0b57fbb4 75bd72a5 asp!CViperAsyncRequest::OnCall+0x92
> 2a 0b57fbd0 7770f0eb comsvcs!CSTAActivityWork::STAActivityWorkHelper
> +0x32
> 2b 0b57fc1c 7770fb38 ole32!EnterForCallback+0xc4
> 2c 0b57fd7c 77710042 ole32!SwitchForCallback+0x1a3
> 2d 0b57fda8 77694098 ole32!PerformCallback+0x54
> 2e 0b57fe40 777127fd ole32!CObjectContext::InternalContextCallback
> +0x159
> 2f 0b57fe60 75bd7649 ole32!CObjectContext::DoCallback+0x1c
> 30 0b57fecc 75bd79a5 comsvcs!CSTAActivityWork::DoWork+0x12d
> 31 0b57fee4 75bd833e comsvcs!CSTAThread::DoWork+0x18
>
> Does this look familiar to anyone? Thanks in advance.