A corrupted page link is detected in a B-Tree and may be caused by hardware failure or antivirus software
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-09-09
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
447 |
Event Source |
ESE |
Category |
KHI |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Extensible Storage Engine |
Rule Name |
A corrupted page link was detected in a B-Tree. This may be caused by a hardware failure or antivirus software. |
Explanation
This Error event indicates that a corrupted page link was detected in a B-Tree. Available space in the Exchange store database is in the form of a list of pages that can be used to store new data. The available space is called a space tree. The space tree is held as a binary tree that is searched whenever a block of new data must be added to the database.
During an online defragmentation, a problem was discovered in this tree.
This event is often caused by a hardware failure or by an antivirus software scan of the database file directory.
User Action
To resolve this problem, do one or more of the following:
Restore the database from a backup. A bad page link error indicates logical corruption at the ESE level in the database. Therefore, it is not safe to continue using the database. The database restore must be performed by using a backup that was taken before this error occurred.
If you do not have a backup that was made before the error occurred, try to repair the database. For example, run the isinteg –fix command to perform a hard repair. Then, use one of the following cmdlets, depending on the version of Microsoft Exchange Server 2010 that is running on the computer:
In Exchange 2010 RTM, use the Export-Mailbox cmdlet or the Move Request cmdlet set.
In Exchange Server 2010 SP1, use the Mailbox Repair Request cmdlet set or the Move Request cmdlet set. For more information, see Recipient Cmdlets.
Make sure that you have configured your antivirus software correctly. For more information, see Managing Anti-Spam and Antivirus Features.
For More Information
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.