MSExchangeTransport 9217

  • Article

 

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

9217

Event Source

MSExchangeTransport

Category

Categorizer

Symbolic Name

AmbiguousRecipient

Message Text

More than one Active Directory object is configured with the recipient address %1. Messages to this recipient will be deferred until the configuration is corrected in Active Directory.

Explanation

This event indicates that the Microsoft Exchange Server 2010 Categorizer component cannot verify a message recipient. Therefore, the message cannot be categorized for delivery to an Exchange mailbox.

To perform message categorization, the Hub Transport server contacts the Active Directory directory service. The Message Categorizer component retrieves recipient mailbox information, determines whether any message restrictions exist for each recipient, and expands distribution groups. Additionally, the Hub Transport server determines routing information for the submitted message.

In Exchange 2010, the Message Categorizer has the following message processing stages:

SMTP event Categorizer action Description

OnSubmittedMessage

  

This event is triggered when a message is submitted to the Submission queue on the receiving SMTP host. All messages trigger this event whether they arrive by SMTP submission, MAPI submission, or by the Pickup or Replay directories. This stage involves resolving senders and recipients and performing distribution group The OnSubmittedMessage event is exposed to the MExRuntime engine, and any agents that are registered to this event run at this time.
 

Resolve Recipients

This stage involves resolving senders and recipients, performing distribution group expansion, restriction checking and message bifurcation.

OnResolvedMessage

  

This event is triggered after all recipients have been resolved but before the next hop has been determined for each recipient. The OnResolvedMessage event is exposed to the MExRuntime engine, and any agents that are registered to this event run at this time.
 

Routing & Topology

This stage involves using the server's routing table to determine the appropriate path for each recipient in a message.

OnRoutedMessage

  

This event is triggered after messages have been categorized, distribution groups have been expanded, and recipients have been resolved. This stage also exposes the OnRoutedMessage event to the MEx Runtime engine. Any transport agents that are registered to this event run at this time.
 

Content Conversion

This stage involves content conversion for messages based on client specific settings, such as Client Internet Encoding Preference, Client Rich Text preference, and Global Domain Configuration settings. During content conversion, the Hub Transport server inspects the recipients of the message to determine how the message should be formatted.
 

Bifurcation by Recipient Settings

Based on the content conversion needs of the recipients, messages may be further bifurcated.

OnCategorizedMessage

  

The OnCategorizedMessage event was added starting with Microsoft Exchange Server 2007 Update Rollup 4 and is included together with exExchange2k10. This event is designed to provide Transport agent developers a way to run agents or events after content conversion or message bifurcation. Exchange 2010 uses this event together with the Journal Report Decryption agent to provide decrypted journal reports.
 

Stuff and DSN

This represents the final stage of categorization. This stage is responsible for generating any required Delivery Status Notification messages.

To perform message restriction checks or message routing, the Categorizer must be able to uniquely identify the message recipient.

Understanding Transport Agents

Understanding Transport Pipeline

User Action

To troubleshoot this issue, 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.

  • Examine the message recipient's primary SMTP address to determine whether it is associated with more than one object in Active Directory.

  • Install the latest service pack or update rollup package for exExchange2k10.

  • Increase diagnostics logging on the components in the transport pipeline. To do this, follow these steps:

    1. In the Exchange Server 2010 Management Console, expand Server Configuration, and then click Hub Transport.

      Note   For an Edge Transport server, click Edge Transport.

    2. In the Actions pane, click Manage Diagnostic Logging Properties for the appropriate server.

    3. Expand MSExchangeTransport.

    4. Click the following components, and then click Expert, then click Configure for each component:

    • Smtpreceive

    • Smtpsend

    • DSN

    • Components

    • Remote Delivery

    • Categorizer

  • If you are moving mailboxes from one Microsoft Exchange organization to Exchange 2010, verify that the affected recipient has logged on to the new Exchange 2010 mailbox by using Microsoft Outlook or OWA.

  • Use the Queue Viewer tool in the Exchange Toolbox to examine the message queues. If the unreachable destinations queue has messages for the affected user, clear the queued messages, and then test message transfer.

  • 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 about the transport pipeline in Exchange 2010, see Understanding Transport Pipeline.To obtain transport architecture diagrams, see the Exchange Server Team blog article, Exchange 2010 Transport Architecture Diagrams Available for Download.

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.