Friday, February 10, 2017

Resource Monitoring and 452 4.3.1 Insufficient system resources in Exchange

The problem

A client has this issue recently on Exchange server 2013 SP1 (works for all versions of exchange server from 2007 to 2016 (2010,2013). This happens because of the lack of free space in the transport server (2010) or mailbox server role 2013/2016. The specific error was: "Resource Monitoring and 452 4.3.1 Insufficient system resources."

The Solution

1. Check the Local space for the logs and for the edb (files on the exchange server)

a. Open a Powershell for exchange or simple powershell with administrative privilegies (using Run as Administrator):


b. Run my script from technet at to check Database (.EDB file) and and Logs size in the server

The correct way to run the script will be as follows

#Change Executionpolicy,
Set-ExecutionPolicy unrestricted
#Run the script (move to the folder where the script is downloaded) 
#Ex: in the downloads of the user 'joseo'
cd "C:\Users\joseo\Downloads"

You will get something like this:

Note: Please Do not modify the edgetransport.exe.config file, it's a bad practice, and it's just a workaround NOT a solution


2. Enable circular logs on the Exchange Server databases

The Easiest way to check if your server has enabled or not this feature, open an exchange PowerShell console and run:

#Checking CircularLogging exchange 2010/2013/2016
#You will get the True/false result and the name of the database.
get-MailboxDatabase | select Name,CircularLoggingEnabled

#To Enable it
Get-MailboxDatabase| Set-MailboxDatabase -CircularloggingEnabled:$true
On exchange server 2007 will be like this:
And you can also do it graphically by doing the following this steps:
After that it will be necessary to unmount and mount again all the databases.


3. Create a Windows Backup with 'VSS Full Backup'

Here's the technet article to do this:


And that's it! thank you for reading

#when you got the results just return the execution policy #(when you finished working with PowerShell scripts, as a good practice ) Set-ExecutionPolicy remotesigned

Please consider to donate and thank you very much for reading this.

No comments:

Post a Comment