Exchange 2007 Stops send or recieving email

WE had a problem with our exchagne 2007 server this morning, The memory was running extreemly high and mail was just sitting in the queue. The event logs tell me

The execution time of agent 'ExclaimerRoutingAgent' exceeded 300000 (milliseconds) while handling event 'OnSubmittedMessage'. This is an unusual amount of time for an agent to process a single event. However, Transport will continue processing this message.

Process MSEXCHANGEADTOPOLOGY (PID=4272). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsGetSiteNameW Error code=800703e5. Make sure that Exchange server is correctly registered on the DNS server.

A reboot fixed the issue  -but as to what caused it and how to prevent it happening again
LVL 1
wanstorAsked:
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.

shadowlesssCommented:
Good practice is to reboot your Exchange server or any server for that matter every 30 days to clean up memory
0
techzterCommented:
Before you rebooted the server did you check all of the Exchange services to see if any of them had crashed, or was everything running with no issues?
0
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Did you verify that the Exchange services were running.
Also apart from SA and IS other service do depend on ADTOPOLOGY service and if the TOPOLOGY service is not runninga nd AD information cannot be verified then Exchange would be affected in a way.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Did the issue reaccour about the mailflow stopping ?
0
wanstorAuthor Commented:
Services were all running and could restart them ok, but restarting services such as transport, iis etc did not fix the problem, the reboot did fix the issue but i dont have an explanation for the boss man. It was using buckets of memory and although everything was working service wise mail was just sitting in the queue.
0
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Look if there is some problem in connectivity from exchange to AD or DNS and we get ADtopology errors we can just try rebooting  or if that does not help then check where the problem lies.
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
wanstorAuthor Commented:
yeah im leaning towards a DNS or AD contact problem. i did flush and re-register DNS and although windows was resolving DNS exchange could not. The server had been up without a reboot for a few months, so im guessing something got 'lost' at some point and never recovered correctly and the reboot just refreshed everything.
0
shadowlesssCommented:
and the reboot just refreshed everything.

As I mentioned above it is good practice to reboot your exchange server every 30 days to clear memory
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.