Microsoft KB Archive/884547

= The Microsoft Exchange Information Store service quits after a version conflict is detected in a public folder post in Exchange Server 2003 =

Article ID: 884547

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition

-





SYMPTOMS
On your Microsoft Exchange Server 2003 computer, the Microsoft Exchange Information Store service may quit unexpectedly. You may experience this problem soon after a version conflict is detected in a public folder post.



CAUSE
This problem occurs because of heap corruption in Exchange. This problem may occur if the following conditions are true:
 * The Exchange diagnostics logging level is set to 5 on the MSExchangeIS\Public Folders\Replication Conflicts object.
 * Exchange detects a version conflict in a public folder post. However, only one change number is associated with this version conflict.

This problem occurs in the Exchange event logging code. In this scenario, the event logging code incorrectly expects two change numbers to be involved in every version conflict. If only one change number is involved in a version conflict, the heap becomes corrupted. Soon after the heap becomes corrupted, the Microsoft Exchange Information Store service may quit.

Typically, a version conflict does involve two change numbers. Each of these two change numbers corresponds to an uncommitted change to the information store. However, in the following sample scenario, only one change number is involved in a version conflict:
 * 1) Two Microsoft Outlook users modify the same message. However, one Outlook user modifies this message while the user is connected to the Exchange computer. The second Outlook user modifies this message while the user is not connected to the Exchange computer.
 * 2) The offline Outlook user synchronizes Outlook with the Exchange computer.

In this scenario, the online Outlook user's change to the message is committed to the information store. Therefore, there is no change number for the version conflict for this message. The second Outlook user's change is not committed to the information store until that second user synchronizes Outlook with Exchange. Therefore, there is only one change number that is involved in the version conflict for this message.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.

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

http://support.microsoft.com/contactus/?ws=support

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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
No prerequisites are required to install this hotfix.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version            Size    File name 28-Oct-2004 22:34  6.5.7232.46     2,528,504  Exchange2003-kb884547-x86-enu.exe



WORKAROUND
To work around this problem, decrease the Exchange diagnostics logging level to 4 or less.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

817903 New naming schema for Exchange Server software update packages

Additional query words: XADM crash CN

Keywords: kbqfe kbhotfixserver kbfix kbbug KB884547

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.