none
Unable to send emails to internet after Exchange CU15 upgrade

    Question

  • We recently upgraded from Exchange 2013 CU6 to CU15. After upgrade users are unable to send emails to internet. They are able to receive emails. Internal mail flow is working fine. We are getting the following errors in event viewer 

    Log Name:      Application
    Source:        MSExchangeFrontEndTransport
    Date:          1/16/2017 4:18:03 PM
    Event ID:      1049
    Task Category: SmtpReceive
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      xxx.xxx.local
    Description:
    SMTP could not find any destinations to proxy to. SMTP session details: [SmtpInSession: SessionId=636202031352468541 ConnectionId=282]

    Log Name:      Application
    Source:        MSExchangeFrontEndTransport
    Date:          1/16/2017 4:20:21 PM
    Event ID:      5039
    Task Category: Routing
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      xxx.xxx.local
    Description:
    Routing failed to select any Mailbox servers to proxy a mail item to in routing tables with timestamp 1/17/2017 12:17:05 AM. Transport process role: FrontEnd. Recipient databases: .

    • Verified all Server Component State is active. 2 components ForwardSyncDaemon & ProvisioningRps were inactive. Set them to active.
    • Created a new Send Connector but still we were getting the same events.
    • Verified in ADSIEDIT and made sure that there are no stale entries of any Exchange server.
    • Created Host file entry for FQDN and NetBIOS name  of Exchange server, DCs and their respective IPs.
    • Verified AD replication was healthy.
    • Increased Protocol logs on Send connector and found that logs were not generated.
    • Performed message tracking and found the error. "Stage:CommitMailItem, SmtpResponse:441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10061, Win32 error code: 10061."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 192.168.46.1:2525" 

    I was not able to find any helpful articles to fix the issue. Please advice. 



    Regards, Naveen Devadiga

    Tuesday, January 17, 2017 5:34 PM

Answers

  • I managed to fix the issue. I set the ServerComponentState to inactive and then Set it active issue was fixed. it was a strange issue.

    Followed the below Steps:-

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester Functional -Component $_.Component -State InActive }

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester HealthApi -Component $_.Component -State InActive }

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester Maintenance -Component $_.Component -State InActive }

     

    # Restarted Microsoft Exchange Active directory Topology Service.

     

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester Functional -Component $_.Component -State Active }

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester HealthApi -Component $_.Component -State Active }

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester Maintenance -Component $_.Component -State Active }

     

    # Restarted Microsoft Exchange Active directory Topology Service.

    # Issue Resolved.


    Regards, Naveen Devadiga

    Tuesday, January 17, 2017 7:29 PM

All replies

  • We recently upgraded from Exchange 2013 CU6 to CU15. After upgrade users are unable to send emails to internet. They are able to receive emails. Internal mail flow is working fine. We are getting the following errors in event viewer 

    Log Name:      Application
    Source:        MSExchangeFrontEndTransport
    Date:          1/16/2017 4:18:03 PM
    Event ID:      1049
    Task Category: SmtpReceive
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      xxx.xxx.local
    Description:
    SMTP could not find any destinations to proxy to. SMTP session details: [SmtpInSession: SessionId=636202031352468541 ConnectionId=282]

    Log Name:      Application
    Source:        MSExchangeFrontEndTransport
    Date:          1/16/2017 4:20:21 PM
    Event ID:      5039
    Task Category: Routing
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      xxx.xxx.local
    Description:
    Routing failed to select any Mailbox servers to proxy a mail item to in routing tables with timestamp 1/17/2017 12:17:05 AM. Transport process role: FrontEnd. Recipient databases: .

    • Verified all Server Component State is active. 2 components ForwardSyncDaemon & ProvisioningRps were inactive. Set them to active.
    • Created a new Send Connector but still we were getting the same events.
    • Verified in ADSIEDIT and made sure that there are no stale entries of any Exchange server.
    • Created Host file entry for FQDN and NetBIOS name  of Exchange server, DCs and their respective IPs.
    • Verified AD replication was healthy.
    • Increased Protocol logs on Send connector and found that logs were not generated.
    • Performed message tracking and found the error. "Stage:CommitMailItem, SmtpResponse:441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10061, Win32 error code: 10061."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 192.168.46.1:2525" 

    I was not able to find any helpful articles to fix the issue. Please advice. 



    Regards, Naveen Devadiga


    Are you smarthosting from the send connector or sending out directly to the internet via DNS?

    Blog:    Twitter:   

    Tuesday, January 17, 2017 5:48 PM
  • It is directly sending out to internet. No smart host!!

    Regards, Naveen Devadiga

    Tuesday, January 17, 2017 6:23 PM
  • It is directly sending out to internet. No smart host!!

    Regards, Naveen Devadiga

    What is the IP? 192.168.46.1:2525

    It looks the issue is when it tries to send the message to another mailbox server, not out to the internet.


    Blog:    Twitter:   

    Tuesday, January 17, 2017 6:36 PM
  • I managed to fix the issue. I set the ServerComponentState to inactive and then Set it active issue was fixed. it was a strange issue.

    Followed the below Steps:-

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester Functional -Component $_.Component -State InActive }

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester HealthApi -Component $_.Component -State InActive }

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester Maintenance -Component $_.Component -State InActive }

     

    # Restarted Microsoft Exchange Active directory Topology Service.

     

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester Functional -Component $_.Component -State Active }

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester HealthApi -Component $_.Component -State Active }

    Get-ServerComponentState  ExchangeServer | % { Set-ServerComponentState  ExchangeServer -Requester Maintenance -Component $_.Component -State Active }

     

    # Restarted Microsoft Exchange Active directory Topology Service.

    # Issue Resolved.


    Regards, Naveen Devadiga

    Tuesday, January 17, 2017 7:29 PM