Tag Archives: service pack 3

Windows XP Service Pack 3 Hangs on “Performing cleanup”

Posted on by

KB ID 0000364

Problem

Saw this a while ago, and just thought it was a “One Off”. Then on a visit to a client yesterday I saw it on both machines I was working on.

Solution

This might scare you, but you need to kill the update, don’t panic at this stage SP3 is already on.

Update 05/04/11: Before continuing please read the feedback below. Ive never personally seen any adverse effects from doing this and I’ve rolled out a few thousand service packs.

1. Right click your task bar and select “Task Manager”.

2. On the applications tab > Select the Software Update Installation Wizard > Click End Task > Accept any warnings etc.

3. Reboot the PC > SP3 installation will recover and finish, ignore any errors or warnings just let it boot up and you will be at SP3, at this point finish the good work by going to windows update and getting all the post SP3 updates.

Feedback from Patrick Wright (05/04/11)

I am sending you a message concerning your advice on the Windows XP SP3 install “hanging” at “Performing Cleanup…”.  The advice you give is to end the installation task at this point and reboot the computer.

The truth of the matter is that during the “Performing Cleanup…” step, there is indeed quite a bit of activity and updating going on.  I’ve had this step take as long as 6 hours on slower machines on our network but it finishes successfully.

For testing purposes, I tried your solution on three training machines that were still running SP2 and ran into numerous issues after rebooting with getting several programs to install that require a minimum of SP3–Adobe Standard/Professional 10 is only one example and will refuse to install on all three of the test machines that I tried your suggested fix on.  It appears that even though Windows shows in system properties to be upgraded to SP3, it is not completely finished if you stopped the install prematurely by ending that task. 

I strongly advise to consider changing your solution to simply wait out the “Performing Cleanup…” task until it finishes.  It can take a while.  I’ve found one way to help the process along is to set the process for the updater to “high priority” in task manager.  This resulted in drastically faster install times when the installer seemed to “hang” at that part of the install.

 

Related Articles, References, Credits, or External Links

NA

Exchange Install Error ‘Setup cannot continue with the upgrade because the ‘beremote’

Posted on by

KB ID 0000475 

Problem

Seen when attempting to install Service Pack 3 on Exchange 2007. On a server that’s also running Symantec Backup Exec.

Hub Transport Role Prerequisites
Error:
Setup cannot continue with the upgrade because the 'beremote' () process (ID: xxxx) 
has open files. Close the process and restart Setup.
Client Access Role Prerequisites
Error:
Setup cannot continue with the upgrade because the 'beremote' () process (ID: xxxx) 
has open files. Close the process and restart Setup.

Mailbox Role Prerequisites
Error:
Setup cannot continue with the upgrade because the 'beremote' () process (ID: xxxx) 
has open files. Close the process and restart Setup.

Solution

1. First make sure you are not currently running any backups with Backup Exec.

2. Click Start > In the Search/Run box type services.msc {enter} >The services console will open.

3. Locate the “Backup Exec Remote Agent for Windows” Service > Right Click and stop it. (Note: In the example above I’ve stopped all the Backup Exec Services, just to be on the safe side).

4. Now try again to install the service pack.

 

Related Articles, References, Credits, or External Links

NA

Exchange 2010 Service Pack 3 Error – ‘The IIS 6 WMI Compatibility component is required’

Posted on by

KB ID 0000771 

Problem

If you attempt to install Exchange Service Pack 3 on an Exchange server that is currently running Service Pack 1 you will see this error.

Error:
The ‘IIS 6 WMI Compatibility’ component is required. Install the component via Server Manager.

Solution

Note: This was a prerequisite for SP2, so if you do not see this error your Exchange was deployed with SP2 slipstreamed into it, or the problem was dealt with when SP2 was installed.

Microsoft Exchange Server Build Numbers

1. Launch the Exchange Management Shell

2. Execute the following two commands;

[box]

Import-Module servermanager
Add-WindowsFeature Web-WMI

[/box]

3. Try again to install SP3.

Related Articles, References, Credits, or External Links

Exchange 2010 Service Pack 2 Fails ‘Readiness Checks’

Exchange 2010 SP3 – Can I Upgrade to Exchange 2013

Posted on by

KB ID 0000770 

Problem

At the time of writing (14/02/13), the answer is NO, for full coexistence with Exchange 2013 you need to have Exchange 2013 CU1 (Cumulative Update), which at this time is unreleased (Expected Q1 of 2013 – so we are not far away).

Note: CU2 is now released.

Solution

So What do I get with Exchange 2010 SP3?

1. You can install Exchange 2010 on Windows Server 2012, (though you can’t in-place upgrade the OS of an existing Windows 2008 R2 server to 2012).

2. Full support for Internet Explorer 10.

3. All fixes from previous update roll-ups, (including MS13-012).

You will need to perform an AD schema update to install SP3.

Related Articles, References, Credits, or External Links

NA

Installing Exchange 2010 on Server 2012

Posted on by

KB ID 0000785 

Problem

With the release of Exchange 2010 Service Pack 3, Exchange 2010 is now supported on Windows Server 2012, but as there (at time of writing) is no media with SP3 slipstreamed into it, installing the product on Windows Server 2012 is a little problematic.

If you got here because you have tried and have got an error, follow the procedure below and you should have the product installed and running without any further problems.

To see the possible errors jump to the end.

Solution

1. If you have Exchange 2010 already deployed on the servers, I would suggest you get all these upgraded to Service Pack 3 before you start.

2. Install the Office 2010 Filter Pack, and the Office 2010 Filter Pack Service Pack 1.

3. Issue the following PowerShell Command;

[box]
Add-WindowsFeature Web-WMI,Web-Asp-Net,Web-ISAPI-Filter,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-Request-Monitor,Web-Static-Content,NET-WCF-HTTP-Activation45,Web-Security,Web-Windows-Auth,Web-Digest-Auth,NET-HTTP-Activation,Web-Basic-Auth,Web-Lgcy-Mgmt-Console,Web-Dyn-Compression,Web-Stat-Compression,RPC-over-HTTP-Proxy,RSAT-ADDS
[/box]

Note: Don’t panic if it appears to hang at 68% for a while!

4. Download this zip file, it contains a .reg file, run it and merge those files into the registry of the 2012 server.

5. Insert the Exchange 2010 DVD, or run setup.exe from the extracted Exchange 2010 install media.

Note: I’m using Exchange 2010 with SP1 included (because its the newest one I can download, and a version with SP2 or SP3 included is not yet available).

6. MAKE SURE, you DO NOT have the ‘Automatically install Windows Server roles and features required for Exchange Server’ option selected or you will see this error.

7. When complete install Service Pack 3.

Errors You May See If You Don’t Follow This Procedure

Error 1.
Error:
The following error was generated when "$error.Clear();
if($RoleInstallWindowsComponents)
{
# Install any Windows Roles or Features required for the Management Tools role
Install-WindowsComponent -ShortNameForRole "AdminTools" -ADToolsNeeded $RoleADToolsNeeded
}
" was run: "The system cannot find the file specified".
The system cannot find the file specified

You see this error if you left ‘Automatically install Windows Server roles and features required for Exchange Server’ ticked, simply click back and untick this box then try again.

Error 2

Mailbox Role
Failed

Error:
The following error was generated when "$error.Clear();
$wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
$manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "ScriptsTSCrimsonManifest.man");
Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
" was run: "Process execution failed with exit code 15010.".
Process execution failed with exit code 15010.

Download this zip file, it contains a .reg file, run it and merge those files into the registry of the 2012 server. Then run the setup again.

Know Problem Opening Exchange Management Console

(19/06/13) Update from reader Jeremy Krautkramer.

You may find that on Server 2012, (and Windows 8) You can launch the Exchange Management Console, but are unable to expand any of the objects in the left hand pane.

Jeremy fixed it by dropping to command line and running the following three commands;

[box]set __COMPAT_LAYER=RUNASINVOKER
set COMPLUS_Version=v2.0.50727
“C:Program FilesMicrosoftExchange ServerV14BinExchange Management
Console.msc”[/box]

Note: Change the drive letter and path to match your own server.

Why this happens? The Exchange 2010 Exchange Management Console was built with CLR (Common Language Runtime) version 2.0. Windows 2012/8 by default runs its MMC snap ins with CLR version 4.0.

Related Articles, References, Credits, or External Links

Original article written: 14/03/13

Thanks to Jeremy Krautkramer for his feedback.