Topic Last Modified: 2010-07-02

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:


Product Name


Product Version

14.0 (Exchange 2010)

Event ID


Event Source


Alert Type


Rule Path

Microsoft Exchange Server/Exchange 2010/Mailbox/System Attendant

Rule Name

One of the System Attendant's tasks is blocked.


This Error event indicates that the Microsoft® Exchange System Attendant service cannot start because one or more tasks of this service are blocked. The function name that is specified in the event description indicates the blocked task. Each blocked task will cause this event to be logged by having the function name in the event description. This event may occur for various reasons. See the "User Action" section for information about how to resolve this error.

User Action

To resolve this problem, do one or more of the following:

  • If this Error event is followed by MSExchangeSA Informational Event ID 1032 that has the same function name as specified in the event description, this indicates that a blocked task has recovered from a long delay and now operates correctly.

  • If this event occurs repeatedly without an MSExchangeSA Event ID 1032, increase the diagnostic logging level on the following counters of the MSExchangeSA performance object for additional events:

    • NSPI Proxy

    • OAL Generator

    • Proxy Generation

You can increase logging by running the following Exchange Management Shell commands:

  • Set-EventLogLevel "MSExchangeSA\NSPI Proxy" -Level High

  • Set-EventLogLevel "MSExchangeSA\OAL Generator" -Level High

  • Set-EventLogLevel "MSExchangeSA\Proxy Generation" -Level High

For detailed information about how to increase logging, see Manage Diagnostic Logging Levels.

  • Review other related Error events and Warning events that are logged in the Application log. These related events may help you find the root cause of this error.

  • Try to restart Microsoft Exchange System Attendant service from the Services panel.

Important After you finish troubleshooting this problem, return logging to the default level by running the following commands:

  • Set-EventLogLevel "MSExchangeSA\NSPI Proxy" -Level Lowest

  • Set-EventLogLevel "MSExchangeSA\OAL Generator" -Level Lowest

  • Set-EventLogLevel "MSExchangeSA\Proxy Generation" -Level Lowest

For More Information

If you are not already doing so, consider running the Exchange tools 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, improve mail flow, and better manage disaster recovery scenarios. 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.