Announcement

Collapse
No announcement yet.

Exchange 'does not have enough resources avaliable'

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Exchange 'does not have enough resources avaliable'

    Hi all,

    I hope you can help, we have an Exchange 2010 environment and the following NDR has come back on a number of emails on a specific database. The emails being sent are internal and contain an attachment of about 5MB.

    The code provided in the NDR is so generic and the error code given doesn't seem to tally up with any known NDR codes. Has anyone seen anything like this before or could provide an explanation as to what resources are being exceeded?

    We have tried moving the mailbox to another Exchange database but after a number of months the issue returns.

    Any help appreciated.

    Thanks
    Richard
    Last edited by rich.mullins; 30th May 2017, 13:18.

  • #2
    What are the specs (hard and software) of the Exchange server?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Hi Ossain,

      The hardware and software specs are as follows for the Exchange 2010 Server - if you need further info please let me know:

      Exchange 2010 (Update Rollup 11)
      Windows Server 2008 R2 SP1 (64bit)
      Intel Xeon E5640 @ 2.67Ghz (Dual core)
      144GB RAM

      Thanks
      Richard

      Comment


      • #4
        How about drive space
        Are logs and databases on separate arrays?
        Tom Jones
        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
        PhD, MSc, FIAP, MIITT
        IT Trainer / Consultant
        Ossian Ltd
        Scotland

        ** Remember to give credit where credit is due and leave reputation points where appropriate **

        Comment


        • #5
          Hi Ossian,

          Apologies for the delay, I will check and come back to you.

          Thanks

          Comment


          • #6
            Hi Ossian,

            Our databases are on one hard drive partition (D and our logs are on another partition (E but both on same hard drive.

            Thanks
            Richard

            Comment


            • #7
              OK, that is generally bad for an Exchange server - best practice is to have databases and logs on separate disk spindles.
              Also if you have both on a single hard drive, is there any redundancy if the drive fails?
              Tom Jones
              MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
              PhD, MSc, FIAP, MIITT
              IT Trainer / Consultant
              Ossian Ltd
              Scotland

              ** Remember to give credit where credit is due and leave reputation points where appropriate **

              Comment


              • #8
                The mechanism that is causing this is called Back Pressure. You can read up on how it works here: https://technet.microsoft.com/en-us/...xchg.141).aspx

                You should be able to look through your event logs for the IDs listed in this section to find the cause of the back pressure.
                Regards,
                Jeremy

                Network Consultant/Engineer
                Baltimore - Washington area and beyond
                www.gma-cpa.com

                Comment


                • #9
                  Thanks for your advice guys, I'll have a read through the articles provided.

                  Comment

                  Working...
                  X