Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Mailboxes are quarantined after you install the Exchange Server 2010 SP2 version of the Exchange Server 2010 Management Pack


View products that this article applies to.

Symptoms

Assume that you have a Microsoft Exchange Server 2010 Service Pack 2 (SP2) organization that is monitored by a System Center Operations Manager (SCOM) server. You install the Exchange Server 2010 SP2 version of the Exchange Server 2010 Management Pack on the SCOM server. In this situation, many mailboxes in a single mailbox database are quarantined. Additionally, the following event is logged in the Application log on the Mailbox server:
 

↑ Back to the top


Cause

This issue occurs because the SCOM server uses the Troubleshoot-DatabaseSpace.ps1 script to monitor log generation. The mailboxes are quarantined because the script is executed when there is less than 25 percent of free disk space. Additionally, the mailboxes are quarantined when the JET Log Bytes Generated/hour performance counter indicates that the log generation consumes the remaining free disk space within 12 hours.

Note The default settings that are used in the Troubleshoot-DatabaseSpace.ps1 script are defined in the StoreTSConstants.ps1 script that is located in the following path:
Drive:\Program Files\Microsoft\Exchange Server\V14\Scripts\StoreTSConstants.ps1

↑ Back to the top


Resolution

To resolve this issue, install Exchange Server 2010 Service Pack 3 (SP3) on the Exchange Server 2010 servers. For more information about Exchange Server 2010 SP3, click the following article number to view the article in the Microsoft Knowledge Base:
2808208 Description of Exchange Server 2010 Service Pack 3

↑ Back to the top


Workaround

To work around this issue, use one of the following methods.

Method 1

Create an SCOM override to disable the database space troubleshooter that checks for free disk space. To do this, refer to the Workaround section in the following Microsoft website:

Method 2

Make one of the following changes in the StoreTSConstants.ps1 script:
  • Set the PercentEdbFreeSpaceDefaultThreshold value to 16. This enables the database space troubleshooter to retrieve the quarantine action when there is less than 20 percent of free disk space on the database or log volume. The value is as follows:
    # The percentage of disk space for the EDB file at which we should start quarantining users. 
    $PercentEdbFreeSpaceDefaultThreshold = 16
    Note The PercentEdbFreeSpaceDefaultThreshold value can be greater than or equal to the PercentEdbFreeSpaceAlertThreshold value that is specified in the StoreTSConstants.ps1 script as follows:
    # The percentage of disk space for the EDB file at which we are at alert levels.
    $PercentEdbFreeSpaceAlertThreshold = 16
  • Set the HourDefaultThreshold value to 1 so that the database space troubleshooter will retrieve the quarantine action. The quarantine action is retrieved when the JET Log Bytes Generated/hour performance counter indicates that the log generation consumes the remaining free disk space of the log or database volume within one hour. The value is as follows:
    #The number of hours we can wait before running out of space. 
    $HourDefaultThreshold = 1

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about the Troubleshoot-DatabaseSpace.ps1 script, go to the following Microsoft website:For more information about the Exchange Server 2010 Management Pack, go to the following Microsoft website:

↑ Back to the top


Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2729444
Revision : 1
Created on : 1/7/2017
Published on : 2/12/2013
Exists online : False
Views : 333