Just so people have the solution on hand, install a patch from
Microsoft on this particular DLL. Turns out once our organization
started using Outlook 2003, an additional property was added to the
"Inbox" folder on the Exchange Server. This additional property was
not expected by the CDO.dll causing it to hang up. The following link
describes this problem and the download for the solution. Good luck
to all. (KB818709)
<a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=kb;en-us;818709" target="_blank">http://support.microsoft.com/default.aspx?scid=kb;en-us;818709</a>
"Pat [MSFT]" <patfilot.RemoveThis@online.microsoft.com> wrote in message news:<OgKTvfldEHA.3420.RemoveThis@TK2MSFTNGP12.phx.gbl>...
> Yep. You picked the right thread. Bug in CDO.dll. You will need to
> contact support to get the fix.
>
> Pat
>
> "Sean" <aether8203.RemoveThis@yahoo.com> wrote in message
> news:9f0ea455.0407300830.2803c525@posting.google.com...
> > Platform: Outlook Web Access (service pack 4 from Exch 5.5 SP4) on
> > Windows 2000 Adv Server & IIS 5.0 with all Service Packs and Patches.
> >
> > Problem: Occasionally hit 100% CPU hang.
> >
> > Action: Used iisstate against the inetinfo.exe PID. Instead of
> > reporting all 63 Threads here, I found the "one" that was locked up
> > for over 2 hours. I included a few threads after it as well.
> >
> > ======= BEGIN EXCERPT FROM LOG ========
> >
> > Thread ID: 50
> > System Thread ID: 788
> > Kernel Time: 0:0:2.468
> > User Time: 2:44:53.406
> > *** ERROR: Symbol file could not be found. Defaulted to export
> > symbols for -
> > Thread Type: ASP
> > Executing Page: Unable to locate ASP page
> >
> > # ChildEBP RetAddr
> > 00 0364f0e4 6f06c9fb cdo!CDispatchObj::M_InvalidateObj1+0xb
> > 01 0364f0ec 6f06c969 cdo!CDispatchObj::M_InvalidateChildren1+0x1b
> > 02 0364f0f8 6f08663c cdo!CDispatchObj::M_InvalidateChildren+0x29
> > 03 0364f130 6f083726 cdo!CSession::M_ScLogoff+0x11c
> > 04 0364f134 6f06cd80 cdo!CSession::V_HrInvoke+0xf6
> > 05 0364f144 03264279 cdo!CDispatchObj::Invoke+0xa0
> > WARNING: Stack unwind information not available. Following frames may
> > be wrong.
> > 06 0364f1c0 0326866f vbscript!DllCanUnloadNow+0x8e24
> > 07 00000000 00000000 vbscript!DllCanUnloadNow+0xd21a
> >
> >
> >
> > Thread ID: 51
> > System Thread ID: 770
> > Kernel Time: 0:0:0.0
> > User Time: 0:0:0.0
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 036aff9c 77f842c4 ntdll!NtDelayExecution+0xb
> > 01 036affb4 7c57438b ntdll!RtlpTimerThread+0x42
> > 02 036affec 00000000 KERNEL32!BaseThreadStart+0x52
> >
> >
> >
> >
> > Thread ID: 52
> > System Thread ID: 764
> > Kernel Time: 0:0:0.0
> > User Time: 0:0:0.0
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 03a5ff20 77f838a5 ntdll!ZwRemoveIoCompletion+0xb
> > 01 03a5ffb4 7c57438b ntdll!RtlpWorkerThread+0x6b
> > 02 03a5ffec 00000000 KERNEL32!BaseThreadStart+0x52<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: IISState Log: 100% CPU on OWA 
FAQ
Search
Profile
Private Messages
Log in
