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

This article was previously published under Q305370
This article has been archived. It is offered "as is" and will no longer be updated.
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+0x8068e5d39c 612555d5 0c8ea880 68e5d594 1292a340 EXCDO!HrSyncCdoOlFBCOnCreateSingle+0x48668e5d3c8 61254791 68e5d6b0 00000000 00000000 EXCDO!HrSyncCdoOlFBC+0xad68e5d420 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+0x2668e5d490 61270624 00000000 68e5d6b0 00000000 EXCDO!CExpStatus__HrSaveSingle+0xee 230a91e0 00470ac0 23555498 236cd184 236cd018 EXCDO!HrSavingAppt+0x5b2 230a92bc 00650072 00610077 006c006c 0031002d store!EcSortAttachlist+0x11e					
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.
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 hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this fix should have the following file attributes or later:

Component: CDO

File nameVersion

NOTE: Due to file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Article ID: 305370 - Last Review: 10/24/2013 07:18:02 - Revision: 1.6

Microsoft Exchange 2000 Server Standard Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbbug kbexchange2000presp2fix kbfix kbqfe KB305370
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)