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

Posted on 2013-03-15
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!
Question by:medium_grade
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 12

Expert Comment

by:Deepu Chowdary
ID: 38990859
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.
LVL 43

Expert Comment

ID: 38990981
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38996757
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.

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.


Author Comment

ID: 39001741
Installed Service Pack. No dice. Uninstalled Client Access Services. No dice. Anymore ideas?
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39009223
You are getting the identical error after the service pack installation? Highly unusual to survive a service pack installation.


Author Comment

ID: 39009380
Yes, same error after SP3 install. Any other ideas ?
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39009479
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.


Accepted Solution

medium_grade earned 0 total points
ID: 39013114
Got it. You're gonna love this:

If you'll notice, the error mentions "2013-03-12 21-00 Copy of Microsoft.Exchange.Clients.Owa" The first part is the key. When I started fishing around my Exchange program folder, I found many DLLs, config files and XSD files with duplicate copies that had this "2013-03-12 21-00 Copy of" string in the beginning. It looks as though one of the updates did not remove the older backup copies of the various Exchange files once it installed the new ones. Exchange, it seems, simply loads whatever libraries just happen to be in those folders and, if it detects a mismatch, errors out. I had to delete duplicate files from the following directories:

C:\Program Files\Exchange Server\V14\ClientAccess\Autodiscover\bin
C:\Program Files\Exchange Server\V14\ClientAccess\ecp\bin
C:\Program Files\Exchange Server\V14\ExchangeOAB\a986a330-9e79-4eef-bb89-11ab58573e49
C:\Program Files\Exchange Server\V14\ClientAccess\exchweb\ews\bin
C:\Program Files\Exchange Server\V14\ClientAccess\Owa\Bin
C:\Program Files\Exchange Server\V14\RemoteScripts
C:\Program Files\Exchange Server\V14\Scripts
C:\Program Files\Exchange Server\V14\ClientAccess\Sync\Bin
C:\Program Files\Exchange Server\V14\ClientAccess\Sync\Xsd
C:\Program Files\Exchange Server\V14\Bin

Once deleted, OWA, Autodiscover and ActiveSync worked perfectly. I really wanted to post this fix in the hopes that the next person who receives this error will find it.

Thank you all for your suggestions!

Author Closing Comment

ID: 39024267
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.

Featured Post

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
how to add IIS SMTP to handle application/Scanner relays into office 365.

687 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question