Wednesday, December 12, 2012 3:58 PM
Exchange 2010 SP2 Rollup 5 V2 today (KB2785908) keeps failing regardless of whether I try installing using Microsoft Update (fails with error 80070643) or the download ("Setup ended prematurely because of an error.")
Event Viewer has this to say ... Product: Microsoft Exchange Server - Update 'Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 (KB2785908) 14.2.328.10' 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: http://go.microsoft.com/fwlink/?LinkId=23127
Server has all roles and is current up to SP2ru5.
Here is the Windows Installer log: https://skydrive.live.com/redir?resid=E590E0F619452189!9683&authkey=!AB1zXR5c7Sk3lF0
- Edited by Scott Miller (Work) Wednesday, December 12, 2012 4:08 PM
Wednesday, December 12, 2012 4:40 PMDid you run it as administrator?
Wednesday, December 12, 2012 4:52 PMWindows was logged-on as an administrator (the domain administrator in fact.) I can try again using "Run As ..."
Wednesday, December 12, 2012 5:00 PM
Same here on an SBS2011.
This is what i have tried so far:
- stopped exchange services manually
- ran the rollup from an admin command prompt
- repaired .Net 4 Client Profile
No luck ...
Wednesday, December 12, 2012 5:19 PMI am on Server 2008R2. 65 views in under 2hrs ... I do not think we are alone in having issues with this rollup.
- Edited by Scott Miller (Work) Wednesday, December 12, 2012 5:19 PM
Wednesday, December 12, 2012 5:25 PM
I would try "Run As".
May or may not help, but I recall that solution working for me when I could not otherwise install RU8 for Exchange 2007 SP3 (yes, I realized entirely different version) - and also simply open the antivirus management console that was installed on that server.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.
Wednesday, December 12, 2012 5:28 PM
I actually had a similar issue with Rollup 4 but am not sure how i fixed it exactly. Am quite sure though this helped: http://exchangeblog.pl/en/tag/exchange-2010-sp2-rollup-4-v2/
Will try that later ...
I could reproduce the error but 1st: KUDOS to our polish friend from exchangeblog.pl!!!
So to sum up here is how it works step-by-step:
1. locate KB2506143 and uninstall it
3. open windows update from systray or control panel -> now there will be 2 updates available: KB2506143 and KB2785908
4. uncheck KB2506143 and install only KB2785908
5. open windows update again and install KB2506143
6. reboot ... and DONE!
Instead of using windows update you can certainly install the updates manually (with elevated rights!).
Wednesday, December 12, 2012 5:40 PM
Windows was logged-on as an administrator (the domain administrator in fact.) I can try again using "Run As ..."
Whenever installing anything on a Windows 2008 Server (not only Exchange Updates) one should always to it with elevated privileges (run as administrator).
Don't forget that User Account Control (UAC) is enabled by default.
<snip from your log file>
msgErrorExchangeAdmin = The user who's currently logged on doesn't have sufficient permissions to install this package. You need at least Exchange Server Administrator permissions on the current computer to complete this task.
- Marked As Answer by Scott Miller (Work) Wednesday, December 12, 2012 6:07 PM
Wednesday, December 12, 2012 6:09 PMI do not know if opening a command prompt as an admin and running the rollup was the solution, or if uninstalling WMF 3.0 did the trick, but combined I was able to install the 5v2 rollup.
- Marked As Answer by Scott Miller (Work) Wednesday, December 12, 2012 6:11 PM
Wednesday, December 12, 2012 7:19 PM
I had the same Exchange Server Administrator permissions error in the log file.
Removing the WMF 3.0 update that was installed by Windows Updates before the Rollup, allowed the rollup to install.
- Proposed As Answer by WormGeo Wednesday, December 12, 2012 7:20 PM
Wednesday, December 12, 2012 7:36 PMDitto that - same problem on SBS 2011 - fully patched. Restarted and tried several times with the update failing. Hope someone offers up a solution soon..
MCP, MCTS, PMP
Wednesday, December 12, 2012 9:44 PM
I can confirm that removing the optional Windows Management Framework 3.0 update that came out at the same time as this Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 will allow you to install the Rollup 5-v2 update with no errors. If you installed the WMF 3.0 update then the rollup 5-v2 update fill fail with reason "windows update encountered an unknown error".
- Proposed As Answer by paul-telluric Wednesday, December 12, 2012 11:03 PM
Wednesday, December 12, 2012 11:03 PMThanks to Valtteri for posting this! I uninstalled Windows Management Framework 3.0, which was an optional update as he pointed out. After restarting the server, I was then able to successfully install the Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2. Fix confirmed!! :]
MCP, MCTS, PMP
Thursday, December 13, 2012 1:09 AM@#$#@$ sorry not swearing at you, swearing at Microsoft. PowerShell 3.0 is not supported on Exchange 2010 and in my opinion should not be offered up on SBS 2011 boxes.
Thursday, December 13, 2012 8:29 AM
WMF 3.0 uninstall
WMF 3.0 inst.
-> okay :-)
Thursday, December 13, 2012 11:58 AM
@#$#@$ sorry not swearing at you, swearing at Microsoft. PowerShell 3.0 is not supported on Exchange 2010 and in my opinion should not be offered up on SBS 2011 boxes.
Hee hee. Noticed that this is rolled out via Windows Update this week across the board. It will break Exchange, especically UM. I only went there for use of Windows 2012 Server Manager, which is great, by the way. But there is an awfull lot of faffing about with WMF 3.0 (of which PowerShell 3 is a part.) I think you are right. This could be a 'left hand/right hand' thing.
Oh well. Bulletin board is going to busy for a while... :)
Anthony Sheehy - MCP, MCITP
Thursday, December 13, 2012 5:33 PM
I can't believe this has not been tested ... indeed removing WMF 3.0 will let you install Exchange 2010 sp2 rollup 5v2.
Just for your information ... Exchange 2007 SP3 rollup 9 is not impacted by this behavior.
I've been able to install it on a Windows Server 2008 sp2 with WMF 3.0 already installed : no error.
Starting being tired of those incoherent releases from Microsoft.
So for all future ROLLUP for Exchange 2010 ... we will have to unistall WMF 3.0 ? What about the installation of Exchange 2010 SP3 in a near future ? Will it be WMF 3.0 capable ? Hope so ...
Thursday, December 13, 2012 5:37 PM
Given that PowerShell 3 is not certified with Exchange 2007 I would not be deploying that on that platform. Is there a need for WMF 3 on an Exchange 2007 box?
Exchange 2010 sp3 will support PowerShell 3. Until then....
Thursday, December 13, 2012 6:02 PM
It's just to point out that WMF 3.0 will come with problems on Windows 2008 R2 sp1 and not on Windows 2008 sp2 ...
Just annoying ...
Thursday, December 13, 2012 7:09 PM
Thanks - this works well.
Thursday, December 13, 2012 8:47 PMI hope Microsoft is paying attention. Now that they have released both updates together, and in some cases the two have a conflict, hopefully they will fix whatever is causing it.
Friday, December 14, 2012 7:21 AM
I do not have the WMF 3.0 installed on my mailbox server, when I run the update either from windows update or manually I gor the same error...
This is the first node in my mailbox DAG, I successfully updated the second one with this update.
Friday, December 14, 2012 1:30 PM
You say the server is a member of DAG ... have you moved all databases to other node ? I guess yes but just to be sure.
Can you activate adavanced logging when launching the update and let us know ?
Friday, December 14, 2012 2:36 PM
Hi, all the databases are now on the second node and up and running, this second node got the update successfully.
On the first node, the one on which I have the issue, I cannot start some exchange services after the failed try to install this rollup.
Friday, December 14, 2012 5:42 PM
Hum, you may have a partial install of this rollup.
Is it listed in installed updates in Add/Remove software ?
Your issue is different from what we are facing because in WMF 3.0 installed case ... nothing is modified and services are not stopped when trying to apply rollup.
If you can't bring up services on impacted node ... I suggest to reinstall from scratch your non working node.
Here are the steps to follow :
Hope it will help.
- Proposed As Answer by Ahmad K. Jayyusi Monday, December 17, 2012 11:29 AM
Friday, December 14, 2012 7:11 PMActually it is not installed in the Add/Remove software. mmm... I will try to recover this node and let you know the results.
Friday, December 14, 2012 10:21 PM
are you 100% positive KB2506143 is not installed?
You have to check in "installed updates" in the "Microsoft Windows" section:
... or you can use the following command to find it:
systeminfo | find "KB2506143"
Friday, December 14, 2012 11:12 PM
I am sure it is not installed, I check in "installed updates" and using the command, it is not installed.
Monday, December 17, 2012 5:01 PM
The update as installed via WSUS or Windows Update has a different KB article but it is still titled Microsoft Windows Management Framework 3.0. It will cause the same problem.
Anthony Sheehy - MCP, MCITP
Monday, December 17, 2012 10:01 PM
Thanks Jens Vorat, really works.
Monday, December 17, 2012 11:55 PM
WMF 3.0 breaks the Update5 v2 install. WMF 3.0 breaks SBS user account creation/email creation.
To fix this I had to roll back to before Updat4 install and remove WMF 3.0, reinstalled Update5v2 and forget WMF 3.0. Now it's all working fine. PITA MS!!!
Tuesday, December 18, 2012 4:02 PM
WMF 3.0 may possibly cause more problems than what you mentioned for SBS 2011 systems. I was in the process of building a 2011 system in my lab and accidentally installed WMF 3.0 on it. Once I started having problems and researched it, I then uninstalled WMF 3.0 and thought that everything was back to normal.
However, in looking at my event logs, I was unable to view the ForwardedEvents log. The error message was something along the lines of "Channel Missing". Further research showed that the portion of the registry:
was now missing from my test SBS 2011 system. I was able to copy that section of the registry from another system and replace it in the affected system and that fixed the problem with the ForwardedEvents log.
I don't know definitively if it was the process of installing and then uninstalling WMF 3.0 that caused these changes, but I'm very suspicious.
I also don't know what other problems may crop up down the line. As far as I'm concerned, WMF 3.0 is poison for SBS2011 systems. Stay Away.
Microsoft, WTF are you thinking?
Saturday, December 29, 2012 8:34 PM
I had the same problem. Could not install SP2 RU5-v2.
The error was the same as in the first posting. I tried all suggestions here, including some from other websites. I was absolute positive that Windows Management Framework 3.0 (WMF 3.0) was NOT installed on that SBS 2011 system. I anyway checked.
systeminfo | find "KB2506143"
systeminfo | find "KB2506146"
did not show any output.
Searching for WMF with several name variations in Windows Update also showed no result. So I confirmed that I had WMF 3.0 not installed.
Yet, RU5-v2 still won't install.
Finally I found the solution in my case.
I had to manually start the RU5-v2 update file from an elevated (run as Administrator) prompt. That's it.. nothing else. Then the installation worked fine.