MSExchangeTransport 2007

 

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

2007

Event Source

MSExchangeTransport

Category

SmtpSend

Symbolic Name

SmtpSendNewSession

Message Text

Send connector %1 has initiated a new session to %2.

Explanation

This event may indicate a message delivery failure between the Send connector on a Microsoft Exchange Server 2010 Transport server and another SMTP server. The SMTPSend component is the transport component that sends messages from the Delivery Queue to other destinations. This event describes a scenario in which the SmtpSend component has started a new session to retry delivery after previously being unable to deliver the message.

This issue may occur if an issue affects the destination domain. For example, this issue may occur if a DNS-related issue hinders obtaining the MX record for the domain or a networking issue.

For more information, see the following topics:

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.

  • Temporarily disable any e-mail antivirus program that may be running on the destination server to determine whether the issue is caused by a third-party program.

  • Determine whether the following conditions are true:

    • The destination server is subscribed to a block list provider

    • The domain or IP address from which the Transport server sends the message is listed on the block list

    You can use third-party tools such as www.mxtoolbox.com to determine whether a domain or IP address is listed on one or more block lists.

  • Determine whether a message size restriction on the destination server is configured to block the affected messages.

  • Determine whether the destination domain has an accessible MX record. To do this, use a third-party program such as www.mxtoolbox.com.

  • Verify that you can resolve the MX record for the affected domain. To do this, use any of the following methods:

    • Examine the hosts file on the Transport server to determine whether any incorrect entries exist.

    • Determine whether any firewall rules are configured that may block DNS queries for specific domains.

    • Log on to a client computer that is pointed to your internal DNS servers. Then, use the Nslookup command to determine whether you can resolve the external domain and the MX record for that domain. For more information about how to use the Nslookup command, see Microsoft Knowledge Base article 200525, Using NSlookup.exe.

    • If you cannot resolve the MX record from a client that is pointed to the internal DNS servers, point the same client computer to an external DNS server, and then repeat the Nslookup requests. For example, point the client computer to 4.2.2.2 for DNS queries.

  • You may want to increase diagnostics logging to log the components in the transport pipeline. To increase diagnostics logging for the Transport components, 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

  • 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.