none
Exchange insufficient resources in MEG RRS feed

  • Question

  • Hi Experts,


    Seeking your assistance regarding this concern. We are seeing Insufficient Resources status in our MEG for drive D of our Exchange server 10.7.4.243 even it has enough space, this is causing email ques.  Please refer to the screenshots below. Thanks!

    Has any solution on this ? or any recommendation for this. Appreciate your quick responds. 



    Homer Sibayan



    Monday, June 10, 2019 3:05 AM

Answers

  • Hi,

    Do you get any Application event logs from Event Viewer? You can post the screenshot here, and please don't forget to cover your personal information.

    Back Pressure may be one of the reasons behind this 452 4.3.1 insufficient system resources error. Back pressure detects when vital system resources, such as hard drive space and memory, are overused, and takes action to prevent the server from becoming completely overwhelmed and unavailable.

    As you mentioned, "Increase the amount of free space on the Microsoft Exchange server drive" may help you solve this issue. You can try to clean up some logs to increase drive space. You can use Windows Server Backup to back up Exchange data, and a VSS full backup can be selected. It allows the transaction logs for the databases on the selected volumes to be truncated at the completion of a successful backup.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, June 11, 2019 7:38 AM
    Moderator

All replies

  • Hi

    Can you provide more information? are the databases stored on drive D:\ and is this on a SAN or direct attached storage?


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, June 10, 2019 9:04 AM
    Moderator
  • Hi ,

    Insufficient Resources in MEG due to running out of space in the Disk or free  up drive Volume (D:\) . We have checked already the Queue Viewer with no any errors and issues . Can someone knows how can i resolve this kind of issue? or can someone tell us how to and what is the best approach to check this. 

    Solution / Workaround : Is this advisable ? 

    The '452 4.3.1 Insufficient system resources' error is originating from the Microsoft Exchange server due to the server either running out of disk space or free memory. To address this: 
    • Increase the amount of free space on the Microsoft Exchange server drive
    • Reduce the amount of memory being used by all processes

    Please see the attached screenshot. 


    Homer Sibayan


    • Edited by Remoh_10 Friday, June 14, 2019 2:23 AM
    Tuesday, June 11, 2019 1:43 AM
  • Hi,

    Do you get any Application event logs from Event Viewer? You can post the screenshot here, and please don't forget to cover your personal information.

    Back Pressure may be one of the reasons behind this 452 4.3.1 insufficient system resources error. Back pressure detects when vital system resources, such as hard drive space and memory, are overused, and takes action to prevent the server from becoming completely overwhelmed and unavailable.

    As you mentioned, "Increase the amount of free space on the Microsoft Exchange server drive" may help you solve this issue. You can try to clean up some logs to increase drive space. You can use Windows Server Backup to back up Exchange data, and a VSS full backup can be selected. It allows the transaction logs for the databases on the selected volumes to be truncated at the completion of a successful backup.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, June 11, 2019 7:38 AM
    Moderator
  • Just checking in to see if above information was helpful. 

    Did making a VSS full backup help solve your issue? If you have any questions or need further help on this issue, please feel free to post back. 

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, June 17, 2019 11:49 AM
    Moderator