In any org, not all upgrades succeed, you might come across a server, whether it is a multi-role, CAS, HUB or MBX server where it fails.

The error is a bit cryptic, the setup creates the assemblies and then rolls back immediately with a premature failure.

To be able to see what is causing the issue, you need to capture the setup process to a log file.

To do so, you would run the setup from an elevated command prompt as follows:

  • Exchange2010-KB4487052-x64-en /lxv c:\installsLog.Log to generate Log file

In this example, what stood out in the log file at the bottom was the following:

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.

You might think that there is a problem with the Rollup and re-download it but the first thing that came to mind was the execution policy on PowerShell.

You can do so by launching PowerShell elevated and running the following command:

  • Get-ExecutionPolicy
Exchange 2010:- rollup upgrade fails
Exchange 2010:- Rollup Upgrade Fails 1

As you can see it is set to restricted. This was changed to unrestricted and you can do so using the following command:

  • Set-ExecutionPolicy unrestricted
Exchange 2010:- rollup upgrade fails
Exchange 2010:- Rollup Upgrade Fails 2

Accept the change and now launch your setup again from an elevated prompt and it should succeed.

Hope it helps.

Discover more from COLLABORATION PRO

Subscribe now to keep reading and get access to the full archive.

Continue reading