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
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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
techzter
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?
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.
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.
Did the issue reaccour about the mailflow stopping ?
ASKER
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.