MSExchange Transport Error Event ID: 5006

I am getting an Application error
Source:  MSExchange Trasport
Event ID:  5006
Level:  Warning
That indicates the Exchange Server is looking for an 'old' nonexistent exchange server (server is still in use but not as exchange server).
Cannot find router to Mailbox Server CN=WrongServerName, CN-Servers,CN-first administrative group,CN=Administrative Groups,CN=CorrectDomainName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=CorrectDomain,DC=local for store CN=Public Folder Store (WrongServerName),CN=First Storage Group,CN=InformationStore,CN=WrongServerName,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=CorrectDomainName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=CorrectDomainName,DC=local in routing tables with timestamp 9/5/2013 5:14:02 PM. Recipients will not be routed to this store.
Then had MSExchange ActiveSync Event ID:  1033 stating:
The setting ExternalProxy in the Web.Config file was not valid. The previous value was null and has been changed to .
and:  A process serving application pool 'MSExchangeOWAAppPool' exceeded time limits during shut down. The process id was '8296'.

Everyone's email stopped working and Found the Exchange System Attendant services had stopped.
Started the service and restarted Outlook
What would cause this?
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.

with regard to the wrong server issue, it looks like a previous migration fro an old email server may not have been completed.

This is a good guide to removing old servers

make sure you have backups before attempting as ADSI edit is a dangerous tool in the wrong hands :-)

as for the other stuff, you don't mention any details on what version of exchange or server you are using so it's a bit vague.

The best place to start is finding out which process caused it to stop.

The process id was '8296'.

if it occurs again check the process id to see what was responsible for the shutdown request.

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
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
Server Software

From novice to tech pro — start learning today.