Known Exchange 2010 SP3 RU2 issues

11/25/13 Update: Exchange 2010 SP3 RU2 release:  (I will move my “Known Issues” list to this blog post once I have some to list)

8/13/13 Update: Exchange 2010 SP3 RU2 released: EHLO Blog Post | Download

7/12/13 Update: I’ve started a similar list for Exchange 2013 CU2 issues on this blog post:

5/30/13 Update: Exchange 2010 SP3 RU1 released: EHLO Blog Post | Download

This is not a full list of issues by any means, only those that I’m aware of and feel are important enough to share. In addition, I’m only listing issued that are new\only in Exchange 2010 SP3 and that there  is a Microsoft  KB or multiple community posts about it.

If you know of others please post them in the comments! I’ll update this post as I come across new info.

  • AllowCrossSiteRPCAccess reverts back to $False after running Set-DatabaseAvailabilityGroup
  • On-line Outlook or OWA users unable to soft delete some messages
    • Impact: Minor – Limited to Outlook in on-line mode or OWA with embedded WAV files, generated by Voice Mail, or PDF files, generated by scanners\copies.
      • Very few people have run into this issue and the only ones who have filed embedded in emails as a WAV or PDF. I have clients with Exchange UM and other solutions who haven’t seen this issue, so may just be limited to Cisco UM and Xerox scanners, where the problem has been seen.
    • Workarounds:
      • Do SHIFT-Delete, change to cache mode, call MS PSS for fix
      • Install SP3 RU1
    • More info:
  • When activating a database on another server it may cause the status to show failed on the original server
    • Impact: Unknown – I haven’t seen this issue or spoken to anyone who has
    • Workaround: Depends, but start by disabling 8DOT3 name creation: fsutil 8DOT3name set. See KB for more details
    • More info:
  • Messages get stuck in the poison queue and transport crashes
    • Note: This is an issue with Exchange 2010 SP3 RU1 only
    • Impact: HIGH <If you use a disclaimer transport rule>
      • The issue is caused by a transport rule (disclaimer) attempting to append the disclaimer to the end of HTML formatted messages.   When this occurs, messages will be placed in the poison queue and the transport service will crash with an exception.
    • Workarounds:
      • Disable the disclaimer transport rule
      • Install SP3 RU2
  • Some cmdlets fail in PowerShell ISE after an upgrade to Exchange Server 2010 SP3
    • Impact: Minor – Only an issue with PowerShell ISE – Added 7/17/13
      • This is really an issue with local PowerShell not working, while it may have worked in the past only remote PowerShell is supported and it seems changes in SP3 enforce this
      • See KB2859999 for more details
      • Exchange cmdlets fail in ISE after running “Add-PSSnapin”
        • Example: (Local PowerShell session being used)
          Add-PSSSnapin Microsoft.Exchange.Management.PowerShell.E2010 PS H:\> Test-WebServicesConnectivity -ClientAccessServer
          WARNING: An unexpected error has occurred and a Watson dump is being generated: Operation is not valid due to the current state of the object. Test-WebServicesConnectivity : Operation is not valid due to the current state of the object.
      • Workaround: Open a remote session to an Exchange server by using the following cmdlets at the beginning of the ISE script
        • Example:
          $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http:///PowerShell/ -Authentication Kerberos
          import-pssession $session
          test-webservicesconnectivity -clientaccessserver CASSERVER –trustanysslcertificate
  • On Windows 8.1 or 2012 R2 OWA comes up in Lite mode (9/19/13)
    • This is a known issue with IE11, which comes with Windows 8.1 and 2012 R2
      • Workaround: Use Firefox or Chrome
      • 2010 SP3 RU3 & 2013 CU3 should fix this issue

For general Exchange 2013 questions or to discuss non-support topics join the “Microsoft Exchange 2013” Facebook group I admin:

For community based support goto TechNet forums:

About jasonsherry

I am a 20 year Exchange consultant and expert. I currently work for Commvault as a Solutions Specialist for Microsoft Infrastructure For more info see my resume at:
This entry was posted in Exchange, Microsoft, Technical and tagged , . Bookmark the permalink.

30 Responses to Known Exchange 2010 SP3 RU2 issues

  1. Mike Cowan says:

    after updating exch 2010 to sp3 had issues with ms exchange rpc service unable to start 9starts and stops immediately) and outlook clients not showing new email…owa worked fine…tried registry fix for tcp/ip port and still no luck…made ure rpc locator service set to auto still no luck..,.when rebooted i stopped all exch srvcs and then started ms exch rpc svcs anit presto it started then started otherv services and all good…i see alot of people with this issue any fix??



  2. PL444 says:

    Hello all

    I am getting fed up with people trying to deny the deletion bug is a problem We have over 400 Xerox scanners that scan to PDF. Additonally, if you run in a Virtual Desktop evironment, like Citrix for example, running in Outlook in cached mode is not a viable option as it would at the very least double our space requirements. Additonally as we runEnterprise Vault and it deletes stubs over a year old daily, what happens f those stubs contain PDF files. 3 months plus now and no rollup 1 or not even an offically available fix for it.


    • jasonsherry says:

      Call Microsoft PSS support and reference KB2822208, there is a hotfix out for this issue for SP3 but is is not publicly available.

      This same issue exists in SP2 RU6 also, there is NOT a fix for SP2 RU6.

      I’ve only heard about this issue with Xerox scanners, or with Cisco UM, and you have a valid point with virtual desktops.

      As for stubbing, I and everyone else I know in the Exchange community strongly recommends against it. I don’t know if this bug would affect EV, but if it’s stubbing the e-mails the attachment and message type should already be removed and changed.


      • PL444 says:

        Thanks for your reply. I am aware of the KB282298 hotfix. However, the fact it is not publicly available suggests it is not fully regression tested. So I am left asking, given the long list of problems with many of the update rollups, do I want to deploy a one off hotfix that is not even fully tested? I am getting the distinct impression MS have given up on 2010 now 2013 is RTM. We regularly get updates every 6- 8 weeks for 2010 until 2013 is RTM and have now not had anything for 12 weeks and counting. Don’t even start me on the fact that it could be argued and has been by some people. that 2013 is not even feature complete, let alone anything else.

        Do not stub messages? That is the whole point of EV or is it being suggested we archive the messages but leave no pointer in the mailbox at all, so our users will see nothing and have to go and search for every single archived messages they want to access? This is not a viable proposition for us I’m afraid. Perhaps I did not ask this part correctly. I agree old messages that have already been archived will probably be fine. The correct question perhaps is when a message has been placed in to EV will the messages get dleted and replaced with a stub if it contains a PDF attahcment from one our 400 Serox scanners?


      • jasonsherry says:

        Have no doubt that Microsoft is only focusing on Exchange 2013 now, and E16. I’m 99% sure there won’t be a SP4 for 2010 and probably only one more RU for it I guess.

        Here are some key reasons why stubbing shouldn’t be used (words taken from an e-mail thread I participated on recently)

        Cost – how much will it cost to run one solution over another. Exchange wins big because of its integrated functionality, loses because of the need to deploy the latest versions (including clients). But overall, a positive point for Exchange, if only because it is much easier to deploy and support the single integrated solution rather than different software from different vendors.

        Exchange Native Data Protection – If you stub data you can no longer rely on native data protection; retention, legal hold, and Dumpster 2.0

        Distributed Database Availability Groups – If a DAG spans multiple locations and a failover occurs, users will not be able to access archived content unless the stubbing solution has its own replication engine to replicate stubbed data to multiple sites.

        Articles on stubbing:
        From 2008: See “Eliminated third-party archiving stub files”

        With 2010 you could be using 3TB SATA JBOD drives, so storage cost really shouldn’t be a factor anymore. I know this is a hard sell to management and I’ve yet to use JBOD for Exchange 2010, but 2TB+ SATA\SAS drives in a SAN is fine also.

        So large\slow disk support with archive mailboxes should replace the need for stubbing.


      • Ron says:

        Hi All,
        Does anyone know whether or not the deletion bug and fix applies to both virtual and non-virtual environments?


      • jasonsherry says:

        Physical or virtual doesn’t matter to most software, so it’s fixed in both. 9/10 Exchange 2010 installs I’ve done in the last three years have been on VMs.


  3. Pingback: #MSExchange 2010 SP3 RU1 is out | Jason (Izzy) Sherry's Blog

  4. PL444 says:

    Thanks for the update.

    So the best answer MS have for custoners who are using Symantec Enterprise Vault is too effectevly turn it off to fix a problem their poor coding created. Need i say more?!


    • jasonsherry says:

      If you are talking about stubbing, then the recommendation for years has been to not stub. This has nothing to do with Exchange code, it’s mainly due to the fact that stubbing doesn’t not add much value and adds to much complexity. I’ve been telling customers this since Exchange 2007 came out, which was the first version of Exchange that really didn’t need high I/O drives and high capacity drives were a valid option.

      Stubbing saves disk space (in most cases), but Exchange 2010+ supports 2TB DBs, 2013 supports multiple DBs, running on SATA drives, so disk space is cheap. I know many organizations have invested in SANs, but I strongly recommend against using high end (15K SAS drives) for Exchange, it’s a huge waste of money. Using a SAN is fine, but trays of high capacity drives should be used for Exchange 2010+. In some designs we will use a SAN for the primary servers, but DAS for a DR server that will fully support the same mailbox load.


  5. Devon says:

    RU1 appears to have a bug that breaks online archive names. we have seen the issue in outlook 2010/2013, when a user has multiple archives open, such as a delegates archive. All archives now show the name of the primary mailbox owner. the content is correct inside the archives, it just makes it difficult to determine who’s archive is who’s.


    • jasonsherry says:

      Hadn’t heard of this issue yet. Thanks for sharing!

      Have you opened a ticket with PSS yet? If so, or when you do, update us here. Thanks


      • Devon says:

        Yes we did open a ticket. They confirmed it was a bug aftewr testing and said they would “pass it on”. have not heard anything since so no clue if it will actually be fixed or not.


  6. DiPersiaTech says:

    Found a bug that is rumored to be resolved in 2010 SP3 RU2 where emails are getting stuck in the queue due to rich text/html.


  7. Peter says:

    I upgraded 50 servers to Exch 2010 SP3 RU2 and most of them had issues the next day with constant queues in “Mail submission Queues Threshold exceeded”. These are MAILBOXD ROLE servers only with the issue. Before SP3 RU2, we never had any issues- Exch 2010 was stable. troubles hooted for hours and cannot find any solution. Seems inherent to SP3 code.


    • jasonsherry says:

      You’ve upgraded more 2010 servers to RU2 then I have, but I haven’t seen this issue on the dozen or so servers I’ve upgraded so far. Have you checked TechNet forums?


  8. draulbe says:

    We just upgraded about 20 MBX servers to SP3 RU2. We are seeing “Mail submission queues treshold exceeded” on at least one database.
    We are also seeing the test “ServicelocatorService”, part of the Test-ReplicationHealth, fail on the DAG members that weren’t patched yet.


  9. jasonsherry says:

    Sound’s like a possible backpressure issues, But could be many other things and this isn’t something common to upgrading to SP3 RU2 that I’ve seen or heard of.

    So I would recommend posting your issues on the TechNet forums:


  10. Nick says:

    Great Exchange supports huge databases, how do you back them up? You still need to pay for the cost of backup storage and using slow disks for backup means you do not complete your backups in 24 hours


    • jasonsherry says:

      You don’t back them up. You replicate them to other servers, including ones at other sites. Then you use storage that supports hardware bases snapshots or software bases ones for point-in-time recovery if ever needed.


      • PL444 says:

        Really? What happens if a user requests an email they deleted a year ago for a pending legal case, that was only in their mailbox for a few weeks and is now gone from deleted item retention?


      • jasonsherry says:

        Backups are NOT an archiving solution. If the company policy is that deleted items are only saved for 90 days then that will hold up in court, and has for many years for a major airline and other orgs I’ve worked with.

        If regulatory requirements require data to be saved you need to have a real archiving solution.


      • PL444 says:

        Agreed but take our organisation as an example and we are not unique by any means. We only archive messages after 30 days as many, if not most, mesages in that period are not required to be kept, so there is no point in archiving them. For compliance reasons nothing is deleted thereafter. It would substantially increase our storage requirements for little real advantage. Granted occasionally we will get caught out and hence the need for the backups. We then have daily, weekly, monthly and yearly backups in additon. I see and agree with your point in principle but archiving absolutely everything is just not practical for us.

        Compliance is a double edge sword and the real issue with it is how to catergorize the data so as to know what should be done with it once archived. For example, some data must be kept forever, some must be kept for 7 years and some must be deleted as soon as it is no longer required.


      • jasonsherry says:

        Categorization of data by users is an impossible task. I worked with an e-mail archiving vendor for two years and have heard many different needs. But depending upon the users to put stuff in the right buckets will always fail. With Exchange 2013 you have more powerful transport rules and In-Place Hold support you can auto categorize items for long term retention. Then with archiving policies that older data can be moved to the personal archive mailbox of a user, which can be stored on different storage than the primary mailboxes, or in the cloud.

        Most companies I worked with several years ago archived everything to be safe.

        The other risk you have, is if you have made it a standard practice to recover data from tapes for user or legal request then ANY of your backups can be requested in court. This can cost the company LOTS of $$$ in time if the other legal team request lots of backup data to be recovered. In addition, the recovery process from tapes has a high chance of failure, 42% or higher depending upon the statistics source.

        Disk storage is also getting cheaper and cheaper, 8TB drives should be out next year! The bigger issue is now search ability and recoverability, which Exchange 2010 and 2013 are pretty good at but the big 3rd party archiving solutions may provide a better interface for regulatory and legal compliance staff. Exchange & SharePoint 2013 together now offer some of the key features that 3rd party solutions used to only provide; like case management, Boolean search logic w/ proximity support, shared search results, results tagging, and searching across Exchange, SharePoint, Lync, and file shares from a single console.
        See this page for more info on new eDiscovery feature in 2013


  11. Larry says:

    Hi Jason

    Nice blog.
    I came across this while searching for a solution to the problem I currently face.
    I’m supporting a charitable organisation who have Server 2012 with Exchange 2010.
    For a few months, they have had various emails not delivered (in and out) without notification at all.
    The only way they’ve been finding out, is through telephone calls.
    Anyway, it turns out that they think it’s limited to sending or replying using html.
    Although some html mails get through.

    You mentioned that we should search the forums for answers, but having done that for a few weeks without finding a solution, what should I actually be searching for?

    Thanks in advance


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s