none
Receive connector error : 452 4.3.1 Insufficient system resources. No back pressure event RRS feed

  • Question

  • Hi ,

    I have Exchange 2013 server configured as a multirole (cas+mbx) that is rejecting messages .

    I started the verbose logging of the receive connector and notice that sometimes the response from the server was

    452 4.3.1 Insufficient system resources.

    I don't have back pressure events and my Transport Database has a lot of free space.

    Any ideas ?

    Exchange 2013 CU7

    Error from managed availability

    Mailbox Transport Submission - the verification that the probe messages were successfully submitted within 5 minutes to HUB has failed. 
          This could indicate that the mailbox submissions are taking too long or not progressing at all.
          SequenceNumber: 635708989783012831
    	   
          Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
          FailureContext: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
          ExecutionContext: MapiSubmitLAMProbe started. This performs - 1. Submits a new message to Store 2. Checks results from previous Send Mail operation. Sequence # = 635708989783012831. First Run? = False. Previous mail submission to store was successful. Results -  # of previous results: 0.  Could Not Find stages that ran.  Previous SendMail failure -  Mail submitted to Store during the previous run never reached SendAsCheck. 
                            This may indicate a latency from Store to Submission Service. Investigating.  Found lower SA latency. Indicates an issue in Submission service. 
                                Investigate. In SendMail -  NotificationID=00000050-0000-0000-0000-00004489f5df Sending mail. SendMail finished. MapiSubmitLAMProbe finished with CheckPreviousMail failure. 
          CheckPreviousRunMail exception details: 
          Current SendMail exception details: 
           
          MailWasSentInLastRun (0(no)/1(yes)): 1
          CheckMailSuccess(0(no)/1(yes)): 0
          SendMailSuccess(0(no)/1(yes)/2(no-noMDBs)/3(no-noActiveMDBs)/4(no-ignorableException)): 1
           
          PreviousMailLatencies: <2816a467fc6e4df58602517b149c0d3d@ex01.cosanostra-bg.com>,,2015-06-29T19:24:24.120Z;LSRV=ex01.cosanostra-bg.com:TOTAL-SUB=0.515|SA=0.031|MTSSDPL=0.011|MTSSDSS=0.013;;<c553276a7fdc48bb971696959d0d2e12@ex01.cosanostra-bg.com>,,2015-06-29T19:19:24.074Z;LSRV=ex01.cosanostra-bg.com:TOTAL-SUB=0.312|SA=0.031|MTSSDPL=0.011|MTSSDSS=0.012;;<555848d05c0e4141a7c441ff0fdb294b@ex01.cosanostra-bg.com>,,2015-06-29T19:14:23.902Z;LSRV=ex01.cosanostra-bg.com:TOTAL-SUB=5.593|SA=5.249|MTSSDPL=0.006|MTSSDSS=0.014;;
          GetPreviousMailLatencyFailures: 
           
          (The following are applicable if the mail was actually sent)
          MailSentAt: 29.6.2015 19:29:24
          TimeInSendingToStore: 125,0239
          Sent Mail Result Details:
            (InternetMessageId:<3fd1eb6e77e74b78a40ebd213ca3dbd9@ex01.cosanostra-bg.com>;
            ItemEntryId:0 0 0 0 B2 A1 18 B5 9C ED 46 4E 9A BE D6 7B 72 A 16 42 7 0 F6 1E 9B BD D4 78 81 4E 82 A BD AE 4 39 B5 43 0 0 0 0 1 B 0 0 F6 1E 9B BD D4 78 81 4E 82 A BD AE 4 39 B5 43 0 0 44 C5 DF 36 0 0 )
            Properties of Sending mail 
            (Subject:00000050-0000-0000-0000-00004489f5df-MapiSubmitLAMProbe;
            Sender:HealthMailboxad7d1178cd2f4d89a176adf4adfcd908@cosanostra-bg.com;
            MbxGuid:b3d5201b-e40b-4987-b335-385fb733c354;
            MdbGuid:2a1cd6fa-6435-4ab1-82b2-8b9654e4ee94;
            Recipient:HealthMailboxad7d1178cd2f4d89a176adf4adfcd908@cosanostra-bg.com;
            Body and MessageClass:MessageClass:IPM.Note.MapiSubmitLAMProbe;MessageBody:This is a Probe Mapi message that's Submitted from Store to Mailbox transport Submission service to Hub transport service;
            DoNotDeliver, DropMessageInHub and DeleteAfterSent:DoNotDeliver:True;DropMessageInHub:True;DeleteAfterSubmit:True;)
    Probe Exception: 'System.ApplicationException: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
       at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.PerformProbeFinalAction(Boolean potentialForAlertBasedOnPreviousRun, Boolean potentialForAlertBasedOnCurrentRun, Exception previousRunVerificationException, Exception currentRunException, DateTime timeMessageSentToStore)
       at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWorkInternal(CancellationToken cancellationToken)
       at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWork(CancellationToken cancellationToken)
       at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
       at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
       at System.Threading.Tasks.Task.Execute()'
    Probe Result Name: 'Mapi.Submit.Probe'
    Probe Result Type: 'Failed'
    Monitor Total Value: '0'
    Monitor Total Sample Count: '12'
    Monitor Total Failed Count: '12'
    Monitor Poisoned Count: '0'
    Monitor First Alert Observed Time: '26.6.2015 7:17:58'
    

    Tuesday, June 30, 2015 6:33 AM

Answers

  • Just found the problem. Except that affected Exchange server there was other 4 that doesn't host any services. No mailbox databases ,no one uses them.

    Well one of them was with 0 bytes free on the OSDisk. So no shadow redundancy and no back pressure event on that server.

    Because there is another Server on the same site , shadow redundancy works fine. It seems that this was my major issue for now.Clearing free space and restarting the Exchange transport services fired up Back Pressure event from High to Normal on the affecter server with zero free space.

    How to diagnose this kind of error - Look for FrontEnd connectivity logs , not SMTP verbose logs :)

    Tuesday, June 30, 2015 10:39 AM

All replies

  • Hi Martin,

    Is it rejecting external emails or internal as well. Is it actually causing a failure or delay only.

    This 4.3.1 Insufficient system resources is usually for Back Pressure issue (No sufficient disk space or RAM)

    Do you see anything on the Application event log.

    When you see the error\issue next time Validate the following system resources are in normal:

    Calculate the values for your environment using the article Back Pressure:

    • Free space on the hard drive that stores the message queue database.

    • Free space on the hard drive that stores the message queue database transaction logs.

    • The number of uncommitted message queue database transactions that exist in memory.

    • The memory that's used by the EdgeTransport.exe process.

    • The memory that's used by all other processes.

    • The number of messages in the Submission queue.

    Referneces:

    error 452 4.3.1 no exchange mail being sent
    https://social.technet.microsoft.com/Forums/en-US/ebf60b1b-5fc2-49a6-b83c-b8e28e928287/error-452-431-no-exchange-mail-being-sent?forum=exchangesvrsecuremessaginglegacy


    https://support.microsoft.com/en-us/kb/329167

    ManagedAvailability problem with Mailbox Transport Submission
    https://social.technet.microsoft.com/Forums/en-US/60cd0199-aeca-4215-a2bd-579b5123c427/managedavailability-problem-with-mailbox-transport-submission-after-cu6?forum=exchangesvrgeneral

     

    Back pressure
    https://technet.microsoft.com/en-us/library/bb201658%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396


    Regards,

    Satyajit

    Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Tuesday, June 30, 2015 8:08 AM
  • Hi,

    No event 15004-15007. Disk , CPU and ram are sufficient.Event tried to disable Back Presure in EdgeTransport.exe.config with this key :

    <add key="EnableResourceMonitoring" value="false" /> (Transport services restarted)

    Still my server rejects mails. Internal, external same problem.

    Tuesday, June 30, 2015 8:39 AM
  • Just found the problem. Except that affected Exchange server there was other 4 that doesn't host any services. No mailbox databases ,no one uses them.

    Well one of them was with 0 bytes free on the OSDisk. So no shadow redundancy and no back pressure event on that server.

    Because there is another Server on the same site , shadow redundancy works fine. It seems that this was my major issue for now.Clearing free space and restarting the Exchange transport services fired up Back Pressure event from High to Normal on the affecter server with zero free space.

    How to diagnose this kind of error - Look for FrontEnd connectivity logs , not SMTP verbose logs :)

    Tuesday, June 30, 2015 10:39 AM
  • Is that a beer in your profile picture? Impressive!

    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Tuesday, June 30, 2015 11:10 AM
  • Hi Martin,

    Great, so finally 4.3.1 Insufficient system resources did mean No sufficient disk space.

    Good learning for us to keep an eye on other transport servers in the site as well.


    Regards,

    Satyajit

    Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Wednesday, July 1, 2015 6:04 AM