Exchange 2013 OWA wont load and Outlook clients wont connect

We have a single exchange server running exchange 2013.
Clients are running outlook 2013.
This morning clients cannot connect - all client outlooks show disconnected.
OWA is not working - shows:
:-( something went wrong

ecp is working without issue.
Have rebooted server, checked authentication method is correct in OWA frontend and backend, and also uninstalled this update from last night: KB2992611

I have checked outlook connectivity status on client, and it is empty - even after clicking reconnect, nothing happens.
Any ideas?
davids355Asked:
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.

it_saigeDeveloperCommented:
What do your event logs show?

-saige-
0
VB ITSSpecialist ConsultantCommented:
Yep logs would be the first place I'd look. Also check that all the relevant Exchange services are started and running.
0
davids355Author Commented:
FYI I have actually opened a support incident now with microsoft - just because I have seen some indication that it may have been a recent update that has broken exchange/IIS.
Ill post results here anyway if thats ok?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

VB ITSSpecialist ConsultantCommented:
Yep, let us know the outcome either way. Would be good to know when a particular KB breaks Exchange.
0
davids355Author Commented:
Hi guys,
Microsoft helped to resolve the issue, but I don't have confirmation as to whether the update had any relationship to the issue - as it turned out, the database was continuously dismounting (Something I somehow missed), and was corrupt beyond repair - we tried hard repair and defrag with Microsoft but still the database had the same issue, whilst a new "test" database did not.

In the end we restored the entire database from the previous evenings backup and now everything is working as expected.

Thanks guys.
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
davids355Author Commented:
After posting the question I also contacted Microsoft support, and they ended up fixing 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.