A Reboot From a Previous Installation is Pending

Posted on 09/07/2021 by PeteLong

KB ID 0001755

Problem

You may see the “A Reboot From a Previous Installation is Pending” error when either attempting to install Microsoft Exchange or apply a cumulative update, (which is basically a reinstall anyway!) You may also see this if you are only installing the management tools.

At command line;

A reboot from a previous installation is pending. Please restart the system and then rerun Setup.

Or if you are running the install upgrade from the GUI;

A Reboot From a Previous Installation is Pending : FIX

Before we go any further, I’m assuming you have rebooted the server in question, this post is for the good folk who have already done the obvious, and are still getting prompted with the above error!

This happens because the setup procedure checks TWO registry keys, though to be fair the first one is for older versions of the OS so don’t be surprised if you look for it, and the key does NOT exist, there’s nothing wrong!

Open the registry editor and navigate to;

[box]

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile

[/box]

If the key exists either delete it completely or set its value to ‘0’ (Zero).

Then navigate to;

[box]

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

[/box]

This is a string value which means it can contain multiple values, as you will probably see most of them will be corrupt links to things. Many sites will tell you to delete the entire string value (PendingFileRenameOperations), but you don’t need to simply empty out all the values like so, before;

After

Then retry.

Windows USB Install Error 0x80070026

Posted on 02/11/2018 by PeteLong

KB ID 0001485

Problem

Now physical servers don’t really come with DVD drives any more, Im forever deploying Windows, ESX, or some other Linux OS via a bootable USB drive.

I generally use Unerbootin, and just point it at the .iso file and away we go, which I did this week when trying to deploy Window Server 2016. However when I did that, this happened;

Windows cannot open the required file {Drive}:\Sources\install.wim. Make sure all files required for installation are available, and restart the installation. Error code: 0x80070026

Solution

I assumed there was a problem with my .iso, so I downloaded a new one, same problem. I then put the drive in another machine and went to make sure that install.wim was there, (in fact I was going to copy the install.wim from the .ISO onto the drive,) when I noticed something. The install.wim on the drive was 4 GB and the source file was over 5GB.

Only at this point did I realise what was happening! The USB drive is formatted at FAT, and that file is too big to be supported in that file system?

Format the drive at NTFS;

Then recreate it

And Windows Server 2016 installed fine! (I’ll put that one down to experience!)

Exchange: “BuildToBuildUpgrade” Error

Posted on 12/05/2018 by PeteLong

KB ID 0001436

Problem

In the middle of an Exchange upgrade I got a bit stuck with the following error;

“Setup previously failed while performing the action “”BuildToBuildUpgrade” You can’t resume setup by performing the action “Install”.

There are a couple of variations on this error as well, you can also see either of the following;

“Setup previously failed while performing the action “Install” You can’t resume setup by performing the action “BuildToBuildUpgrade”.

OR

“Setup previously failed while performing the action “Uninstall” You can’t resume setup by performing the action “Uninstall”.

That last of those I’ve covered before here.

Solution

As you are probably already aware this is because either an install/upgrade/uninstall has failed, and you are attempting to get the process going again, (or someone else has, and left it ‘broken’!)

This is happening because as Exchange performs installs/upgrades/uninstalls it creates some values in the registry as it progresses. And if you attempt to restart the process, it can see these entries, and that’s what causes the error.

So you simply need to remove them;

Open the registry editor (Windows Key+R > Regedit {Enter}).

Where you navigate to, depends on your version of Exchange;

[box]

HKLM\Software\Microsoft\ExchangeServer\v14\ (Exchange 2010)

HKLM\Software\Microsoft\ExchangeServer\v15\ (Exchange 2016 and 2013)

[/box]

Within all the sub keys (i.e. below v14 or v15) there will be a ‘Value’ thats within the role that was being installed/upgraded/uninstalled, when the process ‘fell-over’. That value will be called ‘Action‘ locate and delete it.

Also be on the lookout for a value called ‘Watermark’ if you see that, remove it also, and Exchange will start a fresh, install/upgrade/uninstall.

When you have checked all the sub keys, restart your install/upgrade/uninstall.

Exchange 2016 Setup Error “Server-Gui-Mgmt-Infra” Isn’t Installed

Posted on 07/02/2018 by PeteLong

KB ID 0001397

Problem

During the Exchange 2016 Setup Readiness Checks;

The Windows component Server-Gui-Mgmt-Infra isn’t installed on this computer and needs to be installed before Exchange Setup can begin

Solution

This is a known problem when installing Exchange 2016 on Server 2016, and was fixed in Exchange 2016 (Cumulative Update number 4). You are probably installing Exchange 2016 from the RTM media, (downloaded from Microsoft.)

You need to download a newer version of the Exchange 2016, install media, CU4 or newer. Use the following link;

Updates for Exchange 2016

Note: The update, is the full install media, (It might just look smaller, because it does not have every language pack in it!)

VMware Linux VM – ‘No DEFAULT or UI configuration directive found’

Posted on 23/07/2017 by PeteLong

KB ID 0001334

Problem

Last week while trying to create a Linux VM on a VMware ESX 6.5 server, I saw this;

No DEFAULT or UI configuration directive found

Solution

Normally the error indicates theres something wrong with the install media, so I deleted it and uploaded it again, same error. So I downloaded the setup iso file again and checked its checksum, to make sure it was OK, (it was, but the problem persisted).

To fix the problem I simply had to connect to the host, using a different browser, (I used Firefox). Upload the .iso file and start again. Once I did that, hey presto;

Exchange 2016 Install Error ‘Skipping creating Discovery Arbitration Mailbox because of insufficient permission”

Posted on 01/08/2016 by PeteLong

KB ID 0001221

Problem

Note: Can also be seen on Exchange 2013.

While installing a new Exchange 2016 Server into a clients Exchange 2010 infrastructure last week, the setup failed with the following error.

A cutdown version of the error;

[box]

          Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
          }
          }
          else
          {
          write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
          }
          }
        " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow)
   at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.Validate(TDataObject dataObject)
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`3.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`3.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

[/box]

Click for the full Error.

Solution

This error is about arbitration mailboxes, so let’s have a look at those, (on my Exchange 2010 server, in the Exchange Shell).

[box]Get-Mailbox –Arbitration | Select Name,Database[/box]

As you can see I’ve got a system mailbox that is not attached to any database, (the one with the yellow error under it). So I simply need to associate that with a mailbox database.

[box]Set-Mailbox ‘{mailbox}’ –Database {Exchange-2010-Database} –Arbitration[/box]

Answer ‘A’ for ‘All’ when prompted.

Working Example

[box]Set-Mailbox ‘SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}’ –Database ‘Mailbox Database’ –Arbitration
[/box]

Now check the arbitration mailboxes again, and there should be no errors.

Re-run setup.exe from the Exchange install media again, and the install should detect the failed one, and let you continue from the point of failure.

VMware vCenter Install ‘Error 26002’

Posted on 17/11/2015 by Migrated

KB ID 0000941

Problem

While attempting to install vCenter 5.5, I got the following error.

Error 26002. Setup failed to register vCenter Server. This might indicate a problem with the SSL certificates for vCenter Server. Search the VMware Knowledge Base (http://kb.vmware.com) for “Error 26006” for more information.

Earlier on in the install it had asked me if I wanted to overwrite the certs, and I just clicked OK, this probably was not such a good idea!

Solution

1. Navigate to C:Program DataVMwareVMware Virtual Center >Locate the SSL folder and rename it to SSL-OLD.

2. Navigate to C:Program DataVMwareInfrastructureInventory Service > Locate the SSL folder take a copy of it.

3. Paste that folder back in the C:Program DataVMwareVMware Virtual Center location to replace the folder you renamed earlier.

4. This is what the folder should now look like.

5. Now attempt the install, and it should complete without error.

vSphere Client cannot be installed on a Domain Controller

Posted on 17/11/2015 by Migrated

KB ID 0000968

Problem

I tried to install the VI client on my test network and this happened;

vSphere Client requires Windows XP SP2 or later. vSphere Client cannot be installed on a Domain Controller.

Solution

Well I’m not over the moon about that? Ive only got one permanent VM and it’s a DC? Who came up with this? What about sites who have a single DC on an ESX box? What are they going to do!

Turns out its quite easy to bypass, install the VI client from command line with a switch on the end, like so;

[box]
{Path}VMware-viclient-5.5.exe /VSKIP_OS_CHECKS=”1″
[/box]

The install will now complete without error. I thought that it might be a cunning ploy to get me to use the new web client instead, so out of interest I tried that, and got the following error;

vSphere Web Client requires Windows Server 2008 or later. vSphere Web Client cannot be installed on a Domain Controller.

Fair enough! So I tried the same switch on that, and guess what? That works as well.

[box]
{Path}VMware-WebClient.exe /VSKIP_OS_CHECKS=”1″
[/box]

Other Options

You can also use the ‘Thin App’ version of the VI client, (even if you don’t have ThinApp) you can download it here.

Microsoft Autoroute Install Errors (Windows 8)

Posted on 17/11/2015 by Migrated

KB ID 0000686

Problem

I only use Autoroute once a month, (when I put my mileage in at work!). So this month I had a head slap when it was one of the bits of software I had forgotten to install on my freshly rebuilt laptop. So I fired up the setup for Autoroute 2007 and it failed.

So I moaned and was furnished with a shiny new copy of Autoroute 2011. But when I tried to install it, this happened.

Microsoft Autoroute 2011 Setup One of the prerequisite components failed to install. Setup will now exit.

Solution

It installed fine on my colleagues laptop so the problem had to be something to do with me. I did manage to get the product installed by running the data.msi file and installing the product that way, this got me further but then I got this error,

Microsoft Autoroute A licensing initialisation error has occurred. Please contact customer support for more assistance. Error 0x80070005

I got round that by installing in compatability mode, and running the install from command line admin mode. (Press Windows Key+X).

When I finally got the program installed, it would launch then crash. I installed it in a virtual machine and it worked faultlessly? I unistalled the product and compared my installed programs with the ones on my working virtual machine, I found that the C++ Distributable and the Microsoft Access database engine 2010 had different sizes? These were the prerequisites that Autoroute wanted to install at the very beginning.

So I unistalled everything ad tried to install the prerequisites manually, and then I located an issue,

You cannot install the 32 bit version of Microsoft Access Database Engine 2010 because you currently have 64-bit Office products installed.

So (begrudgingly) I removed x64 office and installed x86 Office.

Then the Access Database Engine Installed but the C++ wouldn’t! Because a newer version was installed.

A newer version of Microsoft Visual C++ 2010 Redistributable has been detected on the machine.

Microsoft could you please make this software MORE incompatible with MORE bits of your OWN software please, I’ve spent a large chunk of my morning trying to fix this now!

Fix the problem and get it installed.

1. Make sure you are running an x32 bit version of Office. (see above)

2. Press Windows Key+R > appwiz.cpl {enter}, Uninstall ALL the following if present,

Microsoft Office Access Database Engine. Microsoft Autoroute 2011. ALL Instanced off C++ Redistributable (all the x86 ones and All the x64 ones).

3. Reinstall Autoroute 2011.

4. Install the x64 bit C++ Redistributable from here.

5. It should now work fine.

SQL Install Error “SQL Server Browser Service Group Does Not Exist”

Posted on 17/11/2015 by Migrated

KB ID 0000689

Problem

Seen when reinstalling SQL 2008 R2 on a domain controller. Note: as a background the SQL Server was installed previously and then the server was promoted to a domain controller. Then when the attempt to reinstall SQL was carried out this happened:

Microsoft SQL Server 2008 R2 Setup
The following error has occurred.
SQL Server Browser service group does not exists. Check for earlier failures in the setup

Note: Yes thats a typo, but there is a typo in the error message.

Solution

1. You need to create the group(s) manually, logon to a domain controller > Windows Key+R (to run) > type ‘dsa.msc’ > Enter.

2. Create two Windows security groups called;

[box]

SQLServer2008SQLBrowserUser${ServerName}
SQLServer2005SQLBrowserUser${ServerName}

[/box]

3. Retry the install.

Problem

A Reboot From a Previous Installation is Pending : FIX

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links

Problem

Solution

Other Options

Related Articles, References, Credits, or External Links

Problem

Solution

Fix the problem and get it installed.

Related Articles, References, Credits, or External Links

Problem

Solution

Related Articles, References, Credits, or External Links