locked
Installing CU11 Failed with Error 1603 - Corrupt Installation RRS feed

  • Question

  • Hi,

    I crashed an Exchange 2013 Installation on Server 2012 R2 while installing the CU11. It stopped during step 3 with a fatal error, code 1603. I can repeat this error when trying to install it again. The Services are disabled now, and I'm unsure about the versions of the binaries.

    As far as I could Google for it, the 1603 is a generic MSI Installation error code. I am not able to get more details for it. The last lines of the Setup log from the installer are:

    [01.11.2016 21:41:13.0257] [1] Processing component 'FrontendTransport MidFileCopy' (Vorbereiten von Dateien für die Clientzugriffsrolle: Front-End-Transport-Dienst.).
    [01.11.2016 21:41:13.0258] [1] Processing component 'Client Access MidFileCopy' (Vorbereiten von Dateien für die Postfachrolle: Installation des Clientzugriffsdiensts.).
    [01.11.2016 21:41:13.0258] [1] Processing component 'Unified Messaging MidFileCopy' (Vorbereiten von Dateien für die Postfachrolle: Unified Messaging-Dienst.).
    [01.11.2016 21:41:13.0258] [1] Processing component 'Mailbox MidFileCopy' (Vorbereiten von Dateien für die Postfachrolle: Installation des Postfachdiensts.).
    [01.11.2016 21:41:13.0258] [1] Processing component 'Admin Tools MidFileCopy' (Die Dateien für die Installation der Exchange-Verwaltungstools werden vorbereitet.).
    [01.11.2016 21:41:13.0258] [1] Processing component 'CAFE MidFileCopy' (Vorbereiten von Dateien für die Clientzugriffsrolle: Installation des Clientzugriffs-Front-End-Diensts.).
    [01.11.2016 21:41:13.0258] [1] Finished executing component tasks.
    [01.11.2016 21:41:13.0261] [1] Ending processing Start-MidFileCopy
    [01.11.2016 21:41:13.0265] [0] **************
    [01.11.2016 21:41:13.0265] [0] Setup will run the task 'install-msipackage'
    [01.11.2016 21:41:13.0265] [1] Setup launched task 'install-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -targetdirectory 'C:\Program Files\Microsoft\Exchange Server\V15' -features 'Bridgehead','FrontendTransport','ClientAccess','UnifiedMessaging','Mailbox','AdminTools','Cafe' -packagepath 'E:\_no_backup_\CORETO\Exchange2013-CU11\exchangeserver.msi' -updatesdir $null -PropertyValues 'DISABLEERRORREPORTING=0 PRODUCTLANGUAGELCID=1033 DEFAULTLANGUAGENAME=ENU DEFAULTLANGUAGELCID=1033 INSTALLCOMMENT="Installierte Sprache für dieses Produkt: English (United States)"''  
    [01.11.2016 21:41:13.0269] [1] Die Active Directory-Sitzungseinstellungen für 'Install-MsiPackage' lauten: Vollständige Gesamtstruktur anzeigen: 'True', Konfigurationsdomänencontroller: 'SERVER2012.internaldomain.local', Bevorzugter globaler Katalog: 'SERVER2012.internaldomain.local', Bevorzugte Domänencontroller: '{ SERVER2012.internaldomain.local }'
    [01.11.2016 21:41:13.0270] [1] User specified parameters:  -UpdatesDir:$null -PackagePath:'E:\_no_backup_\CORETO\Exchange2013-CU11\exchangeserver.msi' -TargetDirectory:'C:\Program Files\Microsoft\Exchange Server\V15' -PropertyValues:'DISABLEERRORREPORTING=0 PRODUCTLANGUAGELCID=1033 DEFAULTLANGUAGENAME=ENU DEFAULTLANGUAGELCID=1033 INSTALLCOMMENT="Installierte Sprache für dieses Produkt: English (United States)"' -Features:'Bridgehead','FrontendTransport','ClientAccess','UnifiedMessaging','Mailbox','AdminTools','Cafe' -LogFile:'C:\ExchangeSetupLogs\ExchangeSetup.msilog'
    [01.11.2016 21:41:13.0270] [1] Beginning processing install-msipackage
    [01.11.2016 21:41:13.0697] [1] ProductCode is '4934d1ea-be46-48b1-8847-f1af20e892c1'.
    [01.11.2016 21:41:13.0705] [1] PackagePath was set to 'E:\_no_backup_\CORETO\Exchange2013-CU11\exchangeserver.msi'; changing to full path 'E:\_no_backup_\CORETO\Exchange2013-CU11\exchangeserver.msi'.
    [01.11.2016 21:41:13.0748] [1] ProductCode is '4934d1ea-be46-48b1-8847-f1af20e892c1'.
    [01.11.2016 21:41:13.0754] [1] Installing MSI package 'E:\_no_backup_\CORETO\Exchange2013-CU11\exchangeserver.msi'.
    [01.11.2016 21:41:13.0769] [1] No updates directory was specified for the msi installation.
    [01.11.2016 21:41:13.0769] [1] Installing a new product. Package: E:\_no_backup_\CORETO\Exchange2013-CU11\exchangeserver.msi. Property values: DISABLEERRORREPORTING=0 PRODUCTLANGUAGELCID=1033 DEFAULTLANGUAGENAME=ENU DEFAULTLANGUAGELCID=1033 INSTALLCOMMENT="Installierte Sprache für dieses Produkt: English (United States)" REBOOT=ReallySuppress TARGETDIR="C:\Program Files\Microsoft\Exchange Server\V15" ADDLOCAL=Bridgehead,FrontendTransport,ClientAccess,UnifiedMessaging,Mailbox,AdminTools,Cafe,AdminToolsNonGateway
    [01.11.2016 21:44:37.0118] [1] [ERROR] Installing product E:\_no_backup_\CORETO\Exchange2013-CU11\exchangeserver.msi failed. Schwerwiegender Fehler bei der Installation. Error code is 1603.
    [01.11.2016 21:44:37.0119] [1] [ERROR] Schwerwiegender Fehler bei der Installation
    [01.11.2016 21:44:37.0141] [1] [ERROR] Installing product E:\_no_backup_\CORETO\Exchange2013-CU11\exchangeserver.msi failed. Schwerwiegender Fehler bei der Installation. Error code is 1603.
    [01.11.2016 21:44:37.0141] [1] [ERROR] Schwerwiegender Fehler bei der Installation
    [01.11.2016 21:44:37.0144] [1] [ERROR] Installing product E:\_no_backup_\CORETO\Exchange2013-CU11\exchangeserver.msi failed. Schwerwiegender Fehler bei der Installation. Error code is 1603.
    [01.11.2016 21:44:37.0144] [1] [ERROR] Schwerwiegender Fehler bei der Installation
    [01.11.2016 21:44:37.0149] [1] Ending processing install-msipackage
    [01.11.2016 21:46:51.0822] [0] CurrentResult setupbase.maincore:396: 0
    [01.11.2016 21:46:51.0824] [0] End of Setup
    [01.11.2016 21:46:51.0824] [0] **********************************************

    the ExchangeSetup.msilog has not more than a begin and end time stamp.

    How can I get an idea what's going wrong?

    Thanks,

    Matschek

    Tuesday, January 12, 2016 12:09 AM

Answers

  • If you have a good backup, recovering the entire server image would likely work.

    If not, and the server is in AD in the Configuration naming context:

    CN=Configuration,... > CN=Services > CN=Microsoft Exchange > CN=<your org> > CN=Administrative Groups > CN=Exchange Administrative Group (FXDIBOHF23SPDLT) > CN=Servers

    then what you will want to do is flatten the computer, build a new one with same operating system and patch level, prepare the server for Exchange, install your certificate, download Exchange 2013 CU2, unpack it, and then run:

    Setup.exe /mode:RecoverServer /IAcceptExchangeServerLicenseTerms

    This will reinstall Exchange pretty much as it was before.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    • Proposed as answer by David Wang_ Thursday, January 14, 2016 1:03 AM
    • Marked as answer by David Wang_ Monday, January 25, 2016 9:07 AM
    Wednesday, January 13, 2016 5:53 PM

All replies

  • Have you tried an uninstall?  Is the server present in Active Directory?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Tuesday, January 12, 2016 12:14 AM
  • There's no uninstall option in the program uninstall list, or which type of uninstall do you mean?

    Yes, the server is an DC running an AD and I just checked the presence in the OU domain controlles.

    The "old" Exchange 2013 instance went fine for the last two years with the patch level available during initial installation (I think it was CU5).

    Thanks, Matschek

    Tuesday, January 12, 2016 12:24 AM
  • Setup.exe /Mode:Uninstall /IAcceptExchangeServerLicenseTerms

    What about if you enter Get-ExchangeServer?  That's where it matters.

    Are you trying to reinstall an existing server on a new platform with the same name? That is definitely not clear from your original post. In that case enter:

    Setup.exe /Mode:RecoverServer /IAcceptExchangeServerLicenseTerms

    Reinstall the same CU that was installed before, then update it if you want to afterward.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Tuesday, January 12, 2016 1:14 AM
  • Hi,

    Please review ExchangeSetupLog file to find more error messages related to Exchange setup.

    Please make sure that all antivirus and anti-spam are temporarily disabled.

    Clear the data in the "%SystemDrive%\Windows\TEMP"folder.

    Then try to download and re-install the update rollup. (do not download from third party sites)

    https://technet.microsoft.com/en-us/library/bb125254%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

    Regards,

    David 





    • Edited by David Wang_ Tuesday, January 12, 2016 8:06 AM
    Tuesday, January 12, 2016 6:37 AM
  • Hi David,

    I posted the relevant part of the ExchangeSetupLog in the first post. If you think it may help, I can share the whole log and/or the other files beeing generated in the log folder. As far as I can see all entries above the final lines seem to be OK.

    ESET Antivirus+Antispam are disabled. I cleared the Windows Temp Folder before the second try. Only an "XCCache" folder remains where I have no access by default ACL.

    A few hours ago I downloaded the 1,6GB Setup again from MS and did a file compare, but it was identically with the one I donloaded before. Nevertheless I gave it a try with the new download file, but it did not change the error.

    BTW, your link leads to Exchange 2016

    Thanks,

    Matschek

    Tuesday, January 12, 2016 7:26 AM
  • Hi Ed,

    Get-ExchangeServer is not a known commandlet anymore...

    Sorry to be unclear: I tried to upgrade an existing and working instance of Exchange CU2 (I looked up patch level in the old archived setup folder) with CU11 and went into the error.

    Now I try to fix it on the same server. There's no second server in the network.

    If I try to uninstall and then reinstall with RevocerServer option, how much of the Exchange settings will be lost? Is this a non-destructive way? Never went through this option before...

    Thanks,

    Matthias

    Tuesday, January 12, 2016 7:31 AM
  • Hi Ed,

    gave it a try:

    A Setup /mode:uninstall tells me that no Exchange Server ist installed and therefore none can be uninstalled.

    A Setup/mode:recoverserver runs into the same problem like the upgrade setup path (fatal error 1603).

    I'm stuck.

    It might be an error with the MSI installer engine?

    KR,

    Matschek

    Tuesday, January 12, 2016 7:39 AM
  • It's not?

    https://technet.microsoft.com/en-us/library/bb123873%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Tuesday, January 12, 2016 8:38 AM
  • I don't know what's happened to your server.  I recommend you open a ticket with Microsoft Support.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Tuesday, January 12, 2016 8:38 AM
  • I was able to extract the MSI call from the setup log. After lauching the msiexev with a logfile parameter, I got more infos from the install process.
    This sequence seems to be the first error:

    Action start 11:18:11: InstallExecute.
    CAQuietExec:  
    CAQuietExec:  Error 0x80070216: Command line returned an error.
    CAQuietExec:  Error 0x80070216: CAQuietExec Failed
    CustomAction RegisterPerfmonManifest returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    01/12/2016 11:19:18.668 [1920]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
    
    01/12/2016 11:19:18.684 [1920]: Detailed info about C:\Windows\assembly\tmp\PGZEDBRE\Microsoft.Exchange.Data.Common.dll
    
    01/12/2016 11:19:18.684 [1920]: 	File attributes: 00000080
    
    01/12/2016 11:19:18.715 [1920]: 	Restart Manager Info: 1 entries
    
    01/12/2016 11:19:18.715 [1920]: 		App[0]: (1920) Windows Installer (msiserver), type = 3 
    
    01/12/2016 11:19:18.715 [1920]: 	Security info:
    
    01/12/2016 11:19:18.715 [1920]: 		Owner: S-1-5-18
    
    01/12/2016 11:19:18.715 [1920]: 		Group: S-1-5-18
    
    01/12/2016 11:19:18.715 [1920]: 		DACL information: 4 entries:
    
    01/12/2016 11:19:18.715 [1920]: 		ACE[0]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-18
    
    01/12/2016 11:19:18.715 [1920]: 		ACE[1]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-32-544
    
    01/12/2016 11:19:18.715 [1920]: 		ACE[2]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-5-32-545
    
    01/12/2016 11:19:18.715 [1920]: 		ACE[3]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-15-2-1
    
    01/12/2016 11:19:18.715 [1920]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
    
    01/12/2016 11:19:18.715 [1920]: Detailed info about C:\Windows\assembly\tmp\IWT055UW\policy.8.0.Microsoft.Exchange.Data.Common.dll
    
    01/12/2016 11:19:18.715 [1920]: 	File attributes: 00000080
    
    01/12/2016 11:19:18.752 [1920]: 	Restart Manager Info: 1 entries
    
    01/12/2016 11:19:18.752 [1920]: 		App[0]: (1920) Windows Installer (msiserver), type = 3 
    
    01/12/2016 11:19:18.752 [1920]: 	Security info:
    
    01/12/2016 11:19:18.752 [1920]: 		Owner: S-1-5-18
    
    01/12/2016 11:19:18.752 [1920]: 		Group: S-1-5-18
    
    01/12/2016 11:19:18.752 [1920]: 		DACL information: 4 entries:
    
    01/12/2016 11:19:18.752 [1920]: 		ACE[0]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-18
    
    01/12/2016 11:19:18.752 [1920]: 		ACE[1]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-32-544
    
    01/12/2016 11:19:18.752 [1920]: 		ACE[2]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-5-32-545
    
    01/12/2016 11:19:18.752 [1920]: 		ACE[3]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-15-2-1
    
    01/12/2016 11:19:18.752 [1920]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
    
    01/12/2016 11:19:18.752 [1920]: Detailed info about C:\Windows\assembly\tmp\Z6MAQ2RD\policy.8.1.Microsoft.Exchange.Data.Common.dll
    
    01/12/2016 11:19:18.752 [1920]: 	File attributes: 00000080
    
    01/12/2016 11:19:18.783 [1920]: 	Restart Manager Info: 1 entries
    
    01/12/2016 11:19:18.783 [1920]: 		App[0]: (1920) Windows Installer (msiserver), type = 3 
    
    01/12/2016 11:19:18.783 [1920]: 	Security info:

    Then several thousand lines with blocks similar to this "Assembly Install, Detailed info etc" follow, finally ending with:

    01/12/2016 11:19:25.223 [1920]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
    
    01/12/2016 11:19:25.223 [1920]: Detailed info about C:\Windows\assembly\tmp\AHZROGZM\microsoft.ceres.searchcore.seeding.dll
    
    01/12/2016 11:19:25.223 [1920]: 	File attributes: 00000080
    
    01/12/2016 11:19:25.254 [1920]: 	Restart Manager Info: 1 entries
    
    01/12/2016 11:19:25.254 [1920]: 		App[0]: (1920) Windows Installer (msiserver), type = 3 
    
    01/12/2016 11:19:25.254 [1920]: 	Security info:
    
    01/12/2016 11:19:25.254 [1920]: 		Owner: S-1-5-18
    
    01/12/2016 11:19:25.254 [1920]: 		Group: S-1-5-18
    
    01/12/2016 11:19:25.254 [1920]: 		DACL information: 4 entries:
    
    01/12/2016 11:19:25.254 [1920]: 		ACE[0]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-18
    
    01/12/2016 11:19:25.254 [1920]: 		ACE[1]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-32-544
    
    01/12/2016 11:19:25.254 [1920]: 		ACE[2]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-5-32-545
    
    01/12/2016 11:19:25.254 [1920]: 		ACE[3]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-15-2-1
    
    01/12/2016 11:19:25.254 [1920]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
    
    01/12/2016 11:19:25.254 [1920]: Detailed info about C:\Windows\assembly\tmp\X4CL7DEM\Microsoft.Ceres.Diagnostics.dll
    
    01/12/2016 11:19:25.254 [1920]: 	File attributes: 00000080
    
    01/12/2016 11:19:25.286 [1920]: 	Restart Manager Info: 1 entries
    
    01/12/2016 11:19:25.286 [1920]: 		App[0]: (1920) Windows Installer (msiserver), type = 3 
    
    01/12/2016 11:19:25.286 [1920]: 	Security info:
    
    01/12/2016 11:19:25.286 [1920]: 		Owner: S-1-5-18
    
    01/12/2016 11:19:25.286 [1920]: 		Group: S-1-5-18
    
    01/12/2016 11:19:25.286 [1920]: 		DACL information: 4 entries:
    
    01/12/2016 11:19:25.286 [1920]: 		ACE[0]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-18
    
    01/12/2016 11:19:25.286 [1920]: 		ACE[1]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-32-544
    
    01/12/2016 11:19:25.286 [1920]: 		ACE[2]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-5-32-545
    
    01/12/2016 11:19:25.286 [1920]: 		ACE[3]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-15-2-1
    
    Action ended 11:19:25: InstallExecute. Return value 3.
    
    
    
    CAQuietExec:  
    CAQuietExec:  Warnung: Von "C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\FipExEuPerfCtr.man" aus kann kein passender Anbieter "{55d388b9-85e1-47f4-a311-451dbe30d8b7}" im Systemrepository gefunden werden. Fehlercode: 2.
    

    Tuesday, January 12, 2016 10:39 AM
  • Just to clarify, are you trying to install a new Exchange 2013 CU11 server in your forest or trying to update an existing server with CU11?  If you're trying to install a new server, do you have existing servers?

    From your original post I assumed you were trying to update an existing CU2 server with CU11:

    "I tried to upgrade an existing and working instance of Exchange CU2"


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Tuesday, January 12, 2016 11:28 PM
  • Hi Ed,

    You are right. We're talking about an existing CU2 beeing upgraded to CU11.

    It is the same physical mashine and the same Exchange instance which I am trying to get working again after the error during the CU2->CU11 update attempt.

    There's no second server in the network."

    Meanwhile I opened a ticket at Microsoft Support, but the Exchange team is telling me that the error code is MSI installer related, and the platform Team (responsible for MSI) is telling me that the problem is Exchange related. Currently both teams have no idea what happened and what can be done next. They're still investigating the issue, I'm wating for a call.

    I worry that we have to do a complete server restore from an older state if the Exchange does not come up again within the next hours.

    Thanks,

    Matschek

    Wednesday, January 13, 2016 9:13 AM
  • If you have a good backup, recovering the entire server image would likely work.

    If not, and the server is in AD in the Configuration naming context:

    CN=Configuration,... > CN=Services > CN=Microsoft Exchange > CN=<your org> > CN=Administrative Groups > CN=Exchange Administrative Group (FXDIBOHF23SPDLT) > CN=Servers

    then what you will want to do is flatten the computer, build a new one with same operating system and patch level, prepare the server for Exchange, install your certificate, download Exchange 2013 CU2, unpack it, and then run:

    Setup.exe /mode:RecoverServer /IAcceptExchangeServerLicenseTerms

    This will reinstall Exchange pretty much as it was before.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    • Proposed as answer by David Wang_ Thursday, January 14, 2016 1:03 AM
    • Marked as answer by David Wang_ Monday, January 25, 2016 9:07 AM
    Wednesday, January 13, 2016 5:53 PM
  • Did you ever receive a fix for this?
    Monday, February 15, 2016 9:45 PM
  • Hi Michael,

    no, it was impossible to solve this.

    Two Microsoft guys tried to fix this after I opened a ticket for it.

    The Exchange Team did a long diagnostic and came to the conclusion that the error is based on a MSI error and not an Exchange specific thing.

    The platform team (responsible for MSI) did a short analyze (they just installed another small MSI package and said “works, so MSI engine is OK”) and bounced back to the Exchange team.

    After several more hours MS told me they will not able so solve this within a few days. They had no idea what happened to the system. They couldn’t find any related report. The only theoretical option would have been to open a bug report and give this for a deep analyze and have some weeks passing by, with open end.

    The only way here was to give up the old system, do a partial restore, migrate to a new Exchange and finally uninstall the old one.

    I hope you didn’t run into exactly the same error?

    KR,

    Matthias

    Tuesday, February 16, 2016 10:30 AM
  • Dear All,

    We had the same issue and received "fatal error 1603" while installing Exchange 2016 cu11 .

    Took below steps which resolved the issue and installation was completed w/o error.

    1- make sure that visual C++ 2013 is installed on Exchange server

    2- execute below command on powershell with run as administrator privilege on DC :

    ./setup /prepareAD /organizationname:"" USE YOUR OWN ORGANIZATION NAME"  /IAcceptExchangeServerLicenseTerms 

    3- execute exchange cu11 setup command 

    hope that above commands help other professionals.

    • Proposed as answer by Ali Khoshbin Saturday, February 16, 2019 7:35 AM
    Saturday, February 16, 2019 7:35 AM