Hi

Posted a message yesterday about a server running ASP that after a
while running fine, suddenly the inetinfo process consumes 100% cpu.
The application that is running on the IIS server is a "standard" ASP
application that uses self-made VB COM dll's. I have analyzed the dump
file created by iisstate, and by running windbg with the correct
symbols loaded this is one of the threads that consumes almost all the
cpu time:

OLE32!CoSetErrorInfo+0x52 (FPO: [Non-Fpo])
OLEAUT32!SetErrorInfo+0x25 (FPO: [2,0,2])
WARNING: Stack unwind information not available. Following frames may
be wrong.
msado15!DllRegisterServer+0x2652
msado15!DllCanUnloadNow+0x14da7
msado15!DllCanUnloadNow+0x22dec
ISKunde!KUNDEdb::RemoveParameterItems+0x105
[C:\D-disk\API\Common\DBClasses2\ISKunde\Source\KUNDEdb.cls @ 870]
ISKunde!KUNDEdb::bFetch+0xec
[C:\D-disk\API\Common\DBClasses2\ISKunde\Source\KUNDEdb.cls @ 309]
ISKunde!KUNDE::bExist+0x8f
[C:\D-disk\API\Common\DBClasses2\ISKunde\Source\KUNDE.cls @ 750]
ISCust2!clsCustomer::bExist+0x26f
[C:\D-disk\API\ISCust2\Source\clsCustomer.cls @ 3014]
OLEAUT32!DispCallFunc+0x15d
MSVBVM60!EpiInvokeMethod+0x1e1
MSVBVM60!BASIC_CLASS_Invoke+0x52
vbscript!DllRegisterServer+0x4b76
vbscript!DllGetClassObject+0xba01
vbscript!DllGetClassObject+0x8aa1
vbscript!DllGetClassObject+0x8a4b
vbscript+0x4f79
vbscript!DllGetClassObject+0x866e
vbscript+0x4412
vbscript+0x5824
vbscript+0x4412
vbscript+0x480d
vbscript!DllCanUnloadNow+0x76ef
vbscript!DllGetClassObject+0x202d
ASP!CActiveScriptEngine::TryCall+0x15 (FPO: [Non-Fpo])
ASP!CActiveScriptEngine::Call+0x4d (FPO: [Non-Fpo])
ASP!CallScriptFunctionOfEngine+0x48 (FPO: [Non-Fpo])
ASP!ExecuteRequest+0x19e (FPO: [Non-Fpo])
ASP!Execute+0x17e (FPO: [Non-Fpo])
ASP!CHitObj::ViperAsyncCallback+0x452 (FPO: [Non-Fpo])
ASP!CViperAsyncRequest::OnCall+0x3f (FPO: [Non-Fpo])
comsvcs!STAActivityWorkHelper+0xa (FPO: [1,0,0])
OLE32!EnterForCallback+0x6a (FPO: [Non-Fpo])
OLE32!SwitchForCallback+0x12f (FPO: [Non-Fpo])
OLE32!PerformCallback+0x50 (FPO: [Non-Fpo])
OLE32!CObjectContext::InternalContextCallback+0x10d (FPO: [Non-Fpo])
OLE32!CObjectContext::DoCallback+0x1a (FPO: [Non-Fpo])
comsvcs!STAActivityWork::DoWork+0x75 (FPO: [0,4,2])
comsvcs!STAThread::STAThreadWorker+0x423 (FPO: [Uses EBP] [1,31,4])
KERNEL32!BaseThreadStart+0x52 (FPO: [Non-Fpo])

The dll's ISKunde and ISCust2 are the "home-made" VB COM dll's. I'm not
an expert in understanding these call stacks, and I hope someone can
point out the exact reason for the high CPU usage. By the way, this web
application runs on about 30 other production servers, and I haven't
experienced this problem on some of the other servers.

Hope someone can give me a clue about this.

Re: W2K/IIS5, high CPU utilization by Pat

Pat
Tue Dec 13 11:16:27 CST 2005

Posted a response on another thread. Most likely problem is MDAC which
should be updated.

Pat

"Eivind" <eivind.eriksen@gmail.com> wrote in message
news:1134489974.494147.40480@f14g2000cwb.googlegroups.com...
> Hi
>
> Posted a message yesterday about a server running ASP that after a
> while running fine, suddenly the inetinfo process consumes 100% cpu.
> The application that is running on the IIS server is a "standard" ASP
> application that uses self-made VB COM dll's. I have analyzed the dump
> file created by iisstate, and by running windbg with the correct
> symbols loaded this is one of the threads that consumes almost all the
> cpu time:
>
> OLE32!CoSetErrorInfo+0x52 (FPO: [Non-Fpo])
> OLEAUT32!SetErrorInfo+0x25 (FPO: [2,0,2])
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> msado15!DllRegisterServer+0x2652
> msado15!DllCanUnloadNow+0x14da7
> msado15!DllCanUnloadNow+0x22dec
> ISKunde!KUNDEdb::RemoveParameterItems+0x105
> [C:\D-disk\API\Common\DBClasses2\ISKunde\Source\KUNDEdb.cls @ 870]
> ISKunde!KUNDEdb::bFetch+0xec
> [C:\D-disk\API\Common\DBClasses2\ISKunde\Source\KUNDEdb.cls @ 309]
> ISKunde!KUNDE::bExist+0x8f
> [C:\D-disk\API\Common\DBClasses2\ISKunde\Source\KUNDE.cls @ 750]
> ISCust2!clsCustomer::bExist+0x26f
> [C:\D-disk\API\ISCust2\Source\clsCustomer.cls @ 3014]
> OLEAUT32!DispCallFunc+0x15d
> MSVBVM60!EpiInvokeMethod+0x1e1
> MSVBVM60!BASIC_CLASS_Invoke+0x52
> vbscript!DllRegisterServer+0x4b76
> vbscript!DllGetClassObject+0xba01
> vbscript!DllGetClassObject+0x8aa1
> vbscript!DllGetClassObject+0x8a4b
> vbscript+0x4f79
> vbscript!DllGetClassObject+0x866e
> vbscript+0x4412
> vbscript+0x5824
> vbscript+0x4412
> vbscript+0x480d
> vbscript!DllCanUnloadNow+0x76ef
> vbscript!DllGetClassObject+0x202d
> ASP!CActiveScriptEngine::TryCall+0x15 (FPO: [Non-Fpo])
> ASP!CActiveScriptEngine::Call+0x4d (FPO: [Non-Fpo])
> ASP!CallScriptFunctionOfEngine+0x48 (FPO: [Non-Fpo])
> ASP!ExecuteRequest+0x19e (FPO: [Non-Fpo])
> ASP!Execute+0x17e (FPO: [Non-Fpo])
> ASP!CHitObj::ViperAsyncCallback+0x452 (FPO: [Non-Fpo])
> ASP!CViperAsyncRequest::OnCall+0x3f (FPO: [Non-Fpo])
> comsvcs!STAActivityWorkHelper+0xa (FPO: [1,0,0])
> OLE32!EnterForCallback+0x6a (FPO: [Non-Fpo])
> OLE32!SwitchForCallback+0x12f (FPO: [Non-Fpo])
> OLE32!PerformCallback+0x50 (FPO: [Non-Fpo])
> OLE32!CObjectContext::InternalContextCallback+0x10d (FPO: [Non-Fpo])
> OLE32!CObjectContext::DoCallback+0x1a (FPO: [Non-Fpo])
> comsvcs!STAActivityWork::DoWork+0x75 (FPO: [0,4,2])
> comsvcs!STAThread::STAThreadWorker+0x423 (FPO: [Uses EBP] [1,31,4])
> KERNEL32!BaseThreadStart+0x52 (FPO: [Non-Fpo])
>
> The dll's ISKunde and ISCust2 are the "home-made" VB COM dll's. I'm not
> an expert in understanding these call stacks, and I hope someone can
> point out the exact reason for the high CPU usage. By the way, this web
> application runs on about 30 other production servers, and I haven't
> experienced this problem on some of the other servers.
>
> Hope someone can give me a clue about this.
>