I tried to roll out Update Rollup 2 for Exchange 2007 SP1 yesterday. I am running 8 exchange servers with the various roles. Im having issues installing it on th 2 mailbox servers I have running in a CCR environment. Once I verify the passive node is indeed fully passive, I run the .msp file and receive an error stating that it ended prematurely because of an error. The system has not been modified. The following is added to the Application Event Log: Product: Microsoft Exchange Server - Update 'Update Rollup 2 for Exchange Server 2007 Service Pack 1 (KB948016) 8.1.278.2' could not be installed. Error code 1603. Additional information is available in the log file C:\DOCUME~1\administrator\LOCALS~1\Temp\MSI1924a.LOG. The following is the contents of MSI1924a.log: === Logging stopped: 6/3/2008 10:54:03 ===MSI (c) (38:4C) [10:54:03:610]: Product: Microsoft Exchange Server - Update 'Update Rollup 2 for Exchange Server 2007 Service Pack 1 (KB948016) 8.1.278.2' could not be installed. Error code 1603. Additional information is available in the log file C:\DOCUME~1\administrator.LOE\Local Settings\Temp\MSIc694a.LOG. MSI (c) (38:4C) [10:54:03:610]: Note: 1: 1729 MSI (c) (38:4C) [10:54:03:610]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (38:4C) [10:54:03:610]: Transforming table Error. MSI (c) (38:4C) [10:54:03:610]: Transforming table Error. MSI (c) (38:4C) [10:54:03:610]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (38:4C) [10:54:03:610]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (38:4C) [10:54:03:610]: Transforming table Error. MSI (c) (38:4C) [10:54:03:610]: Transforming table Error. MSI (c) (38:4C) [10:54:03:610]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (38:4C) [10:54:03:610]: Product: Microsoft Exchange Server -- Configuration failed. MSI (c) (38:4C) [10:54:03:610]: Attempting to delete file C:\DOCUME~1\administrator.LOE\Local Settings\Temp\40c694b.mspMSI (c) (38:4C) [10:54:03:610]: Unable to delete the file. LastError = 32MSI (c) (38:4C) [10:54:03:625]: Grabbed execution mutex.MSI (c) (38:4C) [10:54:03:625]: Cleaning up uninstalled install packages, if any existMSI (c) (38:4C) [10:54:03:625]: MainEngineThread is returning 1603=== Verbose logging stopped: 6/3/2008 10:54:03 === As well as this: MSI (s) (E0:A8) [10:50:37:664]: Attempting to delete file C:\WINDOWS\Installer\406b6bc.mspMSI (s) (E0:A8) [10:50:37:664]: Unable to delete the file. LastError = 32MSI (s) (E0:A8) [10:50:37:664]: Attempting to delete file C:\WINDOWS\Installer\406b6bc.mspMSI (s) (E0:A8) [10:50:37:664]: Unable to delete the file. LastError = 32MSI (s) (E0:A8) [10:50:37:664]: MainEngineThread is returning 1603MSI (s) (E0:A4) [10:50:37:774]: Destroying RemoteAPI object.MSI (s) (E0:14) [10:50:37:774]: Custom Action Manager thread ending.MSI (c) (38:4C) [10:50:37:774]: Back from server. Return value: 1603MSI (c) (38:4C) [10:50:37:774]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1MSI (c) (38:4C) [10:50:37:774]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'.Action ended 10:50:37: ExecuteAction. Return value 3.MSI (c) (38:4C) [10:50:37:774]: Doing action: FatalErrorAction 10:50:37: FatalError. Action start 10:50:37: FatalError.MSI (c) (38:4C) [10:50:37:774]: Transforming table CustomAction. MSI (c) (38:4C) [10:50:37:774]: Transforming table CustomAction. MSI (c) (38:4C) [10:50:37:774]: Note: 1: 2262 2: CustomAction 3: -2147287038 MSI (c) (38:1C) [10:50:37:774]: Transforming table Binary. MSI (c) (38:1C) [10:50:37:774]: Transforming table Binary. MSI (c) (38:1C) [10:50:37:774]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (c) (38:1C) [10:50:37:789]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (38:1C) [10:50:37:789]: Transforming table Error. MSI (c) (38:1C) [10:50:37:789]: Transforming table Error. MSI (c) (38:1C) [10:50:37:789]: 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 pixelsThe 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 rightAction 10:50:37: FatalError. Dialog created The following is the contents of the Servicecontrol.log: [15:55:51] ************************************************[15:55:51] * ServiceControl.ps1: 6/2/2008 3:55:51 PM[15:55:51] Performing service control with options: BeforePatch[15:55:51] Setting ApplicationBase to D:\Program Files\Microsoft\Exchange Server\bin[15:55:51] Setting AssemblyName to Microsoft.Exchange.PowerShell.Configuration, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35[15:55:51] Setting CustomPSSnapInType to Microsoft.Exchange.Management.PowerShell.SetupPSSnapIn[15:55:51] Setting PowerShellVersion to 1.0[15:55:51] Setting Description to Setup Tasks for the Exchange Server (v240)[15:55:51] Setting ModuleName to D:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.PowerShell.configuration.dll[15:55:51] Setting Version to 8.0.0.0[15:55:51] Setting Vendor to Microsoft[15:55:52] Saving service and registry data[15:55:52] Saving service state to 'C:\DOCUME~1\administrator\Local Settings\Temp\StoppedServices.xml'...[15:55:53] Saving services registry data[15:55:53] Error: There is also this in the Se I have searched for hours but cannot find anything to assist in solving this issue. It appears to falter when it tries to export the state of the services. Here is the statement when i manually try to run ServiceControl.ps1 BeforePatch Add-PSSnapin : Windows PowerShell snap-in "Microsoft.Exchange.Management.PowerShell.Setup" is loaded with the following warnings: There were errors in loading the format data file:Microsoft.Exchange.Management.PowerShell.Setup, D:\Program Files\Microsoft\Exchange Server\bin\Exchange.format.ps1xml : File skipped because it was already present from "Microsoft.Exchange.Management.PowerShell.Admin".At D:\Program Files\Microsoft\Exchange Server\bin\ServiceControl.ps1:598 char:14+ add-PSSnapin <<<< -Name Microsoft.Exchange.Management.PowerShell.SetupAdd-PSSnapin : Cannot add Windows PowerShell snap-in Microsoft.Exchange.Management.PowerShell.Admin because it is already added. Verify the name of the snap-in and try again.At D:\Program Files\Microsoft\Exchange Server\bin\ServiceControl.ps1:599 char:14+ add-PSSnapin <<<< -Name Microsoft.Exchange.Management.PowerShell.AdminGet-ItemProperty : The member "ImagePath" is already present.At D:\Program Files\Microsoft\Exchange Server\bin\ServiceControl.ps1:72 char:18+ get-itemproperty <<<< HKLM:\SYSTEM\CurrentControlSet\Services\* | export-clixml $scripterviceRegistryDataFile Can anyone assist?

Youre unable to complete the installation of rollup 2 for e2k7 on 2 mailbox server. I would like to know more about this issue: 1. Are you doing the update by windows Update or you download and install it from website? 2. Open EMS and run "ServiceControl.ps1 AfterPatch", it sets services back to the recorded state 3. Downloaded rollup2 from website and then apply to server Did you have a chance to check "Known Issues" part of KB 935490 for rollup2? There are same symptoms just like yours Here also shared the action plan which corrects installation in most situations: 1. Unregister Windows Installer <start->run->msiexec /unregister> 2. Reregister Windows Installer <start->run->msiexec /regserver>

Thank you very much for your post. Sorry its taken me this long to reply, but here is some more information. I dowloaded the update from the website and ran it locally on the server. If i run ServiceControl.ps1 AfterPatch manuallyI get the following error: [PS] C:\Documents and Settings\account>ServiceControl.ps1 AfterPatchAdd-PSSnapin : Windows PowerShell snap-in "Microsoft.Exchange.Management.PowerS***.Admin" is loaded with the following warnings: There were errors in loading the format data file:Microsoft.Exchange.Management.PowerShell.Admin, D:\Program Files\Microsoft\Exchange Server\bin\Exchange.format.ps1xml : File skipped because it was already present from "Microsoft.Exchange.Management.PowerShell.Setup".At D:\Program Files\Microsoft\Exchange Server\bin\ServiceControl.ps1:599 char:14+ add-PSSnapin <<<< -Name Microsoft.Exchange.Management.PowerShell.AdminWrite-Progress : Cannot bind argument to parameter 'Activity' because it is null.At D:\Program Files\Microsoft\Exchange Server\bin\ServiceControl.ps1:1017 char:25+ write-Progress -Activity <<<< $activity -Id 0 -Status 'Completed' -Completed Here is if i run ServiceControl.ps1 BeforePatch manually: [PS] C:\Documents and Settings\account>ServiceControl.ps1 BeforePatchAdd-PSSnapin : Windows PowerShell snap-in "Microsoft.Exchange.Management.PowerS***.Setup" is loaded with the following warnings: There were errors in loading the format data file:Microsoft.Exchange.Management.PowerShell.Setup, D:\Program Files\Microsoft\Exchange Server\bin\Exchange.format.ps1xml : File skipped because it was already present from "Microsoft.Exchange.Management.PowerShell.Admin".At D:\Program Files\Microsoft\Exchange Server\bin\ServiceControl.ps1:598 char:14+ add-PSSnapin <<<< -Name Microsoft.Exchange.Management.PowerShell.SetupAdd-PSSnapin : Cannot add Windows PowerShell snap-in Microsoft.Exchange.Management.PowerShell.Admin because it is already added. Verify the name of the snap-in and try again.At D:\Program Files\Microsoft\Exchange Server\bin\ServiceControl.ps1:599 char:14+ add-PSSnapin <<<< -Name Microsoft.Exchange.Management.PowerShell.AdminGet-ItemProperty : The member "ImagePath" is already present.At D:\Program Files\Microsoft\Exchange Server\bin\ServiceControl.ps1:72 char:18+ get-itemproperty <<<< HKLM:\SYSTEM\CurrentControlSet\Services\* | export-clixml $scripterviceRegistryDataFile I ran the msiexec /unregister and msiexec /regserver and tried again, but no such luck. Same problems.

There is also this in the servicecontrol.log.. Looks like it runs into problems saving registry data. Im using an account that has all the necessary rights (exchange admin, server admin, domain admin) [12:59:26] * ServiceControl.ps1: 7/17/2008 12:59:26 PM[12:59:26] Performing service control with options: BeforePatch[12:59:27] Setting ApplicationBase to D:\Program Files\Microsoft\Exchange Server\bin[12:59:27] Setting AssemblyName to Microsoft.Exchange.PowerShell.Configuration, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35[12:59:27] Setting CustomPSSnapInType to Microsoft.Exchange.Management.PowerShell.SetupPSSnapIn[12:59:27] Setting PowerShellVersion to 1.0[12:59:27] Setting Description to Setup Tasks for the Exchange Server (v240)[12:59:27] Setting ModuleName to D:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.PowerShell.configuration.dll[12:59:27] Setting Version to 8.0.0.0[12:59:27] Setting Vendor to Microsoft[12:59:27] Saving service and registry data[12:59:27] Saving service state to 'C:\DOCUME~1\account\LOCALS~1\Temp\StoppedServices.xml'...[12:59:28] Saving services registry data[12:59:29] Error: Thing is it saves theStoppedServices.xml file in the temp directory

I guess im the only one experiencing this.. Im worried that when SP2 comes out and we need to upgrade Ill have this same issue.

It's a bug in the script... add at line 900 $activity = 'BeforePatch' add at line 958: $activity='AfterPatch'Peter D. Wood