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 |
8010 |
Event Source |
MSExchangeTransport |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport |
Rule Name |
A message was rejected by the remote server. This message will be deferred and retried because it was marked for retry if rejected. |
Explanation
This Error event indicates that at least one journal message could not be delivered to a journal report mailbox.
When a journal message is rejected for any reason, the transport process intercepts the non-delivery report (NDR) process and tries to transfer the message again in retry mode. Journal messages do not cause an NDR to be sent.
Note If you do not resolve this error, it is very possible that messages will build in the queues. Eventually the server may stop processing e-mail.
User Action
To resolve this error, determine the reason that a journal message is rejected. Then correct the issue. Follow these steps:
- Run the Exchange Management Shell Get-Message
cmdlet with the IncludeRecipientInfo parameter. The cmdlet
should return the error message that explains why the message was
rejected.
- Fix the issue based on the information in the error specified
in the Exchange Management Shell. After you fix the issue,
message delivery should continue.
For more information, see Get-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.