Home

Update 4/11/11: Please note that the E2010 SP1 RU3 will be available via Microsoft Update on 4/24/11.

On March 14th we posted an announcement to the EHLO blog about removing Update Rollup 3 for Exchange Server 2010 SP1 due to an issue related to Blackberry devices.

The Exchange Servicing team has fixed the reported issue with E2010 SP1 RU3 and is making available a new version of RU3 for our customers, version 14.01.289.007, (KB2529939). We strongly advise all customers install this newly released version of Microsoft Exchange Server 2010 SP1 Update Rollup 3 and to discard any prior version of RU3 (KB2492690) which you may have.

RU3 Installation Guidance:

  • Customers with RU3 already installed within your Exchange environment

    It is not necessary for you to uninstall the existing RU3 within your environment. The new RU3 package can be installed over the top of the existing package installed on your servers.

  • Customers with previous SP1 RUs installed within your Exchange environment

    You can simply install the new version of the RU3 package.

General RU Installation Guidance

  • Note for deployments that leverage Forefront Security for Exchange: For those of you running Forefront Security for Exchange perform these important steps from the command line in the Forefront directory before and after this rollup's installation. Without these steps, Exchange services for Information Store and Transport will not start back up. You will need to disable Forefront via "fscutility /disable" before installing the patch and then re-enable after the patch by running "fscutility /enable" to start it up again post installation.

We deeply regret the impact that these issues have had on you, our customers, and as always, we continue to identify ways to better serve your needs through our regular servicing releases.

Kevin Allison
General Manager
Exchange Customer Experience

73 Comments
Not applicable

nice!

Not applicable

Disabled Forefront but the update still wouldn't install:

Product: Microsoft Exchange Server - Update 'Update Rollup 3-v3 for Exchange Server 2010 Service Pack 1 (KB2529939) 14.1.289.7' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: go.microsoft.com/fwlink

Not applicable

Curiously, I don't see the KB article for the Blackberry bug introduced by the original RU3 in the list of things fixed by the new RU3. :)

Not applicable

Does this also resolve the delay issues in Outlook 2007/2010 clients?

Not applicable

Thanks for the quick fix. The Forefront pre- and post-steps however are very annoying. Can't you just add this to the patch setup?! I hope it'll never get as bad as the Sharepoint or SCOM patches.

Not applicable

Cool!  ...but i think i'll wait some time before applying this... :D

Not applicable

I'm also curious as to what the "issues" are.  

Not applicable

Guys - we discussed what changes were being made to E2010 SP1 RU3 last week.  See blogs.technet.com/.../exchange-2007-2010-rollup-3-status-update.aspx for more details.

Ross

Not applicable

Unfortunately there is a contradiction involved between the post, which is bound to cause confusion (as if there is not enough now with the initial bait and switch RU3's).  

From here:

"On March 14th we posted an announcement to the EHLO blog about removing Update Rollup 3 for Exchange Server 2010 SP1 due to an issue related to Blackberry devices.

"The Exchange Servicing team has fixed the reported issue with E2010 SP1 RU3"

From the other post, blogs.technet.com/.../exchange-2007-2010-rollup-3-status-update.aspx

"Specific to this second issue we uncovered a problem which manifested as an email delivery delay for users of Microsoft Outlook 2007 or 2010.  Our investigation of the problem exposed a rare situation in Exchange 2010 where notifications were not sent to these clients.  What changed in E2010 SP1 RU3 is that this situation is more likely to occur because of code added to support coexistence in cross-premises environments, i.e., users within an enterprise both on-premises and in the cloud"

Unfortunately, I was on the receiving ends of both RU3 disasters, corruption on 2007 databases as well as the Outlook and BES issues with 2010 due to being in the midst of a migration. This unfortunately caused some rather visible bad impressions from the user base as well as the management team, to the point where they are utterly gunshy about future updates, so I am stuck with the existing, visibly "broken" RU3's (could not get a window to remove them) for a couple of weeks until they verify everything is as advertised with this patch and then they will schedule a window.

Thanks.

Not applicable

Just installed update on two Exchange 2010 SP1 servers and still have same issue with Outlook 2003 clients. Is UDP Notifications feature get back to Exchange Server? Do I suppose to revert changes in Registry to make it work? EnablePushNotifications - is it should be 0 or 1???

I was waiting for the update specifically to fix Unknown Error issue when users trying to delete messages and Outlook 2003 not updating it fast enough. I cannot turn on Exchange Cached mode as it is a Terminal Servers. What's next? How we suppose to go around this issue?

Not applicable

Agree completely with @Armen. Continue to have the same issues after installing RU3. Can someone from MS please report whether this is fixed or not, and if it "has" been fixed, why it continues not to work.

Same scenario as before. User on Outlook 2003/Exchange 2003 (Online mode). 10 e-mails in Inbox, deleting one-by-one, all move to Deleted Items and nothing remains in Inbox.

User on Outlook 2003/Exchange 2010 (Online mode). 10 e-mails in Inbox, deleting one-by-one, all "move" to Deleted Items (no. of items updates) but some (usually 3-4) remain in Inbox and do not move. Subsequent attempts to delete result in "Unknown Error" and attempts to open in "Can't open this item".

I have tried EnablePushNotifications registry entry at 0 or 1 with no difference in experience.

Can someone from MS please comment on this specific issue.

Not applicable

KB2410571: A RBAC role assignee can unexpectedly change permissions of mailboxes that are outside the role assignment scope in an Exchange Server 2010 environment (This is still not solved in RU3v3 for Exchange 2010 SP1)

And as Armen states even after RU3v3 is installed Outlook 2003 users still have delay when items are deleted or moved to another folder.

Please Microsoft can you make official statement once for all when and IF Outlook 2003 delay issue will be fixed? I have directors that’s asking me this question every day, would be good to have an answer for this, thanks.

Not applicable

I installed an IU of this RU on Monday and told the engineers that the blackberry duplicate issue wasn't fixed, also told the engineer that from the release notes "2417084  (support.microsoft.com/.../2417084 ) A public folder disappears from the Public Folder Favorites list of an Exchange Server 2010 mailbox" which was fixed in the original RU3 had reappeared or was broken again in this release.  Just don't understand how Microsoft could release this patch with this information.

Not applicable

Armen,

Yes you need to follow the steps in support.microsoft.com/.../2009942 to enable UDP support for OL2003 clients.

As for the "unknown error" issue, this is a result of timing - you move/delete the item and within the same second (or two) before the folder view refreshes, you attempt to move the same item again.  Since the item has already been moved, the second attempt results in "unknown error".

Ross

Not applicable

Please... let it work as promised this time - I would move to uninstall E2007 SP3 RU3 immediately so that you do not experience future database corruption events.  

Ross

Not applicable

Thanks for putting this out there, now there is some information missing to get the picture:

1. BES duplicate Sent itme issue. After this is fixed are there any additional steps required to "clean this up/out"?

2. Seems there has been some suggestions to settings such UDP notifcation for OL03. Does the UR correct this or is this a manual step that needs to be completed?

3. Outlook Cached mode clients and delay of delivery of email to outlook; I have seen several threads on this issue, but I am not sure this is adressed in this release. Can you confirm this is included or not? This seems to affect both OL07 and OL10 on several OS versions.

Thank you!

Not applicable

Ross,

Yes, now I can confirm we did follow ALL the steps on support.microsoft.com/.../2009942 and still experiencing the issue. As you was saying -  the "unknown error" issue, this is a result of timing - you move/delete the item and within the same second (or two) before the folder view refreshes and you're welcome to explain it to our users. They didn't experience it on the Outlook2003/Exchange2003 and now we moved to better, faster system and they getting this error. Why this refreshing timing happening?

We eventually will move to Outlook 2003 and I would like to upgrade all our client's workstations with it but as you understand you cannot do it overnight. Migration process takes some time and we are 2-3 month away from it. So, is it mean we don't have any solution here? Please clarify.

Thank you in advance and I understand you working hard on this but still - this is a big issue for us and a lot of other companies.

Not applicable

Correction to previous post, sorry for mistyping: we eventually will move to Outlook 2010 :) already tired of Outlook 2003

Not applicable

Can Microsoft please comment on whether or not the duplicate message issue with Blackberries has been resolved with this update? There is no mention of it in the description. I realize you mentioned it last week, but there is nothing that shows that this issue has been resolved. Thanks.

Not applicable

Simple question Yes/No

Is the enclosed fixed.  Several people asking here but nothing in KB or this article.

"Specific to this second issue we uncovered a problem which manifested as an email delivery delay for users of Microsoft Outlook 2007 or 2010.  Our investigation of the problem exposed a rare situation in Exchange 2010 where notifications were not sent to these clients.  What changed in E2010 SP1 RU3 is that this situation is more likely to occur because of code added to support coexistence in cross-premises environments, i.e., users within an enterprise both on-premises and in the cloud"

Not applicable

So, I applied the patch after getting around the 1603 issue, it says it applied with no errors, but when I check the build number in the EMC it has not itterated beyond 2010 SP1... so I rebooted & re-applied and still no change. Am I missing something? Rollups are still cumulative correct?

Not applicable

JLK: The console build number does not increment until the next service pack. If you want to verify which RU your servers are running, run the script found here: cid-14adc5cf1e0cbccf.skydrive.live.com/.../Get-ExchangeUpdateRollups.ps1

Not applicable

I am both a Forefront and a WSUS user. If I automatically deploy RU3 with WSUS, will it automatically disable/enable Forefront during the installation?

Not applicable

@JLK and Lars: Also check out Dude, where's my rollup?

Not applicable

@Ross Smith IV,

I know that the "Unknown Error" is a result of timing. It seems that MS know this as well.

I thought that this was the functionality that was supposed to be fixed with RU3. What I am saying is that this is not the case and RU3 does not fix the Outlook2003/Exchange2010 experience is this regard.

When this was in testing (prior to re-release), was the Outlook2003/Exchange2003 experience tested? Was a test similar to the one I described in my previous post conducted, and if so what were the results?

Can MS please comment on this specific issue and provide some guidance for those admins that are continuing to experience this problem?

Not applicable

I have the same problem like Jorgus. I cannot install Update Rollup 3 v3 with the same error. Any ideas?

Thanks!

Olli

Not applicable

Hi Guys - I am not surprised the the delete (UDP) issue not resolved with this roll up, but could someone let me know if this resolves the duplicate blackberry items?

Not applicable

Hi,

I've installed yesterday evening the update.

Problem with duplicated blackberry items was solved

Davide

Not applicable

JLK, Lars, Bharat,

I just look in Control Panel / Program / Programs and Features / Installed Updates and it tells me what Rollups are installed.  One of my test servers, for example, shows Rollup 2, Rollup 3, and Rollup 3 v3 installed.

Not applicable

Installed on multiple servers. Blackberry issues fixed.

@Kevin Allison, Ross Smith IV, Bharat Suneja: Thanks for keeping us updated through these blog posts. It's better to be informed than to wait and be frustrated. We also appreciate your decisiveness in recalling E2007 SP3 RU3 - it's commendable that you would risk the temporary customer frustration to avoid customers potentially losing data, even though there was apparently a very low possibility of that happening.

Please keep up the good work. We look forward to future RUs being uneventful.

Now for a more interesting question for Exchange pros - what's really in store in E15?

Not applicable

I've worked with Exchange since version 5.0 and love the product. However I'm growing increasingly concerned over this RU service release strategy. As development technologies and strategies have changed over the years I know it has becoming easier to roll releases from a product team. However; the error rate in service releases is growing and this particular one shines a bright light into dark corners of the development war room and internal SCRUM processes/QA/test/validation. The customer is NOT test/QA/acceptance and the large enterprises I work with will not tolerate these issues much more. Excahnge is becoming a sore topic unfortunately. What used to "just work" we now have to tip-toe with. Granted there are not many alternatives to a product such as this and nothing comes without issue. However these issues seem "self inflicted". I'm sure these concerns have been brought to the attention of everyone. Leverage the large partner/VAR community to help test/QA/accept if necessary - there are datacenters and labs all over the world that can help the product group deliver. Its undertsood that 100% validated/tested solution is hard to come by - and many of us will sacrifice features to keep things running smoothly. Afterall - we don't live to work on our Exchange databases.

Not applicable

@ConcernedFan-- I couldn't agree more! Historically, the Exchange product has been the poster child for Microsoft software. As an administrator, we have had the luxury of knowing that Microsoft has always had the best and brightest working on this product. I can remember the excitement of moving an organization from Novell Groupwise to Exchange 2003!

However, as you point out..the good ole days of having a solid product and confidence in product updates has dropped tremendously. I would have never thought that we would see the day that the Exchange product would experience such a black eye as it did over the past few weeks. Updates for two different product versions caused HUGE inconveniences for thousands of users worldwide!

Microsoft should realize that many organizations, especially large ones, have very closely monitored change control procedures. It's not as simple as just uninstalling a bad update. To further complicate the issue, if that particular rollup fixes an issue that we have been waiting for, you have a dilemma. Do you uninstall the update from multiple servers..reboot..install an interim update..reboot....only to have to schedule ANOTHER maintenance window to uninstall the interim update..reboot...install new rollup and reboot?

Finally, management is asking for an analysis of the entire situation. While I can provide the Exchange Team blog postings, that doesn't really satisfy "How was this allowed to happen in the first place?" question. Even opening a ticket with Microsoft Professional Support provided LESS information than was available via this website. It's like the Tier 1 technicians do not even read this blog...even after specifically sending them the link.

Sorry for the long post. Just wanted to provide some constructive feedback to the powers that be.

Not applicable

Luckily we never deployed these but it was just a timing thing that worked out.

In the old days, we wouldn't install an Exchange patch unless it fixed a specific issue we were having or that we expected to have. Otherwise, we just waited for the Service Pack. I can see why they had to move to a rollup model- supporting customers who had chose a bunch of "a la carte" patches in different combinations and having to test each one against the other must have been a nightmare (all those patches have to apply to the same binaries.)

We run every Update Rollup through at least a month in our labs, and that's usually after it's been out in the "wild" for a month (sorry and thanks to everyone else I guess, for being the earlier adopters.)

To AnotherConcernedFan (one customer to another) - if you have premier support, your TAM could probably get as much info as possible for your management. I don't think you'd get very far with tier 1 other than break/fix (but I agree they should at least know the info that's posted here.)

Not applicable

Thanks..!

I'm having a strange problem now in Exchange 2010. If a user loses a mail and can't find the email he was looking for we used to redeliver from our SMTP Server (It's much easier than doing a recovery) now when we try to redeliver the mail Exchange 2010 thinks it's a duplicate mail and its not delivering the mail.

I started message tracking it says mail was delivered but when I look into the Log Explorer it says  DUPLICATE under EventID and Source says STROEDRIVER.

How do I force the mail to re deliver? I think this changed with RU 3 -v3.

I appreciate any help...!

RG

Not applicable

Due to the pull and re-release of RU3 will RU4 be delayed from its anticipated May release?

Not applicable

So has the Blackberry fix and UDP support is finally good in KB2529939?

Not applicable

Why can't the update automatically disable/enable forefront?  Why can't you include this in the installation packages?  What happens when the update comes down via windows updates and the commands are not run?

Sick and tired of having to remember all this petty stuff with every release of every product.  You have to do this, don't forget to do this, do that, don't do that ... JUST INCLUDE IT IN THE PACKAGE?  Is that too much to ask for?

Not applicable

@Gus: ForeFront is not a part of Exchange - it's a separate product. You may need to follow similar procedures with any third-party products installed on the server.

Although doing so is possible technically, customers wouldn't want Exchange to touch other products or services installed on a server.

Not applicable

@Bharat Suneja [MSFT] (and others [MSFT])- Can you please answer @andy's and other's requests that the UDP support has been fixed in this release? I have installed the re-release of RU3 and applied the registry fix and still experience the same pre-release issues when using Outlook 2003 with an Exchange 2010 mailbox.

Can MS please confirm or deny that this has been fixed and provide some more information. Please?

Not applicable

can someone verify what the build number should be after installing RU3? When I click properties on any of my servers its showing "Version 14.1 (Build 218.15)". Since I am still having issues that were supposed to be fixed in this release I want to make sure it even applied correctly. Thank you

My ongoing issues if anyone is interested is UDP notification to Outlook 2003 clients not working, and a memory leak in the RPCClientAccessService which causes the server to have to be restarted every couple days.

Not applicable

00Hensley, as stated above, the build number you see there doesn't increase for update rollups.

See blogs.technet.com/.../3409469.aspx

Not applicable

Thank you Frank T. Verified that RU3 is installed on all servers, still having issues mentioned.

Not applicable

To Exchange team, I think you guys clarify the status of UDP support in response to various "UDP still not working" comments.  I know you guys are probably working on RU4 right now but an official response will help us to decide whether we should go ahead with RU3v3.  

Not applicable

My last comment never appeared, but if you want to prove the UDP issue, please ensure its enabled in the registry and then use wireshark to look for UDP packets (black lines of text) which will be outlook communication on its default port.

If UDP isnt working, there will be no UDP traffic flowing both ways.

I have RU3 v1 currently and until somebody can officially confirm the Blackberry issue is fixed, i will not be risking another upgrade.

I have a memory leak in RPCClientAccess.which is supposedly fixed in this release too, so i will now be building the Lab environment to prove this.

Not applicable

more on the UDP issue. I just did a packet capture on the CAS server and I do see UDP packets going out from the server to various workstations. However the Outlook 2003 clients do not get new email notifications and I am getting complaints about deleting items does not update their view like it should, ie the problem its supposed to fix.

Not sure what to make of that.

Not applicable

"Bharat Suneja [MSFT] 12 Apr 2011 2:27 PM # @Gus: ForeFront is not a part of Exchange - it's a separate product. You may need to follow similar procedures with any third-party products installed on the server.

Although doing so is possible technically, customers wouldn't want Exchange to touch other products or services installed on a server. "

Bharat - I understand what you're saying - that Exchange shouldn't interfere with other products installed, however, if the option is that the servers will become a very nice expensive bricks if the services are not disabled then the exchange team are neglecting the customer. The check for the service, it's status and the integration should, at the very least be included in the pre-requisites check with a straightforward message informing the admin how to clear the problem.

There is NO mention of this dance required to install a service pack or update in the technet library for Exchange 2010 - WHY?  If the answer to that is "Well we've blogged about it and there is a wiki from the Forefront team" then your understanding of customer requirements are sadly lacking. As this is an important piece of information to enable successful deployment THE place for it is in the Exchange Documentation in the Technet library.

I'm all for Web 2.0, but I'm getting a little tired of having to ferrett around various blogs and wikis for technical documentation that should be in the library.

Not applicable

I installed RU3 and i got new issues to the owa app. I am not able to delete or move emails in the web frontend. I am running in a timeout issue. Syncing deleted emails over BES still work. Send to this i am not able to access the Option Page over OWA APP anymore ...

Does anyone discovered similar problems?

Not applicable

Can anyone else confirm that after applying R3-v3, they have been seeing issues with deleting and moving items in OWA?

Not applicable

@00Hensley:

Well that is a good sign, you now need to check whether the Outlook Clients are 2003 SP3 minimum, and that they are using their own mailbox when this issue occurs, or a secondary mapped mailbox in Outlook.

Do your Outlook 2003 clients us a non-standard UDP Port?

ave you definitely configured the registry on your CAS Servers properly:

support.microsoft.com/default.aspx

Not applicable

@Strange-Danger: it sounds like a failed RU install to me.

Navigate to your OWA folders on your c$Program FilesMicrosoftExchange ServerV14ClientAccessOwa folder.

Find the latest revision folder name, e.g. 14.1.287.0, and make sure that all files are in that folder and subfolders.

It sounds to me like you need to try a re-install of the update package or rebuild your OWA directories.

Also, check your URL's on the ECP folders and authentication is correct.