Updates broke my OWA

After applying the latest round of updates, with the exception of one (IE 10 Update) none of my mobile devices or my OWA page is working. It's as if all the web services have been turned off. However, everything else is working.

I've check both internal and external urls and the error message is the same "Web page not available. Error 103 (net::ERR_CONNECTION_ABORTED): Unknown error."

Any ideas would be greatly appreciated
Wizard_of_Heath_MountAsked:
Who is Participating?
 
Wizard_of_Heath_MountAuthor Commented:
Hi Guys
After checking all the updates, rollups and even running the scripts nothing seemed to work. Until I decided to go back to basics and started to strip all the additional software off the server (monitoring agents, AV, etc.). Turns out the culprit was my anti-virus. I was running kaspersky, but after trawling there user forums I read that it breaks exchange 2010, even running the version that they tell you to use had no joy. As a result it was all un-installed across the site and I'm now using Sophos.
0
 
R--RCommented:
did you checked the iis, www services are running.
All exchange services are running?
0
 
Wizard_of_Heath_MountAuthor Commented:
All services are running for exchange, www and IIS.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Pradeep DubeyConsultantCommented:
Can you check and list the updates you just installed?

One of them is making this issue, try to findout and uninstall that update. Everything will be good after that.

Check updates detail and findout related one (related to IIS and exchange)
0
 
Wizard_of_Heath_MountAuthor Commented:
Thanks for that, I will check and reboot the servers if required tonight and let you know tomorrow morning.
0
 
Ben HartCommented:
Which Exchange specific updates were installed?  You can view that by checking the Updates History on the Windows Update page.

Rollup6 for SP2 broke my web services.. but the fix was as easy as running the updatecas.ps1 script in your exchange server working directory.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Try running the UpdateCAS.PS1 on the CAS server and then check

- Rancy
0
 
Wizard_of_Heath_MountAuthor Commented:
The reason for accepting my own solution is in the answer its self
0
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.

All Courses

From novice to tech pro — start learning today.