Exchange 2010 update rollup error 1603

Exchange 2010 Update Rollups and Error 1603

You download and begin to install an Exchange Rollup Update only to find after waiting ages for it do the NGen stuff it fails, and on watching it closely you notice it fails on stopping services.

In the event log you are pointed at a website with information on verbose logging for MSI installations.

But you can forget that – the fix is easy! Start and administrative command prompt and run the rollup update from the command line! It will work first time (as long as the update msi file is actually copied to the local machine, it will typically not run from a copy on a network drive.

I got Error 1603 in my Rollup 3 installation. Do you mean I need to extract the files locally and run the setup in command line?

No, you just need to start the Command Prompt as an administrator. That is right-click the Command Prompt shortcut and choose Run As Administrator. From here you need to just run the MSI download – nothing else to do. If you run the download with /quiet at the end then there really is nothing else to do.

Excellent Thanks you

Simple and stupid (that it’s necessary) and oddly undocumented anywhere in MS support collateral.

Thanks lifting the kilt on this one.

On the old version of this blog, hosted on Blogger, there were lots of other comments that did not get migrated across. These included:

Neil Natic, Sept 2013: “Thanks for this. huge help!”

Thomas Nielsen, Sept 2013: “I know this is a old post, but this solution also solved my issue installing Exchange SP3 Rollup 2 :-)”

Diem Silvan, Aug 2013: “Wow – works fine now : Exchange 2010 SP1 Rollup 8 Thanks a lot. ”

Jerry Locke, May 2013: “Wow, that’s amazingly stupid behavior on the part of the patch installer. Even stupider that it’s not properly documented over two years later.

Thanks for the tip, I can verify it working correctly for Update Rollup 1 on Exchange 2010 SP3 (KB2803727). Strangely, this is the first time I’ve encountered this particular behavior, previous rollups have worked fine”

Frits Luten, May 2013: “The other option is to set the UAC (temporarely) to nothing … after that you can install the Rollup without having to use the command prompt and from any networkshare. Had the same problem with installing Rollup 6 for Exchange 2010 SP2 this morning ….”

Thank you so much. This was exactly my problem. It’s always the simple things, huh? You saved me a ton of time trying to figure things out.

Still works for RU22 on Exchange 2010!

Can’t believe how simple this fix was, thanks!

Works great, but needs to be run with the rollup file on the C drive (even if other drives are local) otherwise it seems to lose the msi it requires to run.

Currently prepping a SBS2011 server for upgrade and trying to install sp3 rollup 30 for Exchange 2010, ran into this issue. Thanks for highlighting this piece of stupidity 🙂

still saving lives! Thanks

Still works on Exchange 2010 SP3 Rollup 32 released March, 2021!

And Microsoft have an article covering this now, and all the other issues, given there were many during the March 2021 emergency patch. The tip is “always run complex admin required programs from an admin cmd prompt” and not double-click them

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Источник

Exchange 2010 update rollup error 1603

Вопрос

I have began upgrading our Exchange servers to Rollup 4 for Exchange 2010 SP2 last week and the first 3 servers all successfully installed it without any problems. However I have hit a problem with my 4th server.

I am receiving the ‘common’ error 1603 in my Application log and I have already ran through many potential fixes to this problem on various posts on this and other forums, but to no avail.

I have tried the following without success:

• Turning off UAC
• Running from elevated CMD prompt
• Running from elevated Powershell command
• Removing and re-adding «Exchange Trusted Subsystem» from the Administrators group
• Re-downloading the RU4 install package to the local disk on the server
• Adding more RAM and CPU resources

I have watched the installation process and it seems to update of the native assembly files and comes to the «Starting Services» process, with which it appears to do fine as I have watched the Services starting within Server Manager while this has been running, but then all of a sudden just begins «Rolling back actions».

The only difference with this server to the others is the fact that a colleague of mine had to recover this server within the last 6 months and ran the Setup /m:RecoverServer command to do so, could this have anything to do with it?

I have installed Exchange 2010 Service Pack 2 on this server since the recovery though.

I am running out of ideas so any help would be greatly appreciated.

Источник

Exchange 2010 update rollup error 1603

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

Trying to update exchange to do a migration. However I keep receiving Error Code 1603 stating that it failed and rolls back.

I also tried to install the update via the elevated command line and received another error that states This patch Package could not be opened Contact the application vendor. I downloaded the file again from Microsoft and receive the same error message.

I checked a few sites that stated to remove any files from the temp folder.

Here is the error message

Log Name: Application
Source: MsiInstaller
Date: 12/5/2018 7:46:36 AM
Event ID: 1024
Task Category: None
Level: Error
Keywords: Classic
User:
Computer:
Description:
Product: Microsoft Exchange Server — Update ‘Update Rollup 24 for Exchange Server 2010 Service Pack 3 (KB4458321) 14.3.419.0’ could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Event Xml:

1024
2
0
0x80000000000000

2434066
Application

Microsoft Exchange Server
Update Rollup 24 for Exchange Server 2010 Service Pack 3 (KB4458321) 14.3.419.0
1603
(NULL)
(NULL)
(NULL)

7B34393334443145412D424534362D343842312D383834372D4631414632304538393243317D207B34384443423844342D364641352D344131452D393330362D3445313330394331343038387D2031363033

Источник

Exchange 2010 update rollup error 1603

Вопрос

I have began upgrading our Exchange servers to Rollup 4 for Exchange 2010 SP2 last week and the first 3 servers all successfully installed it without any problems. However I have hit a problem with my 4th server.

I am receiving the ‘common’ error 1603 in my Application log and I have already ran through many potential fixes to this problem on various posts on this and other forums, but to no avail.

I have tried the following without success:

• Turning off UAC
• Running from elevated CMD prompt
• Running from elevated Powershell command
• Removing and re-adding «Exchange Trusted Subsystem» from the Administrators group
• Re-downloading the RU4 install package to the local disk on the server
• Adding more RAM and CPU resources

I have watched the installation process and it seems to update of the native assembly files and comes to the «Starting Services» process, with which it appears to do fine as I have watched the Services starting within Server Manager while this has been running, but then all of a sudden just begins «Rolling back actions».

The only difference with this server to the others is the fact that a colleague of mine had to recover this server within the last 6 months and ran the Setup /m:RecoverServer command to do so, could this have anything to do with it?

I have installed Exchange 2010 Service Pack 2 on this server since the recovery though.

I am running out of ideas so any help would be greatly appreciated.

Источник

Exchange 2010 update rollup error 1603

Question

I have began upgrading our Exchange servers to Rollup 4 for Exchange 2010 SP2 last week and the first 3 servers all successfully installed it without any problems. However I have hit a problem with my 4th server.

I am receiving the ‘common’ error 1603 in my Application log and I have already ran through many potential fixes to this problem on various posts on this and other forums, but to no avail.

I have tried the following without success:

• Turning off UAC
• Running from elevated CMD prompt
• Running from elevated Powershell command
• Removing and re-adding «Exchange Trusted Subsystem» from the Administrators group
• Re-downloading the RU4 install package to the local disk on the server
• Adding more RAM and CPU resources

I have watched the installation process and it seems to update of the native assembly files and comes to the «Starting Services» process, with which it appears to do fine as I have watched the Services starting within Server Manager while this has been running, but then all of a sudden just begins «Rolling back actions».

The only difference with this server to the others is the fact that a colleague of mine had to recover this server within the last 6 months and ran the Setup /m:RecoverServer command to do so, could this have anything to do with it?

I have installed Exchange 2010 Service Pack 2 on this server since the recovery though.

I am running out of ideas so any help would be greatly appreciated.

Источник

Hello…

I recently inherited a physical SBS2011 server with Exchange 2010 SP1 RU8 installed.  SP1 RU7v2 is the only other RU installed.  When attempting to upgrade to SP3 the pre-install checks all pass but when it gets to the removal of Exchange part of the install the following error is thrown and the install fails.

Unable to remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘Service » () could not be stopped.  Verify that you have the correct permissions to stop system services.’.

After fixing the services and rebooting the server EmailExchange connectivity is restored.  I get the same error if I try and install SP2 or SP3, and if I try and uninstall the currently installed SP1 RU’s.  My account is a member of the Domain Admins, Enterprise Admins, Schema Admins, and Organization Management groups.  I can fully interact with all MS Exchange services as well as IIS Admin Service, Remote Registry, WMI, and WWW services.  I’ve stopped the Windows SBS Manager service as well as disabled UAC and my AV prior to install and the issue persists. 

I verified the RangeUpper value on my Schema is correct (14734), but attempted to run Setup.com /PrepareAD anyway (from an admin CMD).  The command output shows the first two lines («Welcome to Microsoft Exchange blah blah blah», and then «Preparing Exchange Setup») but then just goes back to the cursor waiting for the next command and no error or changes made.  Same happens when I tried to run ServiceControl.ps1, first 2 or so lines of the command output are shown then back to the cursor with no actual error or changes made.  Powershell Execution Policy is set to Unrestricted.

As near as I can tell what ever 4934d1ea-be46-48b1-8847-f1af20e892c1 represents iswas installed at some point and then removed, I can find that same GUID in the registry (HKLMSOFTWAREMicrosoftWindowsCurrentVersionInstallerFolders) and the WindowsInstaller folder.  I suspect it is gone though because the error references that GUID, then the installer fails because it is unable to stop service (), which isn’t anything.  Mail is currently flowing to Outlook 2010 and below with no issues.  I don’t want to start ripping things out and mess up mailflow but I’m about out of ideas.  Any help you can provide would be great, let me know if I can provide any more info. 

Event 1024 MSiInstaller — Error code 1603

Update: Microsoft is asking customers who are having this issue to open a support case with Microsoft Technical Support.  They see random support calls related to this going back to Exchange 2007, but want to reproduce the issue with customers currently seeing this issue with Exchange 2010 SP2 UR4. 

See

http://support.microsoft.com/kb/319726 for MTS phone numbers in your area. 

I had an interesting problem installing Exchange 2010 SP2 Update Rollup 4 (UR4) on servers that have never had issues installing updates before.  When I tried to install SP2 UR4 on the Edge Transport or typical installation servers it would rollback the installation and log the following error in the application log:

Product: Microsoft Exchange Server — Update ‘Update Rollup 4 for Exchange Server 2010 Service Pack 2 (KB2706690) 14.2.318.2’ could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages.

Normally this issue us fixed by installing the Update Rollup from an elevated CMD prompt (see http://blog.c7solutions.com/2011/03/exchange-2010-update-rollups-and-error.html), but this time it still wasn’t working.

I enabled MSI Installer logging as per http://go.microsoft.com/fwlink/?LinkId=23127 and dived into the setup logs.  I found the following error being logged in the ServiceControl.log:

[19:51:28] [Error]
System.Management.Automation.ParseException: At C:Program FilesMicrosoftExchange
ServerV14ScriptsManageScheduledTask.ps1:462 char:5

+                
return $success

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

Control
cannot leave a finally block.

 

at
System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object
input, Hashtable errorResults, Boolean enumerate)

at System.Management.Automation.PipelineOps.InvokePipeline(Object input,
Boolean ignoreInput, CommandParameterInternal[][] pipeElements,
CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections,
FunctionContext funcContext)

at
System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame
frame)

at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)

at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)

I examined the ManagedScheduleTask.ps1 script which apparently disables the ‘Database One Copy Alert’ scheduled task, but could not determine what the error is.  I also ran the script from EMS, which returned the same error.  Nothing showed up on the Interwebs other than a few references to PowerShell 3.0, which is not installed on these servers.

I finally resolved it by renaming the ManageScheduledTask.ps1 script to ManageScheduledTask.old and creating a new empty ManageScheduledTask.ps1 script.  The script must exist and return a non-error code when executed for the UR4 installer to work.  I renamed the script back when the installer finished.

This may be an esoteric problem, but I wanted to document it in case anyone else has the same problem.  If this does happen in your environment, please leave a comment below.  Thanks.

Follow Up (10/12/2012)

I’ve found several times so far that this happens to servers that have the Windows Management Framework 3.0 installed.  The RTW version is found at http://www.microsoft.com/en-us/download/details.aspx?id=29939.  The Windows Management Framework 3.0 includes PowerShell 3.0, which is not compatible with Exchange 2010 and explains why the ManageScheduledTask.ps1 script doesn’t run properly.

Check the installed updates on the problem server for the Windows Management Framework 3.0 and try uninstalling it to see if it solves the problem.  The Framework allows you to manage servers remotely from the Windows Server 2012 Server Management Console.

Microsoft re-released the following updates to fix a code-signing issue that may affect some customers in the near future:

• Update Rollup 4-v2 for Exchange Server 2010 Service Pack 2 (KB2756485)
• Update Rollup 7-v2 for Exchange Server 2010 Service Pack 1 (KB2756496)
• Update Rollup 8-v2 for Exchange Server 2007 Service Pack 3 (KB2756497)

See the EHLO Blog article, Re-released Exchange 2010 and Exchange 2007 update rollups for more information.  The re-release of the these update rollups has no bearing on the script issue covered in this article, but I do recommend installing the re-released updates on your Exchange servers to prevent future code-signing issues.

Exchange Server 2013 Error Code 1603