Jump to content

Recommended Posts

Posted

Hi,

 

I'm a little stuck with applying an Exchange 2010 sp3 rollup package. I have all up to pack 11 installed but 12 fails to install with a 1603 error rolling back as soon as it stops the services. The log has a variety of errors so will post snippets of each and hopefully someone will be able to help.

 

These errors are in reverse order with last one in the log first.

MSI © (00:6C) [16:35:05:521]: Note: 1: 2262 2: Error 3: -2147287038

MSI © (00:6C) [16:35:05:521]: Transforming table Error.

 

Followed by

Property©: msgINTERIMUPDATEDETECTED = Unable to install because a previous Interim Update for Exchange Server 2010 has been installed. Please use Add/Remove Programs to uninstall the Interim Update before running this setup again.

 

There are no interim updates present in the ARP list

 

The next is a little confusing as there only appears to be one architecture version (x64) of this rollup available as far as I can see. I've been trying to find out how to check which version of Exchange is installed but not managed to find this yet. I'm pretty sure it's 64-bit. The rollup package is x64.

 

Property©: msgRequiresProc = The version of this file is not compatible with the version of Exchange Server 2010 that you're running. Check your computer to see whether you need an x64 (64-bit) or x86 (32-bit) version of this file.

 

The next one seems contradictory as am logged on as a domain administrator which in turn has Exchange Server Administrator permissions. I've also got another domain administrator to try installing this with no luck.

 

Property©: 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.

 

Then

MSI © (00:30) [16:34:52:567]: Note: 1: 2262 2: Error 3: -2147287038

DEBUG: Error 2826: Control BottomLine on dialog FatalError extends beyond the boundaries of the dialog to the right by 5 pixels

The installer encountered an unexpected error while installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalError, BottomLine, to the right

 

I dare say these are all errors relating to different components being installed in the rollup so hard for me to put my finger on it.

 

I've been running the installer from an administrator prompt and UAC is disabled as per many suggestions out there. Am I missing anything obvious?

Posted

Ok, so having spent more time on this with the help of the following article (technet.microsoft.com/en-us/library/ff772434(v=exchg.80).as​px), it appears that all of the above errors are false positives and generated only because verbose logging is enabled.

 

What I have found is that the first "Return value 3" event is what'll provide me with the real cause. In this instance this points to the inability to run a PS script as per case 1 in the above troubleshooting article but my policy is set to unrestricted on the server so should be able to run so again I'm a little confused.

Posted

There isn't a 32bit version of exchange 2010 that I'm aware of so it's definately the 64bit one you want (and must have installed).

 

The below should get you the exchange build number so you can check you really have update 11 successfully installed

Get-Command ExSetup | ForEach {$_.FileVersionInfo}

 

It does sound a bit like you might want to start again though as I've never encountered those errors. (new exchange vm, migrate everything, sort out old exchange server, migrate back)

If not maybe run installation as recovery from the previous update ( Setup /m:RecoverServer )

Posted
Anyhow if you have the UM role installed along with any other roles and have any other lang pack other than US installed you need to uninstall those before you install SP3. I think that's right if my memory serves me! but not sure if that error you are seeing is directly related to that but worth a punt.......
Posted

I'm running v14.03.0266.001 which according to https://technet.microsoft.com/en-us/library/hh135098%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396 is update rollup 11 although the version end is different there being a 002 rather than 001.

 

This is a new job and am tasked with making sure all servers are installing updates as per WSUS schedule. This one was failing and so am investigating but don't think I'd be given free reign to start again with this or do any sort of recovery. Maybe if I'd set this up from the start I'd be confident with this but wouldn't be a good start to the role taking such drastic action.

@HPlum78: Unified Messaging? SP3 is already installed along with all rollups up to 11. I'm not the Exchange administrator and haven't had previous experience of this. I'm literally tasked with updating the server with the latest updates at this time.

Posted
I forgot to add that I'd already tried applying rollup 15 and so tried this version (12) to see if it was this particular file, it wasn't. The same outcome happens regardless of version of rollup applying.
Posted
I sorta guessed that you would have to be honest, I did see something about running the update with a switch to rebuild a .msp file (maybe). Give me a few and I will see if I can dig it out, and if it applies.
Posted

I've actually managed to get a little further with this now following the last post on this site https://translate.google.co.uk/translate?hl=en&sl=de&u=http://www.mcseboard.de/topic/197327-exchange-2010-sp3-rollup-5-installiert-nicht/&prev=search

 

It now goes through with the process but then fails starting the service at the end and so still rolls back annoyingly. Again, the log file isn't the most helpful and still pointing at PS execution policy but I've triple checked this and it's set to unrestricted and not being applied in any way by GPO.

Posted (edited)

Well I've finally got the bottom of this much to my relief...and exhaustion.

 

Turns out it was down to an issue with some code in the PowerShell script "C:\Program Files\Microsoft\Exchange Server\V14\Bin\ManageScheduledTask.ps1" which the RU ran during the install process. Running this manually resulted in the error:

At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\ManageScheduledTask.ps1:462 char:5

+ return $success

+ ~~~~~~~~~~~~~~~

Flow of control cannot leave a Finally block.

+ CategoryInfo : ParserError: (
:)
[], ParentContainsErrorRecordException

+ FullyQualifiedErrorId : ControlLeavingFinally

 

Solution was provided in the last post here: http://www.expta.com/2012/08/exchange-2010-sp2-roll-up-4-does-not.html

 

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'm obviously installing a later RU but was still getting the same "control cannot leave a finally block" error during manual run.

Edited by randle

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...