none
Event ID 1040 MSExchaneg Transport Delivery generates every 15 minutes

    Question

  • Hi All,

    Need your help in resolving the error, I am getting the below events every 15 min (EXc2013 CU8) , Only few users complained emails are getting delayed

    Event ID : 1040

    Source: MS Exchange transport delivery

    The SMTP availability of the receive connector default mailbox delivery was low(0 percent)  in the last 15 minutes.

    Regards

    Mohammed Eliyas

    Saturday, October 15, 2016 7:38 AM

Answers

  • Hi,

    Based on error message, it might be caused by Mailbox deliveries throttling setting, please try to increase the throttling setting for mailbox deliveries throttling for testing:
    Set-MailboxTransportService -MaxConcurrentMailboxDeliveries 100
    Set-TransportService -MaxConcurrentMailboxDeliveries 100

    Besides, please run below command to monitor whether there're lots of messages contain large attachment:

    Get-MessageTrackingLog -Resultsize unlimited -Start "10/17/2016 00:00:00" | Select Sender,Subject,Recipients,Totalbytes | where {$_.Totalbytes -gt "1048576"}

    Allen Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 17, 2016 10:05 AM
    Moderator

All replies

  • Well, the first thing I would do is apply CU14 since CU8 is more than a year and a half old.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Saturday, October 15, 2016 5:26 PM
    Moderator
  • Hi,

    Based on error message, it might be caused by Mailbox deliveries throttling setting, please try to increase the throttling setting for mailbox deliveries throttling for testing:
    Set-MailboxTransportService -MaxConcurrentMailboxDeliveries 100
    Set-TransportService -MaxConcurrentMailboxDeliveries 100

    Besides, please run below command to monitor whether there're lots of messages contain large attachment:

    Get-MessageTrackingLog -Resultsize unlimited -Start "10/17/2016 00:00:00" | Select Sender,Subject,Recipients,Totalbytes | where {$_.Totalbytes -gt "1048576"}

    Allen Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 17, 2016 10:05 AM
    Moderator
  • Hello,

    cloud you please to use the following commands and give me a feedback

    Get-TransportServer | get-queue | where{$_.MessageCount -gt 0}

    get-messagetrackinglog -resultsize unlimited -start "00/00/0000 00:00:00" | select sender, subject, recipients,totalbytes | where {$_.totalbytes -gt "102400"}

    Best Regards

    Yassine BOUNIF

    Wednesday, October 19, 2016 4:53 PM
  • Have the same error occurring every 15 minutes, not due to lack of free disk space for logs - or the size of attachments.   Email delivery seems fine even with the log filling up with these 1040 errors.    

    That get-messagetrackinglog command above will generate a massive output on many servers.  List every message since the beginning of time with an attachment greater than 100K?      Don't see the point of that.

    Tuesday, December 20, 2016 7:11 PM
  • According to this blog, this is a known issue to Microsoft with Exchange 2013 CU9 and up  (With CU9  there is a new Transport Agent called System Probe Drop SMTP Agent.)  The problem server i'm on is CU10, and of Oct 2016 there is no way to suppress these errors.     

    http://www.therealcontoso.com/blog/2016/10/13/the-smtp-availability-of-the-receive-connector-default-was-low


    Running this command will show what messages are failing.   

    Get-MessageTrackingLog -ResultSize unlimited -Server %servername% -EventID FAIL

    If the recipient on EventId FAIL messages is {HealthMailbox3c45... they can safely be ignored. 



    Perhaps Allen Wang, Zi Feng and others marking non-answer 'answers', should talk to Microsoft.






    • Proposed as answer by MSCS Tuesday, December 20, 2016 8:11 PM
    Tuesday, December 20, 2016 8:09 PM