CPU resources are used up when you use the Set-MailboxMessageConfiguration cmdlet in an Exchange Server 2010 environment

Article ID: 2657103 - View products that this article applies to.
Expand all | Collapse all


When you change Microsoft Outlook Web Access options by using the Set-MailboxMessageConfiguration cmdlet in a Microsoft Exchange Server 2010 environment, CPU resources are used up on a mailbox server that is running Exchange Server 2010. When this occurs, many of the following events are logged on the Exchange Server 2010 Client Access server:
Log Name: MSExchange Management
Source: MSExchange CmdletLogs
Date: Date
Event ID: 6
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Cmdlet failed. Cmdlet Set-MailboxMessageConfiguration, parameters {parameters}.


This issue occurs because an infinite loop occurs when the Set-MailboxMessageConfiguration cmdlet is executed. This behavior causes the server that is running Exchange Server 2010 and has the Client Access server role installed to continuously retry writing a configuration file to the mailbox.


To resolve this issue, install the following update rollup:
2661854 Description of Update Rollup 2 for Exchange Server 2010 Service Pack 2


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


For more information about the Set-MailboxMessageConfiguration cmdlet, visit the following Microsoft website:
General information about the Set-MailboxMessageConfiguration cmdlet


Article ID: 2657103 - Last Review: April 16, 2012 - Revision: 1.0
  • Microsoft Exchange Server 2010 Service Pack 2, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
kbqfe kbfix kbsurveynew kbexpertiseinter KB2657103

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com