Poison Queue Length - sustained for 5 minutes - Yellow(>1) - Edge Transport.
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-08-02
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager includes a performance data collection engine that is used to query performance counter objects on computers running Exchange 2010. For this Operations Manager rule, data is collected by using the performance counter specified in the Details table.
To review the value of the performance counter that generated this alert, in Operations Manager, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Object Name |
MSExchangeTransport Queues |
Counter Name |
Poison Queue Length |
Instance Name |
_Total |
Sample Interval |
60 |
Server Role |
Ex14. Edge Transport |
Warning Threshold |
1 |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Edge Transport/Transport Queues |
Rule Name |
Poison Queue Length - sustained for 5 minutes - Yellow(>1) - Edge Transport. |
Explanation
The Poison Queue Length performance counter measures the number of messages currently in the poison queue. Messages in the poison message queue are in a permanently suspended state.
This alert indicates that the Poison Queue Length has been greater than 1 for five minutes.
The poison message queue contains messages that are determined to be potentially harmful to the Microsoft Exchange Server 2010 server after a server failure. The messages may be genuinely harmful in their content and format. They may also be the results of a poorly written agent that has caused the Exchange server to fail when it processed the supposedly bad messages.
Messages remain in the poison message queue until they are manually resumed or removed by an administrator. The messages in the poison message queue are never automatically resumed or expired.
User Action
To resolve this alert, resubmit or remove the messages from the poison message queue. You can resubmit the messages that are in the poison message queue by using Exchange Queue Viewer or by running the Resume-Message cmdlet. You can remove messages from the poison message queue by using Queue Viewer or by running the Remove-Message cmdlet.
Note You cannot resubmit messages in the poison queue using the Retry-Queue cmdlet with the Resubmit parameter.
For detailed steps about resubmitting messages in the poison queue, see the "Resubmit messages located in the poison message queue" section in Resubmit Messages in Queues.
For detailed steps about removing messages from the poison queue, see Remove Messages from Queues.
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.