EdgeTransport.exe process appears to be leaking memory - high object handles

We are seeing an issue with an SBS 2011 whereby every week, pretty much to the hour, Exchange is unable to communicate with Active Directory.

We see event logs which suggest that Exchange is unable to find any global catalogs (there are 2) within the domain.

This has been researched extensively by ourselves and Microsoft - but we aren't really getting anywhere.

Earlier this week a discovery was made that, whereby restarting the EdgeTransport.exe service appeared to restore connectivity and solve the issues.


We've noticed that there were a few processes running with high object handles. One of which was uninstalled (Sage Gateway) and another disabled (A300_Service) but this made no difference. The next object with the highest handles is EdgeTransport.exe.

taskhandlesedge.JPG
The server and exchange is fully service packed.

Any ideas or suggestions please?
utilizeAsked:
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.

Simon Butler (Sembee)ConsultantCommented:
What else is on the server?
Any Exchange integrated AV or Anti-Spam tools?

Simon.
0
utilizeAuthor Commented:
Other software potentially responsible includes:

Sophos (this has been disabled, issue still occurs)
Exclaimer Mail Disclaimers
C2C Mail Archiving

Anti-Spam is cloud based
0
Simon Butler (Sembee)ConsultantCommented:
Disabling the products isn't enough. That is like putting a blindfold over them. You have to actually remove the product and reboot to verify it is not the cause.

It is transport related, so Exclaimer or Sophos would be the places I would look.
In a lot of cases, simply removing the product, rebooting and then reinstalling the latest build resolves the issue.

In these kinds of cases I rarely look past third party software as the cause, and I usually don't have to.

Simon.
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
utilizeAuthor Commented:
Thanks Simon - going through those steps now. (The only problem is that it can take a week to really know if a remedial task has fixed the issue)
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
Exchange

From novice to tech pro — start learning today.