We help IT Professionals succeed at work.

Problems with OWA and ActiveSync after Update Rollups on Exchange 2010 SP1

2,963 Views
Last Modified: 2013-03-27
So, my Windows Update applied Update Rollups 7-v2 and 8 for Exchange 2010 SP1 and now both OWA and ActiveSync are no longer working. The error I receive when I try to go to OWA is this:

Could not load file or assembly '2013-03-12 21-00 Copy of Microsoft.Exchange.Clients.Owa' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I have tried removing the updates, re-applying them as well as resetting and re-configuring the virtual directories all to no avail. Short of restoring the system to a point before the update, can anyone make another suggestion?

Let me know. Thanks!
Comment
Watch Question

CERTIFIED EXPERT

Commented:
New Updates ruined some files..

Restoring from backup is the only option left.. as u have already resetted VD's & all other possible ways.

I have seen in some articles that we have to re-install CAS role from Command prompt.

Check the similar issue happened on 2007 server.

But restoring from backup would be ideal way.
AmitIT Architect
CERTIFIED EXPERT
Distinguished Expert 2017

Commented:
CERTIFIED EXPERT
Most Valuable Expert 2014

Commented:
I would skip SP2 and go straight to Exchange 2010 SP3. SP1 is very old. Even rollup 3 has suggested above is old.

The Exchange service packs effectively reinstall the entire product and will resolve a lot of issues.

Simon.

Author

Commented:
Installed Service Pack. No dice. Uninstalled Client Access Services. No dice. Anymore ideas?
CERTIFIED EXPERT
Most Valuable Expert 2014

Commented:
You are getting the identical error after the service pack installation? Highly unusual to survive a service pack installation.

Simon.

Author

Commented:
Yes, same error after SP3 install. Any other ideas ?
CERTIFIED EXPERT
Most Valuable Expert 2014

Commented:
My instinct is that something else must have installed at the same time, or around the same time as the updates that you installed for Exchange. That has broken things. .netframework would be my guess. I am finding nothing specifically related to Exchange, it is all developer related, which points to something else. As I wrote above, highly unusual for errors to survive a reinstall, which points to something outside of Exchange as the cause.

Simon.
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
The issue was one that I was able to fix on my own. None of the other answers given seemed to relate to the fix directly.

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.