You are currently offline, waiting for your internet to reconnect

XADM: Online Defragmentation Loops Continuously When the Database Is Corrupted

This article was previously published under Q292305
This article has been archived. It is offered "as is" and will no longer be updated.
An incorrect page link in the Extensible Storage Engine (ESE) database may cause online defragmentation to loop continuously.
This problem can occur if the latching logic for merges processes an incorrect page link as a transient error (errBTMergeNotSynchronous). An incorrect page link is caused by a split or merge operation on an adjacent page.
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.For additional information about how to download the fix for this problem, click the article number below to view the article in the Microsoft Knowledge Base:
291222 XGEN: Rollup of Selected Exchange 2000 Server Post-Release Fixes
The English version of this fix should have the following file attributes or later:

Component: ESE

File nameVersion

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
After you apply this fix, the split or merge logic in the ESE searches for incorrect page links in any of the pages that are involved in the split or merge operation; if the ESE finds an incorrect page link, the ESE errors out instead of looping continuously.

Article ID: 292305 - Last Review: 10/23/2013 17:11:05 - Revision: 1.6

Microsoft Exchange 2000 Server Standard Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbbug kbexchange2000presp2fix kbfix kbqfe KB292305