locked
Exchange 2007 Update Rollup 1 for SP2 installation failures RRS feed

  • Question

  • This was released last night (http://support.microsoft.com/?kbid=971534). I have tried it on two x64 Windows Server 2008 SP2 machines which only have the Management Tools installed. In both cases installation failed and rolled back.

    Here is where it stops in patch-config.log.

    Error patching config file: Could not find a part of the path 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\PopImap\Microsoft.Exchange.Imap4.exe.config'.

    Then the log stops.

    Obviously these machines don't have a ClientAccess folder or IMAP4 installed, but this has not stopped Update Rollups before.

    I'm not willing to try it on the Exchange Servers themselves.
    Friday, November 20, 2009 9:01 AM

Answers

  • Ananth,

    I bumped up the memory for my virtual server and it ran through with no issues.  This is the first time that I've had to bump up the memory to complete an update rollup or service pack in my virtual test environment.  My test exchange servers have been running since the original version of Exchange Server 2007 with all update rollups without any issues.  Thank you for pointing me in the right direction.
    Tuesday, November 24, 2009 9:44 PM

All replies

  • since it is brand new

    I would say better to standby till you get some feedback from other people. In between it is always best and recommended to install it in Lab environment test it and then move on to production environment.

    Lets wait till MS people 's comment on this.
    Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
    • Proposed as answer by zhangxiaojian Wednesday, December 16, 2009 1:01 PM
    Friday, November 20, 2009 9:58 AM
  • Some of us don't have the money for a lab environment :-) Hence trying it on a management console.

    I do intend to wait now.
    Friday, November 20, 2009 10:17 AM
  • The error message indicates there was an exception that was caught and logged.
    Since no CAS role installed on your machine, this is expected.
    So it seems something else is causing the problem.

    Could you try to install with command line: "msiexec /p yourRU.msp /lxv* ru.log" ?
    And you can search for last error happened before rollback in ru.log.
    Or you can share the log with us. So we would find out what might be wrong.
    Friday, November 20, 2009 10:34 AM
  • The verbose log ends:

    MSI (c) (38:6C) [11:31:33:732]: Product: Microsoft Exchange Server - Update 'Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB971534) 8.2.217.3' could not be installed. Error code 1603. Additional information is available in the log file C:\Patch\ru2.log.

    MSI (c) (38:6C) [11:31:33:732]: Windows Installer installed an update. Product Name: Microsoft Exchange Server. Product Version: 8.2.176.2. Product Language: 1033. Update Name: Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB971534) 8.2.217.3. Installation success or error status: 1603.

    MSI (c) (38:6C) [11:31:33:732]: Note: 1: 1729
    MSI (c) (38:6C) [11:31:33:732]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (38:6C) [11:31:33:747]: Transforming table Error.

    MSI (c) (38:6C) [11:31:33:747]: Transforming table Error.

    MSI (c) (38:6C) [11:31:33:747]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (38:6C) [11:31:33:747]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (38:6C) [11:31:33:763]: Transforming table Error.

    MSI (c) (38:6C) [11:31:33:763]: Transforming table Error.

    MSI (c) (38:6C) [11:31:33:763]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (38:6C) [11:31:33:763]: Product: Microsoft Exchange Server -- Configuration failed.

    MSI (c) (38:6C) [11:31:33:763]: Windows Installer reconfigured the product. Product Name: Microsoft Exchange Server. Product Version: 8.2.176.2. Product Language: 1033. Reconfiguration success or error status: 1603.

    MSI (c) (38:6C) [11:31:33:763]: Attempting to delete file C:\Users\ND28D~1.FLA\AppData\Local\Temp\2\319ea99b.msp
    MSI (c) (38:6C) [11:31:33:763]: Unable to delete the file. LastError = 32
    MSI (c) (38:6C) [11:31:33:779]: Grabbed execution mutex.
    MSI (c) (38:6C) [11:31:33:779]: Cleaning up uninstalled install packages, if any exist
    MSI (c) (38:6C) [11:31:33:779]: Attempting to delete file C:\Users\ND28D~1.FLA\AppData\Local\Temp\2\319ea99b.msp
    MSI (c) (38:6C) [11:31:33:779]: MainEngineThread is returning 1603
    === Verbose logging stopped: 20/11/2009  11:31:33 ===

    Just before it starts rolling back there is:

    MSI (s) (14:60) [11:06:20:174]: Note: 1: 2205 2:  3: BindImage
    MSI (s) (14:60) [11:06:20:174]: Note: 1: 2205 2:  3: ProgId
    MSI (s) (14:60) [11:06:20:174]: Note: 1: 2205 2:  3: PublishComponent
    MSI (s) (14:60) [11:06:20:174]: Note: 1: 2205 2:  3: SelfReg
    MSI (s) (14:60) [11:06:20:174]: Note: 1: 2205 2:  3: Extension
    MSI (s) (14:60) [11:06:20:174]: Note: 1: 2205 2:  3: Font
    MSI (s) (14:60) [11:06:20:174]: Note: 1: 2205 2:  3: Class
    MSI (s) (14:60) [11:06:34:214]: Failed to generate hash for file 'C:\Program Files\Microsoft\Exchange Server\Scripts\CustomPatchInstallerActions.ps1.template'. Error: 0x2

    The whole log is enormous, of course.

    Friday, November 20, 2009 11:46 AM
  • I have found the cause. The update rollup will not install if you have PowerShell 2.0 installed (I have the RTW version from KB968930). Revert to PowerShell 1.0 and it works.

    It was stated in the Exchange Team blog that SP2 supported PowerShell 2.0. It looks like the rollup patch installer doesn't.
    Friday, November 20, 2009 3:32 PM
  • Yea...!!! Thanks for sharing Neil
    Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
    Friday, November 20, 2009 3:36 PM
  • Thanks for sharing Neil. We will look into this further.
    Friday, November 20, 2009 10:13 PM
  • I'm also having installation issues within my test environment with the following error: The user who's currently logged on doesn't have sufficient permissions to install this package. You need at least Exchange Server Administrator permissions on the current computer to complete this task.

    My permissions on the exchang server has not changed and I used the same credentials to install/upgrade to SP2 for EX2007.  I am not running PS v2.0, but still remain on 1.0 (KB926139)

    Monday, November 23, 2009 7:59 PM
  • Blacktoe,

    Can you send us the log file?
    You need to try the install with command line: "msiexec /p yourRU.msp /lxv* ru.log" and you can search for last error happened before rollback in ru.log.

    The other thing to try would be to launch Exchange Management Shell and run the command "Get-ExchangeServer". How long does this take in your test environment?

    Thanks,

    -Ananth

    Monday, November 23, 2009 8:16 PM
  • It takes 3 seconds to execute the "Get-ExchangeServer" line within the EMS.  I then ran the installation from the command line per your request and it failed again and I do have the ru.log file however, it's pretty detailed for me to upload it here.  Would you like me to upload here anyway?  Or send you the log in an email?  If email then I'll need an email address.  Thank you for your help.
    Tuesday, November 24, 2009 1:08 PM
  • Blacktoe,

    Open your log file and search for "expatchca". Copy from that line till the beginning of "Property(C)" and post it here. Thanks.

    By the way, how long it took to start the EMS roughly? Did you leave EMS running while trying to install from the command line?

    Tuesday, November 24, 2009 7:16 PM
  • It takes roughly 80 seconds to launch the EMS within my test environment.  The test environment is running on my laptop so it is a bit slower.  I did not leave EMS running while installing Update Rollup 1 from the GUI or command prompt.  Here is the information from my log:

    1: ExPatchCa: GetProperty: Get property: RunCommandCmdLine (RunCommandCmdLine): C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe "add-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.Admin
    $exitcode=0
    $exserver=Get-ExchangeServer ([Environment]::MachineName) -ErrorVariable exerr 2> $null
    if($exerr.count -gt 0)
    {
    if (($exerr[0].Exception -eq $null)-or($exerr[0].Exception.InnerException -eq $null)-or($exerr[0].Exception.InnerException.ErrorCode -eq 0))
    {
    $exitcode=5
    }
    else
    {
    $exitcode=$exerr[0].Exception.InnerException.ErrorCode
    }
    }
    remove-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.Admin
    Exit ($exitcode)". (ec: 0x0)
    MSI (c) (00!C0) [07:59:27:178]: Closing MSIHANDLE (2) of type 790531 for thread 3520
    MSI (c) (00!C0) [07:59:27:178]: Creating MSIHANDLE (3) of type 790531 for thread 3520
    1: ExPatchCa: GetProperty: Failed to get property: RunCommandTimeout (RunCommandTimeout): NULL. (ec: 0xd)
    MSI (c) (00!C0) [07:59:27:178]: Closing MSIHANDLE (3) of type 790531 for thread 3520
    MSI (c) (00!C0) [08:00:27:177]: Creating MSIHANDLE (4) of type 790531 for thread 3520
    1: ExPatchCa: RunCommand: ExecCommand: exit code: 0x5b4. timeout: 60000 ms(default). (ec: 0x0)
    MSI (c) (00!C0) [08:00:27:177]: Closing MSIHANDLE (4) of type 790531 for thread 3520
    MSI (c) (00!C0) [08:00:27:177]: PROPERTY CHANGE: Adding RunCommandResult property. Its value is '1460'.
    MSI (c) (00!C0) [08:00:27:177]: Creating MSIHANDLE (5) of type 790531 for thread 3520
    1: ExPatchCa: SetProperty: Set property: RunCommandResult: 1460. (ec: 0x0)
    MSI (c) (00!C0) [08:00:27:177]: Closing MSIHANDLE (5) of type 790531 for thread 3520
    MSI (c) (00:20) [08:00:27:192]: Closing MSIHANDLE (1) of type 790542 for thread 2744
    Action ended 8:00:27: CA_PATCH_OWA_PERMISSION. Return value 1.
    MSI (c) (00:B8) [08:00:27:192]: Doing action: CA_PATCH_OWA_PERMISSION_ERROR
    Action 8:00:27: CA_PATCH_OWA_PERMISSION_ERROR.
    Action start 8:00:27: CA_PATCH_OWA_PERMISSION_ERROR.
    MSI (c) (00:B8) [08:00:27:208]: Transforming table CustomAction.

    MSI (c) (00:B8) [08:00:27:208]: Transforming table CustomAction.

    MSI (c) (00:B8) [08:00:27:208]: Note: 1: 2262 2: CustomAction 3: -2147287038
    MSI (c) (00:B8) [08:00:27:208]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CA_PATCH_OWA_PERMISSION_ERROR'
    MSI (c) (00:B8) [08:00:27:224]: Transforming table CustomAction.

    MSI (c) (00:B8) [08:00:27:224]: Transforming table CustomAction.

    MSI (c) (00:B8) [08:00:27:224]: Note: 1: 2262 2: CustomAction 3: -2147287038
    MSI (c) (00:7C) [08:00:27:239]: Transforming table Binary.

    MSI (c) (00:7C) [08:00:27:239]: Transforming table Binary.

    MSI (c) (00:7C) [08:00:27:239]: Note: 1: 2262 2: Binary 3: -2147287038
    MSI (c) (00:7C) [08:00:27:286]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (00:7C) [08:00:27:302]: Transforming table Error.

    MSI (c) (00:7C) [08:00:27:302]: Transforming table Error.

    MSI (c) (00:7C) [08:00:27:302]: Note: 1: 2262 2: Error 3: -2147287038
    DEBUG: Error 2826:  Control BottomLine on dialog ErrorDlg extends beyond the boundaries of the dialog to the right by 5 pixels
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: ErrorDlg, BottomLine, to the right
    The user who's currently logged on doesn't have sufficient permissions to install this package. You need at least Exchange Server Administrator permissions on the current computer to complete this task.
    MSI (c) (00:B8) [08:03:47:792]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (00:B8) [08:03:47:855]: Transforming table Error.

    MSI (c) (00:B8) [08:03:47:870]: Transforming table Error.

    MSI (c) (00:B8) [08:03:47:870]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (00:B8) [08:03:47:870]: Product: Microsoft Exchange Server -- The user who's currently logged on doesn't have sufficient permissions to install this package. You need at least Exchange Server Administrator permissions on the current computer to complete this task.

    Action ended 8:03:47: CA_PATCH_OWA_PERMISSION_ERROR. Return value 3.
    MSI (c) (00:B8) [08:03:47:886]: Doing action: FatalError
    Action 8:03:47: FatalError.
    Action start 8:03:47: FatalError.
    MSI (c) (00:B8) [08:03:47:933]: Transforming table CustomAction.

    MSI (c) (00:B8) [08:03:47:948]: Transforming table CustomAction.

    MSI (c) (00:B8) [08:03:47:948]: Note: 1: 2262 2: CustomAction 3: -2147287038
    MSI (c) (00:B8) [08:03:47:948]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'FatalError'
    MSI (c) (00:B8) [08:03:47:964]: Transforming table CustomAction.

    MSI (c) (00:B8) [08:03:47:980]: Transforming table CustomAction.

    MSI (c) (00:B8) [08:03:47:980]: Note: 1: 2262 2: CustomAction 3: -2147287038
    MSI (c) (00:7C) [08:03:47:995]: Transforming table Binary.

    MSI (c) (00:7C) [08:03:48:011]: Transforming table Binary.

    MSI (c) (00:7C) [08:03:48:011]: Note: 1: 2262 2: Binary 3: -2147287038
    MSI (c) (00:7C) [08:03:48:042]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (00:7C) [08:03:48:073]: Transforming table Error.

    MSI (c) (00:7C) [08:03:48:073]: Transforming table Error.

    MSI (c) (00:7C) [08:03:48:073]: Note: 1: 2262 2: Error 3: -2147287038
    DEBUG: Error 2826:  Control BottomLine on dialog FatalError extends beyond the boundaries of the dialog to the right by 5 pixels
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalError, BottomLine, to the right
    Action 8:03:48: FatalError. Dialog created
    MSI (c) (00:60) [08:03:48:073]: Note: 1: 2731 2: 0
    Action ended 8:03:49: FatalError. Return value 2.
    Action ended 8:03:49: INSTALL. Return value 3.
    MSI (c) (00:B8) [08:03:49:120]: Destroying RemoteAPI object.
    MSI (c) (00:60) [08:03:49:120]: Custom Action Manager thread ending.

    Tuesday, November 24, 2009 7:59 PM
  • Blacktoe,

    It looks like you are running into a limit of 1 minute which we set in the code to do the check.

    For this rollup
    -> Unfortunately there is no way to bypass this check or configure the timeout to a higher value. You could probably try running this at a time when CPU contention on your laptop from other processes is minimal. If you have been using the same account to install the previous rollups and have not had issues then you should be ok. Also, the chance that you will run into this issue in production is slim because those systems will be a lot faster. 

    For future rollups
    -> We will redesign this code to address this in the future rollups for test systems which will be much slower than production. We are evaluating our options but the most likely fix would be to increase the default timeout to a sufficiently high value to cover the speed differences in both test and production systems.

    Thanks,

    -Ananth

    Tuesday, November 24, 2009 8:32 PM
  • Ananth,

    I bumped up the memory for my virtual server and it ran through with no issues.  This is the first time that I've had to bump up the memory to complete an update rollup or service pack in my virtual test environment.  My test exchange servers have been running since the original version of Exchange Server 2007 with all update rollups without any issues.  Thank you for pointing me in the right direction.
    Tuesday, November 24, 2009 9:44 PM
  • I have found the cause. The update rollup will not install if you have PowerShell 2.0 installed (I have the RTW version from KB968930). Revert to PowerShell 1.0 and it works.

    It was stated in the Exchange Team blog that SP2 supported PowerShell 2.0. It looks like the rollup patch installer doesn't.

    Hello Neil,

    Was there ever any resolution to this issue with trying to install RU1 and PS2.0 on the same machine ?


    Sam

    Wednesday, December 9, 2009 6:21 AM
  • Hi all!

    Even though my Exchange Server (on Small Business Server 2008) is on SP2, the Update Rollup Setup tells me, that i do not have the requested Version.
    This is my System (some values are hidden due to privacy):

    --<snip>--
    [PS] Get-Exchange-Server | fl
    [...]
    IsHubTransportServer              : True
    IsClientAccessServer              : True
    IsExchange2007OrLater             : True
    IsEdgeServer                      : False
    IsMailboxServer                   : True
    IsMemberOfCluster                 : No
    IsProvisionedServer               : False
    IsUnifiedMessagingServer          : False
    [...]
    AdminDisplayVersion               : Version 8.2 (Build 176.2)
    [...]
    ServerRole                        : Mailbox, ClientAccess, HubTransport
    ErrorReportingEnabled             :
    StaticDomainControllers           : {}
    StaticGlobalCatalogs              : {}
    StaticConfigDomainController      :
    StaticExcludedDomainControllers   : {}
    CurrentDomainControllers          : {}
    CurrentGlobalCatalogs             : {}
    CurrentConfigDomainController     :
    [...]
    IsExchange2007TrialEdition        : False
    IsExpiredExchange2007TrialEdition : False
    RemainingTrialPeriod              : 00:00:00
    IsValid                           : True
    [...]
    ExchangeVersion                   : 0.1 (8.0.535.0)
    [...]
    ObjectClass                       : {top, server, msExchExchangeServer}
    WhenChanged                       : 28.12.2009 10:55:30
    WhenCreated                       : 13.11.2009 13:38:23
    --<snap>--

    AFAIK the Update Rollup brings Exchange to version 8.2.217.2.

    The Updater tells me
    --<snip>--
    The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch
    --<snap>--

    When installing via
    msiexec /p Exchange2007-KB971534-x64-DE.msp /lxv* exru.log
    i get the following log:
    --<snip>--
    === Verbose logging started: 28.12.2009  15:51:57  Build type: SHIP UNICODE 4.05.6002.00  Calling process: C:\Windows\system32\msiexec.exe ===
    MSI (c) (90:E4) [15:51:57:662]: Resetting cached policy values
    MSI (c) (90:E4) [15:51:57:662]: Machine policy value 'Debug' is 0
    MSI (c) (90:E4) [15:51:57:662]: ******* RunEngine:
               ******* Product: {24B2C164-DE66-44FE-B468-A46D9D5E6B31}
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (90:E4) [15:51:57:664]: Machine policy value 'DisableUserInstalls' is 0
    MSI (c) (90:E4) [15:51:57:705]: Cloaking enabled.
    MSI (c) (90:E4) [15:51:57:705]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (90:E4) [15:51:57:723]: End dialog not enabled
    MSI (c) (90:E4) [15:51:57:725]: Original package ==> C:\Windows\Installer\604000f9.msi
    MSI (c) (90:E4) [15:51:57:725]: Package we're running from ==> C:\Windows\Installer\604000f9.msi
    MSI (c) (90:E4) [15:51:57:817]: APPCOMPAT: looking for appcompat database entry with ProductCode '{24B2C164-DE66-44FE-B468-A46D9D5E6B31}'.
    MSI (c) (90:E4) [15:51:57:817]: APPCOMPAT: no matching ProductCode found in database.
    MSI (c) (90:E4) [15:51:57:821]: MSCOREE not loaded loading copy from system32
    MSI (c) (90:E4) [15:51:57:850]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
    MSI (c) (90:E4) [15:51:58:886]: Original patch ==> D:\Software\Exchange2007-KB971534-x64-DE.msp
    MSI (c) (90:E4) [15:51:58:886]: Patch we're running from ==> C:\Users\ch_root\AppData\Local\Temp\2\ee247a.msp
    MSI (c) (90:E4) [15:51:58:946]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'D:\Software\Exchange2007-KB971534-x64-DE.msp' against software restriction policy
    MSI (c) (90:E4) [15:51:58:947]: SOFTWARE RESTRICTION POLICY: D:\Software\Exchange2007-KB971534-x64-DE.msp has a digital signature
    MSI (c) (90:E4) [15:52:01:427]: SOFTWARE RESTRICTION POLICY: D:\Software\Exchange2007-KB971534-x64-DE.msp is permitted to run at the 'unrestricted' authorization level.
    MSI (c) (90:E4) [15:52:01:429]: SequencePatches starts. Product code: {24B2C164-DE66-44FE-B468-A46D9D5E6B31}, Product version: 8.2.176.2, Upgrade code: {176A0BF3-6A69-4EEB-95D6-F67F0E9751E0}, Product language 1033
    MSI (c) (90:E4) [15:52:01:437]: Optimizations are not possible in the patch sequencer because there are no applied patches.
    MSI (c) (90:E4) [15:52:01:437]: PATCH SEQUENCER: verifying the applicability of QFE patch D:\Software\Exchange2007-KB971534-x64-DE.msp against product code: {24B2C164-DE66-44FE-B468-A46D9D5E6B31}, product version: 8.2.176.2, product language 1033 and upgrade code: {176A0BF3-6A69-4EEB-95D6-F67F0E9751E0}
    MSI (c) (90:E4) [15:52:01:437]: Validating transform 'E12_DAT_RTMToE12_DAT_UPG' with validation bits 0x923
    MSI (c) (90:E4) [15:52:01:437]: Note: 1: 2745 2: E12_DAT_RTMToE12_DAT_UPG 3: C:\Users\ch_root\AppData\Local\Temp\2\ee247a.msp 4: 1031 5: 1033
    MSI (c) (90:E4) [15:52:01:437]: 1: 2745 2: E12_DAT_RTMToE12_DAT_UPG 3: C:\Users\ch_root\AppData\Local\Temp\2\ee247a.msp 4: 1031 5: 1033
    MSI (c) (90:E4) [15:52:01:437]: PATCH SEQUENCER: QFE patch D:\Software\Exchange2007-KB971534-x64-DE.msp is not applicable.
    MSI (c) (90:E4) [15:52:01:438]: PATCH SEQUENCER: there's no supersedence information available, so no patches will be superseded.
    MSI (c) (90:E4) [15:52:01:438]: SequencePatches returns success.
    MSI (c) (90:E4) [15:52:01:438]: Final Patch Application Order:
    MSI (c) (90:E4) [15:52:01:439]: Other Patches:
    MSI (c) (90:E4) [15:52:01:439]: Unknown\Absent: {9627F154-D755-4F41-8FD0-105C31502B4F} - D:\Software\Exchange2007-KB971534-x64-DE.msp
    Das Upgrade kann nicht vom Windows-Installationsdienst installiert werden, da das zu aktualisierende Programm nicht vorhanden ist oder eine andere Version des Programms mit dem Upgrade aktualisiert wird. Überprüfen Sie, ob das zu aktualisierende Programm vorhanden ist und das richtige Upgrade verwendet wird.
    C:\Windows\Installer\604000f9.msi
    MSI (c) (90:E4) [15:52:01:441]: Product: Microsoft Exchange Server - Update '{9627F154-D755-4F41-8FD0-105C31502B4F}' could not be installed. Error code 1642. Additional information is available in the log file D:\Software\exru.log.

    MSI (c) (90:E4) [15:52:01:443]: Windows Installer installed an update. Product Name: Microsoft Exchange Server. Product Version: 8.2.176.2. Product Language: 1033. Update Name: {9627F154-D755-4F41-8FD0-105C31502B4F}. Installation success or error status: 1642.

    MSI (c) (90:E4) [15:52:01:443]: Note: 1: 1708
    MSI (c) (90:E4) [15:52:01:443]: Product: Microsoft Exchange Server -- Installation failed.

    MSI (c) (90:E4) [15:52:01:444]: Windows Installer installed the product. Product Name: Microsoft Exchange Server. Product Version: 8.2.176.2. Product Language: 1033. Installation success or error status: 1642.

    MSI (c) (90:E4) [15:52:01:456]: Attempting to delete file C:\Users\ch_root\AppData\Local\Temp\2\ee247a.msp
    MSI (c) (90:E4) [15:52:01:466]: MainEngineThread is returning 1642
    === Verbose logging stopped: 28.12.2009  15:52:01 ===
    --<snap>--

    Does anyone have a suggestion for me?

    cheers

    Christian
    Monday, December 28, 2009 3:03 PM
  • Sadly, I now find that the patch installer for Rollup 2 for Exchange 2007 SP2 also will not complete if PowerShell 2.0 has been installed, so nothing got changed. The procedure has to be to remove PowerShell 2.0, reboot, patch, put PowerShell 2.0 back.
    Wednesday, January 27, 2010 8:11 AM
  • Not only was there no resolution, but they have done the same thing with Rollup Update 2. You can have both, but you must be on PowerShell 1.0 when you do the Rollup installation.
    Wednesday, January 27, 2010 8:12 AM