Delivery Failure Routing 5.4.4 happened over last 5 minutes - Yellow(>5).

Details

Explanation

This event indicates that the Microsoft Exchange Server 2010 transport component experienced a routing failure during its attempt to deliver e-mail messages. Delivery status codes that begin with "5" indicate a permanent failure. In this scenario, Exchange cannot deliver the message. Status code 5.4.4 represents the following error message:

This alert may be triggered when the Exchange transport component cannot locate the next hop route to the message destination. This problem may occur when one of the following conditions is true:

• The recipient's e-mail address specifies an invalid domain.

• No connector is available to route the message to the appropriate routing group.

• Network problems are preventing delivery to the destination domain.

For more information, see Understanding Transport Pipeline.

User Action

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

• Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

• Review Operations Manager for detailed information about the cause of this problem. For more information, see the "Introduction" section in this article.

• Examine the recipient's e-mail address. Verify that the address lists a valid domain.

• You may have to increase diagnostics logging to log the component startup sequence during the startup process of the Microsoft Exchange Transport service. To increase diagnostics logging for the Transport component, follow these steps:

  1. Start Registry Editor, and then locate the following registry subkey:

     HKEY_LOCAL_MACHINE\SYSTEM\Current Control set\Services\MSExchangeTransport\diagnostics

  2. Set the following REG_DWORD values to 7:

  • Smtpreceive

  • Smtpsend

  • DSN

  • Components

  • Remote Delivery

  • Categorizer

• Use the Exchange Mail Flow Troubleshooter in the Exchange Troubleshooting Assistant to examine the message tracking log FAIL events that have a status of 5.4.4. To do this, click Users are receiving unexpected non-delivery reports when sending messages in the troubleshooter. For more information, see the Exchange Server Team blog article, Mail Flow Troubleshooter in Exchange Troubleshooting Assistant (ExTRA).
  The content of each blog and its URL are subject to change without notice. The content within each blog is provided "AS IS" with no warranties, and confers no rights. Use of included script samples or code is subject to the terms specified in the Microsoft Terms of Use.

• Resolve your issue by using self-support options, assisted support options, and other resources. You can access these resources from the Exchange Server Solutions Center. From this page, click Self-Support Options in the navigation pane to use self-help options. Self-help options include searching the Microsoft Knowledge Base, posting a question at the Exchange Server forums, and other methods. Alternatively, in the navigation pane, you can click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Product Support Services, be sure to review your organization's guidelines first.

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.