Topic Last Modified: 2010-02-18
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 |
9201 |
|
Event Source |
MSExchangeTransport |
|
Alert Type |
Error |
|
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport |
|
Rule Name |
The OnSubmittedMessage agent did not handle a catchable exception. |
Explanation
This Error event indicates that the transport agent specified in the event description threw an unhandled exception when it tried to process a message. The first time that a message triggers this exception, the Microsoft Exchange Transport service will crash. If the message is processed again and causes the same unhandled exception, the message is moved to 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 Microsoft Exchange Server 2010. 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.
User Action
To resolve this error, follow these steps:
- Review the event description to identify the transport agent
that triggered the unhandled exception.
- If the transport agent is written by Microsoft, contact
Microsoft Product Support Services. For more information about how
to contact support, visit the Microsoft Help and Support Web site.
- If the transport agent is not written by Microsoft, contact the
software vendor who provided the transport agent.
- If the message was transferred to the poison message queue, we
recommend that you contact Microsoft Product Support 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.
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.