Exchange 2010 EdgeTransport.exe Memory issue

My client has a hosted Exchange 2010 (SP1) system hosted externally.

Over the weekend we were alerted to the system going into Back Pressure mode:
LogAlert1LogAlert2
Today I downloaded and installed this
http://support.microsoft.com/kb/2787763 and rebooted but that didnt help.

Doing some more research it seemed like a good idea to check the queue to see if there was any dead items in there causing any loops etc. Being hosted this all has to be done in PowerShell.  I found some:
loopsthe first three seem to be the issue. Thats an insane number of retires!! So I want to delete them. Following the subscribed way of removing these I face this error:
PowerShellCapture
Anyone have any ideas before the client hits the roof (and they will!!)

Thanks
Mark
LVL 13
Mark GalvinManaging Director / Principal ConsultantAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Zaheer IqbalTechnical Assurance & ImplementationCommented:
Can you view the queues with exchange management console
0
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
Hi

As above, this server is installed in Hosted Mode (sorry I wasn't clear) and therefore there is no EMC. Everything is done via PowerShell.

Thanks
Mark
0
lciprianionutCommented:
Get-Queue "..DC01\294825" | Get-Message | Remove-Message -WithNDR:$false

To use Remove-Message you need to supply Identity of the message not of the queue.
See cmdlet help in TechNet
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Mohammed TahirMicrosoft Exchange and O365 AdministratorCommented:
You can suspend and remove messages using the powershell. Use the following command:

Get-Message -Filter {FromAddress -eq "<>"} -Server servername | Remove-Message


Tahir
0
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
Hi lciprianionut

I tried that. I get this:
resultesThe message about throttling comes up about 20 times. Then if I check the queues agin I get:
results
Any ideas? These queues are killing the server.

Thanks
Mark
0
lciprianionutCommented:
Try with this
Get-Queue "..DC01\294825" | Get-Message | Remove-Message -WithNDR:$false -Confirm:$false

For your warning most probably you have some Client Throttling Policies in place.
Also here are some info.

Maybe in your case a better solution would be to Export Messages from Queues (also read this) and then delete and recreate the queue again.

After you exported and recreated the queue, you can put back the exported mails back to queue to be send, but not all at once, but in smaller batches.

This is from some document on how to do it, just adapt to your environment.
After this operations we have all messages exported to directory C:\Export_messages, now we can move them to next Hub Transport server to Transport Pickup directory (default location for Exchange 2010: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Pickup)

To find the queue path (from here)
The location of the queue database and queue database transaction logs are controlled by the QueueDatabasePath and QueueDatabaseLoggingPath parameters in the EdgeTransport.exe.config application configuration file that's located in the C:\Program Files\Microsoft\Exchange Server\V14\Bin directory. The following list describes some important items to consider when you change the location of the queue database.

Let me know if all this worked.
Thank you.
0
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
This was causing so many issues that I followed the instructions here http://www.techieshelp.com/exchange-2007-and-exchange-2010-create-new-mail-queu-database/ and renamed the mail.que file. All the email hanging around was dead anyway.

This fixed the issue with memory utilization and stopped Back Pressure.

Thanks all for your help over the last few days.

thanks
Mark
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
Whilst all experts suggestions where helpful to my knowledge of PowerShell and Exchange queues, what fixed the issue was a fix I located myself .
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.