MSExchangeTransport 9213

 

This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.

Details

Product Name

Exchange

Product Version

14.0

Event ID

9213

Event Source

MSExchangeTransport

Category

Categorizer

Symbolic Name

RetryCategorizationIfFailed

Message Text

A non-expirable message with the Internal Message ID %1 could not be categorized. This message may be a journal report or other system message. The message will remain in the queue until administrative action is taken to resolve the error. Other messages may also have encountered this error. To further diagnose the error, use the Queue Viewer or the Exchange Mail Flow Troubleshooter.

Explanation

This Warning event indicates that a journal report that was sent to a journaling mailbox has been rejected. The journal report has been resubmitted to the Submission queue for categorization. This Warning event may be generated when an error is encountered with the recipient configuration of the journaling mailbox. After the problem with the recipient configuration of the journaling mailbox is corrected, Microsoft Exchange Server 2010 will automatically deliver the journal reports to the journaling mailbox.

The following conditions may cause the journaling mailbox to become unavailable:

  • The journaling mailbox no longer exists.

  • The Hub Transport server is unable to access Active Directory.

  • The recipient object of the journaling mailbox in Active Directory is invalid.

  • The primary Simple Mail Transfer Protocol (SMTP) address of the specified recipient is invalid.

  • The SMTP address that is configured on the specified recipient is not unique.

  • Other recipient resolution, routing, or content conversion errors have occurred.

User Action

To resolve this warning, do the following:

  1. Determine why the journaling mailbox is unavailable. You may be able to retrieve information about why the journal reports were rejected by running the following Exchange Management Shell command on the Hub Transport server that attempted delivery of the journal report:

    Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*<journaling mailbox SMTP address>*" } | Format-List

    This command retrieves all the messages that are currently waiting to be delivered to the journaling mailbox that you specify. For example, if the SMTP address of the journaling mailbox is journaling@contoso.com, you would use the following command:

    Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*journaling@contoso.com*" } | Format-List

    The LastError property of each message that is returned contains the reason the message was rejected. This information will help you determine why the journaling mailbox is unavailable.

  2. Use the following corrective actions to resolve the most common issues that cause this warning. Perform the action that reflects the cause of the failed delivery:

    • Verify the recipient configuration information is correct. If the recipient's SMTP address was entered incorrectly, correct the SMTP address in the journal rule. Then, create a temporary mailbox with the previously entered incorrect SMTP address. This mailbox will accept the journal reports that are sent to the incorrect SMTP address. You can then forward these journal reports to the correct journaling mailbox, and you can delete the temporary mailbox.

    • Verify that no duplicate SMTP addresses are configured on recipients in your organization

    • Verify that there are no invalid characters in the SMTP address of the configured recipient.

    • Run the Dcdiag command-line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Microsoft Windows Server Library.

  3. If you need to, check for additional configuration errors. For help determining what might be configured incorrectly, run the Best Practices Analyzer located in the Toolbox in the Exchange Management Console.

You can also use an alternate journaling mailbox to help manage journal reports that have been rejected. Only journal reports that are submitted categorization for delivery to an unavailable journaling mailbox after an alternate journaling mailbox is configured will be redirected to the alternate journaling mailbox. Journal reports that have already failed categorization when an alternate journaling mailbox is enabled are not redirected.

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.