none
Exchange Server 2003/2010 Coexistence Mail-flow Issues RRS feed

  • Question

  • I've installed Exchange 2010 in a 2003 coexistence scenario. 2010 was deployed with CAS,HUB, and Mailbox roles. 

    The installation went through smoothly, and the default RGC was created.

    On the 2010 Server, when I create a new users with mailbox, that user is no able to send or receive mail from anywhere.

    2010 user to 2010 user does not work
    2003 user to 2010 user does not work

    Mail delivery between 2003 users works fine. 

    The RGC message queue in ESM 2003 shows that the messages are queued and keep retrying. 
    I have deleted the RGC twice and created new ones, I have un-installed the HUB and CAS roles and re-installed them, and I have also re-run setup /preparead and setup /preparelegacyexchangepermissions

    I'm not able to make any sense of the message tracking on the 2010 side. It just shows a bunch of entries: 

    EventID: NOTIFYMAPI

    Source: STOREDRIV 

    When I use the best practices analyzer to test mailflow to a 2010 user from the outside, the test comes back with a pass even though the message itself isn't delivered to the specified mailbox. 

    There is no smart host defined on the default SMTP virtual server on 2003.
    There is no SMTP Send Connector for External or Internal mail configured on 2003 besides the 2010 RGC

    Any ideas?

    Here is the mail flow analyzer result:
         Testing inbound SMTP mail flow for domain 'user01@test.com'.
         Inbound SMTP mail flow was verified successfully.
         
         Additional Details
         
    Elapsed Time: 3437 ms.
         
         Test Steps
         
         Attempting to retrieve DNS MX records for domain 'test.com'.
         One or more MX records were successfully retrieved from DNS.
         
         Additional Details
         
    MX Records Host mail.test.com, Preference 0
    , Host test.com, Preference 10
    Elapsed Time: 110 ms.
         Testing Mail Exchanger mail.test.com.
         This Mail Exchanger was tested successfully.
         
         Additional Details
         
         Test Steps
         
         Attempting to resolve the host name mail.test.com in DNS.
         The host name resolved successfully.
         
         Additional Details
         Testing TCP port 25 on host mail.test.com to ensure it's listening and open.
         The port was opened successfully.
         
         Additional Details
         
    Banner received: 220 EX2K3w2K3.test.net Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Wed, 5 Feb 2014 14:40:44 -0500
    Elapsed Time: 368 ms.
         Analyzing SMTP Capabilities for server mail.test.com:25
         SMTP Capabilities were analyzed successfuly.
         
         Additional Details
         Attempting to send a test email message to user01@test.com using MX mail.test.com.
         The test email message was delivered successfully.
         
         Additional Details
         
    Elapsed Time: 621 ms.
         Testing the MX mail.test.com for open relay by trying to relay to user Admin@TestExchangeConnectivity.com.
         The Open Relay test passed. This MX isn't an open relay.
         
         Additional Details
         Testing Mail Exchanger test.com.
         This Mail Exchanger was tested successfully.
         
         Additional Details
         
         Test Steps
         
         Attempting to resolve the host name test.com in DNS.
         The host name resolved successfully.
         
         Additional Details
         Testing TCP port 25 on host test.com to ensure it's listening and open.
         The port was opened successfully.
         
         Additional Details
         Analyzing SMTP Capabilities for server test.com:25
         SMTP Capabilities were analyzed successfuly.
         
         Additional Details
         Attempting to send a test email message to user01@test.com using MX test.com.
         The test email message was delivered successfully.
         
         Additional Details
         Testing the MX test.com for open relay by trying to relay to user Admin@TestExchangeConnectivity.com.
         The Open Relay test passed. This MX isn't an open relay.
         
         Additional Details
    Wednesday, February 5, 2014 9:08 PM

Answers

  • No duplicate security groups. I did notice Exchange 2010 is not in the Exchange Domain Servers group, but 2k3 is. Not sure if that matters. 

    In the Application event log I'm seeing this error a lot.

    Log Name:      Application
    Source:        MSExchangeMailSubmission
    Date:          05/02/2014 3:02:31 PM
    Event ID:      1009
    Task Category: MSExchangeMailSubmission
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ex2010w2k8.test.net
    Description:
    The Microsoft Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeMailSubmission" />
        <EventID Qualifiers="49156">1009</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-05T20:02:31.000000000Z" />
        <EventRecordID>6530</EventRecordID>
        <Channel>Application</Channel>
        <Computer>ex2010w2k8.test.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>HubTransport</Data>
      </EventData>
    </Event>


    As long as you cannot send email between ex2010 users this has nothing to do with connectors/smtp config..

    I had the same issue one year ago and solved adding both sevrers to old/new exchange sevrers security groups.

    Looks like for some missing security entry (not sure why) mailbox is unable to conact HUB  (MSExchangeMailSubmission) I expect you seing items stuck in draft for owa (outbok for outlook)

    I saw in some blogs similar cases solved by setting static DNS servers for HUB severs config.

    • Marked as answer by Methodman85 Friday, February 7, 2014 2:59 PM
    Wednesday, February 5, 2014 10:07 PM

All replies

  • Any relevant events on 2010 hub/mbx ?

    Check exchange security groups  in AD? are they duplicated?

    Wednesday, February 5, 2014 9:40 PM
  • No duplicate security groups. I did notice Exchange 2010 is not in the Exchange Domain Servers group, but 2k3 is. Not sure if that matters. 

    In the Application event log I'm seeing this error a lot.

    Log Name:      Application
    Source:        MSExchangeMailSubmission
    Date:          05/02/2014 3:02:31 PM
    Event ID:      1009
    Task Category: MSExchangeMailSubmission
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ex2010w2k8.test.net
    Description:
    The Microsoft Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeMailSubmission" />
        <EventID Qualifiers="49156">1009</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-05T20:02:31.000000000Z" />
        <EventRecordID>6530</EventRecordID>
        <Channel>Application</Channel>
        <Computer>ex2010w2k8.test.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>HubTransport</Data>
      </EventData>
    </Event>


    Wednesday, February 5, 2014 9:56 PM
  • First check if any smart host Present in default SMTP server in exchange 2003 if so please remove it first and check

    Check in the Default SMTP Virtual Server in Exchange 2003  in the configure Tab if there is any ip address if so  remove the same.

    Run IISreset  and check
    remove authentication on virtual smtp on exchange 2003 if any

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.

    Regards,
    Sathish

    Wednesday, February 5, 2014 9:59 PM
  • No duplicate security groups. I did notice Exchange 2010 is not in the Exchange Domain Servers group, but 2k3 is. Not sure if that matters. 

    In the Application event log I'm seeing this error a lot.

    Log Name:      Application
    Source:        MSExchangeMailSubmission
    Date:          05/02/2014 3:02:31 PM
    Event ID:      1009
    Task Category: MSExchangeMailSubmission
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ex2010w2k8.test.net
    Description:
    The Microsoft Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeMailSubmission" />
        <EventID Qualifiers="49156">1009</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-05T20:02:31.000000000Z" />
        <EventRecordID>6530</EventRecordID>
        <Channel>Application</Channel>
        <Computer>ex2010w2k8.test.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>HubTransport</Data>
      </EventData>
    </Event>


    As long as you cannot send email between ex2010 users this has nothing to do with connectors/smtp config..

    I had the same issue one year ago and solved adding both sevrers to old/new exchange sevrers security groups.

    Looks like for some missing security entry (not sure why) mailbox is unable to conact HUB  (MSExchangeMailSubmission) I expect you seing items stuck in draft for owa (outbok for outlook)

    I saw in some blogs similar cases solved by setting static DNS servers for HUB severs config.

    • Marked as answer by Methodman85 Friday, February 7, 2014 2:59 PM
    Wednesday, February 5, 2014 10:07 PM
  • First check if any smart host Present in default SMTP server in exchange 2003 if so please remove it first and check

    Check in the Default SMTP Virtual Server in Exchange 2003  in the configure Tab if there is any ip address if so  remove the same.

    Run IISreset  and check
    remove authentication on virtual smtp on exchange 2003 if any

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.

    Regards,
    Sathish

    No smarthost

    No ips being denied

    No certificate on the SMTP virtual server

     
    Wednesday, February 5, 2014 10:32 PM
  • No duplicate security groups. I did notice Exchange 2010 is not in the Exchange Domain Servers group, but 2k3 is. Not sure if that matters. 

    In the Application event log I'm seeing this error a lot.

    Log Name:      Application
    Source:        MSExchangeMailSubmission
    Date:          05/02/2014 3:02:31 PM
    Event ID:      1009
    Task Category: MSExchangeMailSubmission
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ex2010w2k8.test.net
    Description:
    The Microsoft Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeMailSubmission" />
        <EventID Qualifiers="49156">1009</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-05T20:02:31.000000000Z" />
        <EventRecordID>6530</EventRecordID>
        <Channel>Application</Channel>
        <Computer>ex2010w2k8.test.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>HubTransport</Data>
      </EventData>
    </Event>


    As long as you cannot send email between ex2010 users this has nothing to do with connectors/smtp config..

    I had the same issue one year ago and solved adding both sevrers to old/new exchange sevrers security groups.

    Looks like for some missing security entry (not sure why) mailbox is unable to conact HUB  (MSExchangeMailSubmission) I expect you seing items stuck in draft for owa (outbok for outlook)

    I saw in some blogs similar cases solved by setting static DNS servers for HUB severs config.

    Yes that is similar to what I'm experiencing.

    When using the Outlook client with a 2010 mailbox the mail leaves the outbox fine. When using OWA new messages just get saved as drafts when I try to send them.

    I will try your suggestions. I see two groups. Exchange Domain Servers, and Exchange Enterprise Servers of which Exchange Domain Servers is a member.

    Wednesday, February 5, 2014 10:35 PM
  • Added both servers to all the Exchange related Security groups I could find.

    And I specified the internal DNS lookup IP address for the hub transport. Still the same issue.

    I'm thinking a fresh install may be in order. 

    Wednesday, February 5, 2014 11:03 PM
  • I suggest you put the MSExchangeMailSubmission logging level to expert (by default it is lowest)

    This should reveal more details on why mailbox cannot conact hub server. (intersting events are expected on mailbox app log!)

    Hope that help!

    Thursday, February 6, 2014 7:56 AM
  • The server had 1.5GB of free space, I added an additional 5GB after adding to the security groups etc like you suggested. The next day the mail just started flowing. Not sure exactly what caused it to start working. As I rebooted multiple times after adding the space and modifying the security groups. very strange.
    Friday, February 7, 2014 4:30 PM
  • The server had 1.5GB of free space, I added an additional 5GB after adding to the security groups etc like you suggested. The next day the mail just started flowing. Not sure exactly what caused it to start working. As I rebooted multiple times after adding the space and modifying the security groups. very strange.

    If this is related to free space issue you would "back pressure" events

    http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/back-pressure-exchange-2010-part1.html

    By the way after adding the servers to the security groups a reboot is required..

    Friday, February 7, 2014 9:18 PM