XADM: Store May Crash When User Accepts Meeting Request in Outlook Web Access (305370)


The information in this article applies to:

  • Microsoft Exchange 2000 Server
This article was previously published under Q305370

SYMPTOMS

When a user accepts a meeting request in Outlook Web Access (OWA), the store may stop responding (crash) with the following call stack: 

ChildEBP RetAddr Args to Child 
68e5d340 61246991 0d0c2798 00005dd2 68e5d594 EXCHMEM!ExchMHeapFree+0x80
68e5d39c 612555d5 0c8ea880 68e5d594 1292a340 EXCDO!HrSyncCdoOlFBCOnCreateSingle+0x486
68e5d3c8 61254791 68e5d6b0 00000000 00000000 EXCDO!HrSyncCdoOlFBC+0xad
68e5d420 61254ae3 0000ffff 00000000 68e5d594 EXCDO!CExpStatus__HrFBPublish+0x2e7 
68e5d448 61254912 00000001 00000000 1fffffff EXCDO!CExpStatus___HrUpdateFB+0x4b2 
68e5d46c 6123a168 00000001 00000000 00000001 EXCDO!CExpStatus__HrUpdateFB+0x26
68e5d490 61270624 00000000 68e5d6b0 00000000 EXCDO!CExpStatus__HrSaveSingle+0xee 
230a91e0 00470ac0 23555498 236cd184 236cd018 EXCDO!HrSavingAppt+0x5b2 
230a92bc 00650072 00610077 006c006c 0031002d store!EcSortAttachlist+0x11e

CAUSE

The problem is that Exchange 2000 allocates a buffer for the new Microsoft Outlook cache based on the header size, but later when saving the appointment, Exchange 2000 copies the amount of data based on the SPropValue size. The problem comes in when the header size is smaller than the SPropValue size. When this condition occurs, Exchange 2000 copies more data to the target memory location than was allocated, which overruns the buffer.

RESOLUTION

To resolve this issue, before Exchange 2000 copies to the target memory location, it compares the header value with the SPropValue size. If they are different, Exchange 2000 regenerates the cache and synchronizes the values.

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Component: CDO

File nameVersion
Store.exe6.0.4720.43
Jcb.dll6.0.4720.43
Exoledb.dll6.0.4720.43
Excdo.dll6.0.4720.43
Mdbsz.dll6.0.4720.43

NOTE: Due to file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbbug kbExchange2000preSP2fix kbfix kbQFE KB305370
©2004 Microsoft Corporation. All rights reserved.