Exchange 2010 witness server crashed


the witness server in the exchange 2010 environment crashed and will not reboot. It has been down for over 3 days now. We will be rebuilding this server, but wanted to check if there is anything that would be affected when we bring it back online. the following application event gets logged on the mailbox/cas/hub server:
Event id 4065 : The Microsoft Exchange Replication service sent a request to the Hub Transport server sfhub01 to resubmit messages for database mailboxdatase between time periods 8/8/2014 and 8/9/201. Error 0x6ba (The RPC server is unavailable) from the SubmitDumpsterMessages.

Please can some tell me if this is serious and if I need to perform any kind of recovery once the witness server comes back online.

Thanks for your time and help.
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.

your DAG will work until any one DAG member server get down
Do not reboot the DAG member until you make provision of witness server
Better you could assign another server as DAG, there will not be impact
Note that Exchange Trusted Subsystem group must be part of local administrators group of witness server before you set it as Witness server

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
Simon Butler (Sembee)ConsultantCommented:
The error you have posted has nothing to do with it being a witness server. That is a transport error, so I presume it was also doing that role? As already pointed out, make another server the FSW, which will keep the DAG alive.
Then recover Exchange properly on the replacement server.

Antonio02Author Commented:
I ended up rebuilding the witness server. Seems like everything is working fine.
Appreciate your comments.

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
Email Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.