Released: Update Rollup 6 for Exchange Server 2010 SP1


Earlier today the Exchange CXP team released Update Rollup 6 for Exchange Server 2010 SP1 to the Download Center.

This update contains a number of customer-reported and internally found issues since the release of SP1. See ‘KB 2608646: Description of Update Rollup 6 for Exchange Server 2010 Service Pack 1’ for more details.

This update contains a number of customer reported and internally found issues since the release of RU5. In particular we would like to specifically call out the following fixes which are included in this release:

  • 2627769  Some time zones in OWA are not synchronized with Windows in an Exchange Server 2010 environment
  • 2528854  The Microsoft Exchange Mailbox Replication service crashes on a computer that has Exchange Server 2010 SP1 installed
  • 2544246 You receive a NRN of a meeting request 120 days later after the recipient accepted the request in an Exchange Server 2010 SP1 environment
  • 2616127  "0x80041606" error code when you use Outlook in online mode to search for a keyword against a mailbox in an Exchange Server 2010 environment.
  • 2549183  "There are no objects to select" message when you try to use the EMC to specify a server to connect to in an Exchange Server 2010 SP1 environment

 

Availability of this update on Microsoft Update is planned for late November.

General Notes

An issue with management of RBAC roles when RU6 is partially deployed in the organization: Due to changes shipped in this update, certain warnings can be displayed when managing RBAC roles, if RU6 is not yet deployed to all servers in the organization. Please see the following KB article for more information:

Managing RBAC roles might display warnings or errors if Exchange 2010 SP1 RU6 is partially deployed in the organization
http://support.microsoft.com/kb/2638351

Note for Forefront users: For those of you running Forefront Protection for Exchange, before installing the update, stop all Forefront services.

Ron Ragsdale

Comments (61)
  1. HotFix says:

    This is great to see – hopefully this is the precursor to SP2 being announced.

  2. Simon says:

    Note to all Forefront users: We still don't care enough about you to make a small change to the setup script.

    Will this be done automatically when updating via WU?

  3. Anonymous says:

    You mean Forefront Protection for Exchange, not Forefront Security for Exchange.  And don't you meant to do fscutility /disable?  blogs.technet.com/…/sample-script-to-disable-and-enable-forefront-service-during-exchange-patching.aspx

    Seriously guys, add this step to the Exchange RU Update process already.  It's getting annoying…

  4. Nino Bilic says:

    @Simon: in reality, when Exchange services are stopped, Forefront services should stop automatically; but as we cannot guaratee this, we suggest you stop the services manually

    @Anonymous: Thanks for the naming catch; fixed that in the post. Also – with current versions of Forefront, running fcsutil is not required; we have confirmed this with Forefront team. While this was needed for older versions, it is not needed anymore.

  5. Karsten says:

    If I follow the link "Update Rollup 6 for Exchange Server 2010 SP1" I get to the website for that Rollup but under "Overview" is a link pointing to changes of RU5 instead RU6.

    For a list of changes that are included in this update rollup, see KB2582113.

  6. Karsten says:

    I Installed the RU6 in my testenvironment – the error concerning the udp protokoll described in KB2579172 does still exist.

  7. Jerry from Australia says:

    I hope proper testing and QA has been done by Microsoft.  Nothing like the last couple of disasterous buggy releases to make you think twice (thrice) before taking the plunge

  8. wasim_sha@hotmail.com says:

    This is great to see

  9. deiruch says:

    @Nino Bilic: Thanks for the reply. Why can't *you* stop the services in the setup script? What about installing it via WU?

  10. Peter Daalmans says:

    Nice!

  11. HDPsupport says:

    I've got hte same problem like Karsten. The problem disicribed in KB2579172 still exists. Are there any special configs or reg keys to be done? We are about to migrate a system where these faults are a showstopper. Other customers will follow.

  12. Nino Bilic says:

    @HDPsupport and Karsten: After looking into this, it turns out that this fix being listed on the KB article was the error. The fix for this particular problem did not make it into shipped version of SP1 RU6. We are going to remove it from the list of fixes in the release KB article. Sorry for the confusion on this.

  13. HDPsupport says:

    @Nino: Öhm, is that trick or treat? Is there any other possibility to get the hotfix (e.g. support call)?

  14. sejong says:

    Has anyone who had the OWA search problems associated with Events 9877 and 9842 even after installing RU5, found that installing RU6 fixed them?

  15. grmpy says:

    If I had to call out noteable fixes in this release,  I would say support.microsoft.com/…/2449266 is the winner.  Microsoft has been in denial about this issue for a long time.  It's great to see it finally included in a supported rollup.  

  16. Nino Bilic says:

    @HDPsupport: If this was ready – we would have released it with RU6. Alas, not just yet.

  17. Andy says:

    same here, UDP problem still persists after RU6 and registry change.

  18. unaischr@hotmail.com says:

    " Microsoft Exchange Mailbox Replication service crashes  " not solved on Roll UP 6 .. getting error and not able to export mail box to PST

    Event ID :4999 Exchange connection

    "Watson report about to be sent for process id: 9788, with parameters: E12, c-RTL-AMD64, 14.01.0355.001, MSExchangeMailboxReplication, M.Exchange.PST, M.E.P.C.BTreeNode`2.FindLeafEntry, System.NullReferenceException, 1a78, 14.01.0346.000.

    ErrorReportingEnabled: False "

  19. Nino Bilic says:

    @Unais: Call into Exchange support, please… it seems like you are dealing with a bug (a crash = bug :) – and MS does not charge for support cases that are open because of bugs.

    One thing though: do make sure that you are on latest SP / RU combo.

  20. John says:

    Seriously, still no fix for KB2579172.  We ahve one legacy app that only uses Outlook 2003 and cannot handle the delay issue.  So I have to keep a entire Exhange 2007 environement in place, with redundancy, for one single mailbox.  What about the issue that was still in RU5 where moving folders would cause the items to go to Recovery Items, is that fixed in RU6?

  21. Zachary Alex Stern says:

    Is Outlook 2011 for Mac and the random missing emails/super long time delays issue fixed yet? This is a widely reported issue, yet the only way to get the "interim" fix is to open and pay for a support case from Microsoft, and then receive the patch.

    How can Outlook 2011 for Mac, a Microsoft product, not be fully compatible with Exchange 2010? Insanity!

  22. Amir Haque [MSFT] says:

    Zachary Alex Stern,

    I assume you're pointing to this issue in forums: social.technet.microsoft.com/…/352776de-ab8a-400f-9f09-fb13cfa89f52

    As I mentioned in the forun post, this issue has been fixed in RU6, see KB: support.microsoft.com/…/2449266 for details. The description in KB differs from what you've written below which matches with the description in forum post, but it’s the same issue.

  23. a_castoldi@hotmail.com says:

    Hi there. Yesterday we installed the RU6. About problem KB 2544246, should these NRNs stop immediately or in 120 days? In other words, do we have to expect that we still receive the NRNs for the metting requests we sent until yesterday?

    I ask this because after installing RU6, I already received another NRN…

  24. Vladimir says:

    Hello,All

    After you install rollup 6 time zone has not changed in OWA to Russia, Moscow remained the +3, but should be!+ 4 … How to Be?

  25. Nino Bilic says:

    @a-c: Actually, NRNs will be completely flushed only 120 days after the hotfix installation; the fix prevents this problem from happening but items that were already created are not cleaned up by it. It would require some sort of manual per-mailbox process that is risky due to possible data loss. I have requested that an edit be made to the KB to call this put.

  26. unaischr@hotmail.com says:

    @Nino Bilic

    Thanks for info,

    My server is up to date with sp and Rooll Up( Exchange 2010 SP1 with Rollup 6).

    Any Exchange Support Team Mail Id to contact for Support ?

    Thanks

    UNAIS

  27. Sven J says:

    Installed into production.

    So far, so good.

  28. Alternate says:

    Gents,

    Is it fixed issue with Address Book rules in Outlook ?

    Address book rules doesn't work in SP1 RU5/RU4.

  29. eddie.ringrose@voyager.net.uk says:

    Is the fix for the folder copy and move issue in Outlook that was introduced in RU4 (KB2581545) included ?

    The RU 4 interrim hotfix was 492920.

    I can see no reference to it so assume not.

  30. The_Prisoner says:

    Just found this:  briansibley.wordpress.com/…/using-outlook-2003-with-exchange-2010

    "Now, according to support.microsoft.com/…/2009942 this has been resolved by Update Rollup 3 for Exchange Server 2010 Service Pack 1 and a simple Registry entry modification on the Client Access Server. This is not the case, the problem is reduced but not resolved.

    Further investigation uncovers an Interim Update relating to KB2579172, which can be made available if you call Microsoft Support (although they might deny it!), this appears to fix the issue and was due to be included in Update Rollup 6 for Exchange Server 2010 Service Pack 1.

    A contact I have inside Microsoft has informed me that this IU has now been dropped from UR6 due to issues with the RPC Client Access service crashing, and will probably now come in SP2 Rollup 1…..Watch this space."

  31. JamesKenobi says:

    Hey! This was missed on Twitter!  As a mater of fact no posts made to Twitter for 21 days?!  What's Up?

  32. See a case that occurred on TechNet Brazil, after removing the Rollup 5 OWA is working again.

    social.technet.microsoft.com/…/f401f5da-7b41-4a4d-9248-d01ad055ecd2

  33. Shelley Miller says:

    I just installed my first CAS server and am attempting to install this rollup.  I get an error message stating "setup had ended prematurely because of an error.  Your system has not been modified."  This is a fresh install of Exchange Server 2010 SP1.

  34. ktolik@gmail.com says:

    Make sure you run the update from Administrator command prompt…

  35. Braajun says:

    About update-issue between Outlook 2003 & Exchange 2010: this is NOT fixed by Update Rollup 3 & still NOT fixed by Update Rollup 6!

    Since this is a big issue for our migration (we use Outlook in Online-mode because we are using Citrix): I made a case bij Microsoft requesting the intirim update for KB2579172. It took me a little bit of persuading, but I finally got ExchangeServer2010.508887.SP1_RU5_HOT.ZIP which contains intirim updates for KB2579172, KB2543850 & KB2492066. I installed this fix on our 2 CASHUB-servers and it really looks that this issue is now SOLVED!!!! Finally….

  36. HDPsupport says:

    @Brajuun: Thanks for sharing your information. Did you made tests regarding stability? Clive wrote in an earlier post that there could be crashes with the RPC Client Access service. Did MS charge for the call?

  37. JFL says:

    RU6 Installtion fails. Where are the log files located?

    Thanks!

  38. The_Prisoner says:

    @Braajun.  Can you post CAS service stability issues, if any since applying the hotfix.  It has been posted by Brian Sibley in another blog that this was pulled from RU6 and TechNet because of causing the RPC Client Access service to crash.

    If you are finding it stable, can you post what you had to do to get MS to give you the update.  Or if not an issue with MS, post a link to it.

    Thanks

  39. Nino Bilic says:

    @Braajun (and everyone else looking for the hotfix for email notifications):

    The Exchange team understands the importance of delivering a solution to address
    the Outlook UDP notification problem customers are experiencing in
    Exchange 2010 SP1.  Providing a high quality and final fix for this has
    been a team priority for quite some time now.  This issue is resolved to
    our satisfaction in internal builds of SP2.  We have stopped providing
    Interim Updates for SP1 installations and customers should plan to
    deploy SP2 to resolve this issue when it is released.

  40. Karsten says:

    @nino – thanks for that info.

    I think there is a minor bug in the SP1 RU6: When I go to the Tools Section and start the messagequeviewer I get for example 18 queus. After sorting for example for Messagenumber in the queues there remain only 6 queues in the window (although the count displayed on bottom line still says 18).

  41. Carsten_Due says:

    I am trying this again this time with a question if some of these issues are corrected in UR6? We are still on UR5.

    On CAS Servers (4) in a CAS Array, the following issues are seen, repeatedly:

    -Watson report about to be sent for process id: 8432, with parameters: E12, c-RTL-AMD64, 14.01.0325.000, OWA, unknown, unknown, System.InvalidOperationException, 0, unknown.

    -Watson report about to be sent for process id: 24904, with parameters: E12, c-RTL-AMD64, 14.01.0335.000, edgetransport, M.E.Data.Storage, M.E.D.S.InboundMimeConverter.MergeCIDReference, System.InvalidCastException, 4d70, 14.01.0339.001.

    -Watson report about to be sent for process id: 7656, with parameters: E12, c-RTL-AMD64, 14.01.0325.000, OWA, M.E.Clients.Owa, M.E.C.O.C.Utilities.ReconnectStoreSession, System.ArgumentNullException, 1daa, 14.01.0339.001.

    -Watson report about to be sent for process id: 8120, with parameters: E12, c-RTL-AMD64, 14.01.0325.000, AirSync, mscorlib, S.S.P.Win32.ImpersonateLoggedOnUser, System.ObjectDisposedException, c1ae, 02.00.50727.5446.

    -Watson report about to be sent for process id: 2236, with parameters: E12, c-RTL-AMD64, 14.01.0325.000, WS, M.Exchange.StoreProvider, M.M.MapiMessage.CreateAttach, M.E.D.Storage.AccessDeniedException-27121, ffcb-5111, 14.01.0323.000.

    On MBX Servers we only see this one (Expected in UR5):

    -Watson report about to be sent for process id: 288684, with parameters: E12, c-RTL-AMD64, 14.01.0339.001, msexchangerepl, unknown, unknown, M.E.C.Replay.ReplaySeriveTooMuchMemoryException, 0, unknown.

    The only reason we have not yet called PSS is that all of these issues so far are not seen by end users.

  42. HotFix says:

    @Nino – Ok… if you won't give out the IU to fix the Outlook 2003 issue then can we please have SP2 now? Or are we to wait until the estimated ~3+ weeks that was announced at Exchange Connections?

  43. Rollup or Back?! says:

    @Carsten_66 are there any developments on that error you are seeing?  Are your users experiencing any impact as of yet?  I'm interested in finding out what that error indicates.  Have you ran a procdump on it yet?  Thanks

  44. matt34@gmail.com says:

    Has anyone experienced any issues with this UR 6 release?  I am only seeing some positives and very few reviews on the Internet.  We are looking to implement this week.

  45. Zachary Alex Stern says:

    No mention of the EWS fix as important? That's HUGE for Outlook for Mac users. It was unusable before!

    Thanks guys!

  46. daliu says:

    @Zachary Alex Stern, whch EWS problem are you referring to, do you mean OL 2011 users not able to receive emails/msgstore process hung?

  47. hwc says:

    To MSFT or Nino Bilic, any idea when SP2 will be available?  need the UDP fix asap.

  48. Braajun says:

    @Nino: great to hear that the final fix will be in SP2. When will it be out?

    @Clive: we have experienced NO issues with RPC CAS service. Everything seems stable and the issue is really solved! To get the interim update, I opened a case with Microsoft Support. We have a Software Assurance-contract, so we can open 7 cases a year for free……I hade to convince the support-guy to let him ask the PRO-department, but finally got the fix….

  49. RMB says:

    On our Exchange server the MTA started crashing after applying RU6.

    We have uninstalled RU6 to get the MTA running again.

    After uninstalling RU6 my OWA-options pane is broke, so users cannot access the options anymore…

  50. rlawsha@galesburg205.org says:

    RU6 fixed my OWA search problem!

    In RU5 if you tried to do a search form OWA it would fail and no amount of tweaking would fix it. I deleted the search index, restarted the indexer and tried all the usual fixes to no avail.

  51. John says:

    @RMB

    do you have anything special isntalled, never read this problem before?

  52. Public Folders says:

    @EddieR

    I haven't seen any mention of the fix for the folder copy and move issue in Outlook that was introduced in RU4.

    Can anyone confirm?

    Reference KB2581545.  The RU 4 interrim hotfix was 492920.

  53. rlawsha@galesburg205.org says:

    John,

    If you are referring to my post about the search problem…

    I don't have anything special installed that I can think of. Server is running under VMware, has all roles, 900 mailboxes, Trend Micro Scan Mail for Exchange and that is about it.

  54. RMB says:

    @John

    This server is a standard Win2008R2 x64 server with only Exchange installed, nothing else…

    I have uninstalled the RU6 and I will wait for SP2…

  55. Ole Drews Jensen says:

    Thanks for the info.

    Any news about a fix for not being able to shut EMC down except ending the MMC task?

    Thanks.

  56. Ole Drews Jensen says:

    Also, I'd like to see a change in Outlook Anywhere so OOF doesn't rely on AutoDiscover. Since Outlook can be setup with Manual Settings (not using AutoDiscover), it doesn't make sense that OOF can't utilize the same setting.

    Thanks.

  57. anthonynz2000@hotmail.com says:

    What happened to Exchange 2010 SP2?  

    2nd Half of 2011?  Did you mean 2nd half of 2012 Microsoft?

    It's far too late in the year to plan a rollout of a service pack, or was this the plan? Release SP2 and take an extended Christmas holiday!

    *more frustration at Microsofts hollow promises*

  58. BD ADMIN says:

    Installed RU5 and it looks like it is stable with no issues found and everything works well.

    But just found 1 event after installation as mentioned below

    Event ID : 4999

    Source : MSexchange common

    Watson report about to be sent for process id: 4628, with parameters: E12, c-RTL-AMD64, 14.01.0325.000, OWA, M.E.Infoworker.Common, M.E.I.C.A.QueryGenerator.HandleCrossForestMailbox, System.NullReferenceException, 5608, 14.01.0339.001.

    ErrorReportingEnabled: False

    This event  was found on 1 of the Hub / CAS -HUB /CAS role installed on same server and CAS configured as CAS Array.Before installation of RU5 never found this event.

    Also when would SP2 release ?

  59. BD ADMIN says:

    RPC Client access service is still crashing.Will this be resolved in SP2

    Also wanted to know if this causes Outlook connected users to disconnect and reconnect after some time.

    Watson report about to be sent for process id: 3220, with parameters: E12, c-RTL-AMD64, 14.01.0339.001, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Parser, M.E.R.PropertyValue.ParsePropValue, System.NotSupportedException, 275e, 14.01.0323.000.

    ErrorReportingEnabled: False

  60. Jonasca1 says:

    Just installed RU6 without any problems. Was on RU2 before. I disabled forefront for exchange, just to be sure, even though i heard that this is not needed anymore – should be enough to just stop services. I totally agree with other comments here, this should be automated by the installation.

  61. HotFix says:

    FYI – I stopped the Forefront controller service (which stopped all Forefront services) and ran the update to SP1 RU6, when the server came back up the Forefront services were NOT started and when I started the Forefront console it complained about not being hooked into the store with the error "The MS Information Store is running but the Forefront VSAPI Library is not registered."

    I followed the steps in social.technet.microsoft.com/…/58f712ae-e141-4010-b8c8-0e0c4eab9d3e and got it hooked back in. This happened on multiple servers, and was consistent.

    When I didn't stop the Forefront services before hand, RU6 applied fine and everything was 100% happy post reboot. The moral of this story is to ignore the recommendation of stopping the Forefront services and to just plan on rebooting the server after installing RU6. Really rebooting isn't a horrible thing if you are taking down all of the Exchange services anyway – you might as well reboot.

Comments are closed.