rmegni
asked on
4.3.1 Insufficient System Resources on Exchange 2007
Hi,
My client has been reporting intermittent email flow when receiving email. They will go for stretches of hours without receiving email. I checked the boards and found suggestions on telneting to the server and using the command MAIL FROM:admin@test.com. This returns the 4.3.1 Insufficient System Resources message.
I edited the EdgeTransport.exe.config file and disabled Back Pressure setting and changed the Queue path to the D drive and restarted the Transport service as well as the server. In both cases, the email is not flowing and I still receive the above message when telneting.
They are using SBS2008 server.
Any suggestions are appreciated.
Rick
My client has been reporting intermittent email flow when receiving email. They will go for stretches of hours without receiving email. I checked the boards and found suggestions on telneting to the server and using the command MAIL FROM:admin@test.com. This returns the 4.3.1 Insufficient System Resources message.
I edited the EdgeTransport.exe.config file and disabled Back Pressure setting and changed the Queue path to the D drive and restarted the Transport service as well as the server. In both cases, the email is not flowing and I still receive the above message when telneting.
They are using SBS2008 server.
Any suggestions are appreciated.
Rick
madhatter5501
check the space on all the hard drives, most likely there are still some logs on the c: drive building up and causing this issue
ASKER
Hi,
Can you be more specific? What folder paths should i check?
Thanks
Can you be more specific? What folder paths should i check?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This can only be back pressure,
Check the event log and you will know what is causing the back pressure.
Clear the log and restart the transport service
Check the event log and you will know what is causing the back pressure.
Clear the log and restart the transport service
ASKER
I only changed the value with key QueueDatabasePath to the D drive where there is over 1Tb of drive space available.
Should I redirect the key QueueDatabaseLoggingPath as well?
Should I redirect the key QueueDatabaseLoggingPath as well?
yes
then restart the transport service like recommended above, if that doesn't work, the restart the server
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
nice article, good way to get the server going quick for clean up later
Thanks - That's the plan.
ASKER
Hi Guys,
Once I redirected the Log path all is good.
Thanks! You guys were terrific at helping me quickly solve this for my client.
Rick
Once I redirected the Log path all is good.
Thanks! You guys were terrific at helping me quickly solve this for my client.
Rick
Backpressure is a great 'feature' if you haven't come across it before - but the Insufficient Resources message = Backpressure has kicked in.
Need to get your client to keep on top of their disk space to make sure that Backpressure doesn't bite them on the backside again. Are they taking backups with an Exchange Aware backup program?
Need to get your client to keep on top of their disk space to make sure that Backpressure doesn't bite them on the backside again. Are they taking backups with an Exchange Aware backup program?
ASKER
No. Any good recommendations?
I like the built in Windows Backup, there is also a few other paid backup solutions but for me the built in backup works good
Use the built-in SBS backup - it will purge the Exchange logs happily.
You can plug in an external HDD or an internal HDD dedicated to holding the backups (the larger the better) and then configure the backups to use the drive, then the logs shouldn't consume huge amounts of space and the issue should happen again (for the same reason).
As you have SBS - which includes WSUS, disable the logs in IIS for the WSUS virtual Directory and then purge the logs - they will grow and chew up your C: drive very quickly.
You can plug in an external HDD or an internal HDD dedicated to holding the backups (the larger the better) and then configure the backups to use the drive, then the logs shouldn't consume huge amounts of space and the issue should happen again (for the same reason).
As you have SBS - which includes WSUS, disable the logs in IIS for the WSUS virtual Directory and then purge the logs - they will grow and chew up your C: drive very quickly.
ASKER
Excellent! Thanks.
You're welcome. I have found the WSUS logs eating about 30Gb of disk space! As if anyone is going to look through them :)
Any reason why after I canged the line to false all emails trying to be sent are going into the draft folder and not being sent now?