MSExchangePowerShellLiveIDAppPool has exceeded its committed memory limit. See event ID 701 in the application event log for more information
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-09-27
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 |
701 |
Event Source |
WSRM |
Category |
KHI |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Remote PowerShell |
Rule Name |
MSExchangePowerShellLiveIDAppPool has exceeded its committed memory limit. See event ID 701 in the application event log for more information. |
Explanation
This Warning event indicates that MSExchangePowerShellLiveIDAppPool is using more memory than the committed memory limit for the process.
In Microsoft Exchange Server 2010, all PowerShell cmdlet calls are executed remotely in either MSExchangePowerShellAppPool or in MSExchangePowerShellLiveIDAppPool in IIS. These calls are executed by a Windows process (w3wp.exe). This occurs regardless of whether the PowerShell.exe process runs locally or remotely. The Windows System Resource Manager service maintains the committed memory limit. The service monitors the committed memory usage of matched processes. The service also enforces the user-defined action whenever the committed memory usage of the process exceeds its limit.
Event 701 indicates that the online defragmentation feature has finished a full defragmentation. In Exchange 2010, the architecture for online defragmentation was moved out of the Mailbox database maintenance process and now runs in the background 24 hours a day, seven days a week.
You don't have to configure any settings for this feature. Exchange monitors the database as it uses it, and small changes are made over time to keep the database defragmented for space and contiguity. If the database analyzes a range of pages and finds that they are not as sequential as they should be, it starts an async thread to defragment that section of the B-tree or table. Online defragmentation is also throttled so that it does not adversely affect client performance.
User Action
No user action is required.
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.