Topic Last Modified: 2010-09-15

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

MSExchange Store Driver

Alert Type


Rule Path

Microsoft Exchange Server/Exchange 2010/Hub Transport/Store Driver

Rule Name

The Exchange transport Store Driver component encountered a poison message during message submission. The submission will be cancelled.


This Operations Manager alert indicates that the store driver encountered a poison message.

  • If event 1009 is logged, the store driver component encountered a poison message when it tried to submit a message item. The operation to submit the outbound message that is specified in the event description will be aborted.

  • If event 1011 is logged, the store driver encountered poison message when it tried to deliver a message item.

The store driver is a software component of the Hub Transport Server that delivers inbound messages to Microsoft Exchange stores, the databases that contain public folder stores and mailbox stores. The store driver also retrieves messages from a user's outbox, and submits them for delivery.

User Action

To resolve this alert, follow one or more of these steps:

  • If event 1009 is logged, use the Get-Queue cmdlet to determine whether there are any messages in the poison message queue. The poison message queue is a persistent queue that isolates messages that are detected as potentially fatal to a computer that is running Exchange. This queue is typically empty. If no such messages exist in the poison message queue, the queue does not appear in the queue viewing interfaces. For more information about the Get-Queue cmdlet, see Get-Queue.

    If there is a message in the poison message queue, we recommend that you contact Microsoft Product Support Services to report the potentially harmful message that Exchange detected. For more information about how to contact support, visit the Microsoft Help and Support Web site.

    Note   Do not delete the poison message from the poison message queue. Microsoft Product Support Services may have to examine the message.

  • If event 1011 is logged, use the Exchange message tracking feature to try to determine the root cause of this warning. For example, search the message tracking log files for messages delivered to the mailbox specified in the event description. For information about tracking messages, see Configure Message Tracking.

    In addition, poison messages can be resubmitted or exported. For more information about how to troubleshoot messages, see Managing Transport Queues.

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.