Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 447
  • Last Modified:

Unable to install SP2 Rollout 4

I am trying to install Rollup 4-v2 on Exchange 2010.  I tried this on 2 different servers and I come up with the same error.  I did stop IIS prior to install.

"Setup wizard for Update Rolloot 4-v2 for Exchange Server 2010 Service Pack 2 (KB2756485) ended prematurely."

I do get error 1603 in the eventlog and I have followed this:
http://go.microsoft.com/fwlink/?LinkID=191548 but it has not helped.

Any suggestions?
0
FundFire
Asked:
FundFire
  • 7
  • 2
  • 2
1 Solution
 
AmitIT ArchitectCommented:
Did SP2 is already installed?
0
 
FundFireAuthor Commented:
Yes.  The version that I have is 14.2 Build 247.5.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Why dont you try to upgrade to RU5v2 ?
Is the Installer service running on the server ?
Did you try to download a fresh file and install ?

- Rancy
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
FundFireAuthor Commented:
I tried RU5v2, the same thing.
Installer service was not running I started it but I got the same error.
Download fresh copy, the same thing.
0
 
AmitIT ArchitectCommented:
can you run sfc /scannow from cmd
0
 
FundFireAuthor Commented:
I ran it and got back:
Windows Resource Protection did not find any integrity violations.
0
 
FundFireAuthor Commented:
I captured the log in case you guys can see something in there.
update5a.log
0
 
FundFireAuthor Commented:
Hi guys,

One question, how do you upgrade exchange sp1 to sp2?
0
 
FundFireAuthor Commented:
I was finally able to install Roll up 4.  These are the things that I did:

Followed this link:
http://www.expta.com/2012/08/exchange-2010-sp2-roll-up-4-does-not.html

especially the section that says this:

1- My problem was that I installed PowerShell v3 before Update Rollup 4-v2, so "control cannot leave a finally block" was an issue. Rather than substituting an entirely blank script or commenting out the return statement in C:\Program Files\Microsoft\Exchange\V14\Scripts\ManageScheduledTask.ps1, I changed "return $success" to the logically equivalent "Write-Output $success" in line 462. I also removed the now invalid digital signature. My ExecutionPolicy was already RemoteSigned. With these changes the rollup installed normally. The rollup didn't replace the ManageScheduledTask.ps1 script. I ran the rollup msp from the GUI rather than an elevated command prompt. I was logged on as a builtin Administrator. That didn't seem to be a problem. I did open its properties page and unblock it, however.

2- I downgraded my powershell to V 2.
uninstall WMF 3.0 (which includes PowerShell 3.0, which is not suitable for Exchange 2010) from Control Panel > Programs and Features. No need to uninstall .NET 4 - it runs side-by-side with .NET 3.5 and is not an upgrade.

3- I DID NOT do this, it would not install, I left it as Remotesinged.
PowerShell : Set-ExecutionPolicy -scope LocalMachine - ExecutionPolicy Undefined

After this I was able to install.  

I have to say this was so frustrating because this was a fresh install and I had to go through this to install a roll up.  Microsoft needs to do better testing.
0
 
FundFireAuthor Commented:
I was not able to get a bottom of this through expert exchange and followed other link.  Although I really appreciate all the assistance I received.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 7
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now