Exchange 2010 SP3 Update Rollup 8 - Outlook NDR Errors


Yesterday started to notice issues with one or two Outlook 2013 clients where when users try to send emails to any address, whether internal or external, a NDR would immediately come back:

Your message did not reach some or all of the intended recipients.

  Subject:  Earlier letter
  Sent: 10/12/2014 08:03

The following recipient(s) cannot be reached:

  'Joe Bloggs' on 10/12/2014 08:03
        This message could not be sent. Try sending the message again later, or contact your network administrator.  Error is [0x80004005-00000000-00000000].

But when using the user's OWA they could send emails fine. After trawling the internet and getting nowhere I looked at the servers event logs which didn't show anything. It was only when I noticed that Exchange SP3 Update Rollup 8 had automatically been installed on the Exchange Server on the morning of the first instance that I started to wonder.

After uninstalling the rollup package the issue has gone away. Just wanted to see if anyone else had experienced this issue with this update package?

asked on Server Fault Dec 11, 2014 by Jay1980

3 Answers


In WindowsITPro blog they say that this update created a problem with the MAPI RPC component.
Other mail services (OWA, ActiveSync, etc.) should work properly, because they don't use the faulty component.

The update has been removed from "Microsoft updates".

As they strongly suggest, you better test all updates before applying them to avoid such situations.
Alternatively, if you don't have any special systems, you could just wait for someone else to be the Guinea pig.

answered on Server Fault Dec 11, 2014 by EliadTech

Removing Exchange 2010 SP3 Rollup 8 worked for me. Strangely only Outlook 2013 running on Windows 7 (32-bits) had problems with sending mails out. Outlook 2013 on Windows 8.1 (64-bits) was running fine. With Rollup 8 removed all Outlook clients are running normally again.

answered on Server Fault Dec 16, 2014 by Remco

This appears to be an issue with this month's (December 2014) "Update Rollup 8" Exchange 2010 SP3 update.

KB2986475 "Update Rollup 8-v2 For Exchange Server 2010 Service Pack 3" was recently posted to Microsoft Update. Rolling in this update appears to have resolved the issue.

answered on Server Fault Dec 17, 2014 by Dan N

User contributions licensed under CC BY-SA 3.0