Yardstick
asked on
Exchange 2007 SP3 Rollup 13 Fails - Setup Ended Prematurely
Hi Guys,
I am having an issue installing Exchange 2007 Sp3 Rollup 13 on an SBS 2008 Server. Let me give you a little background info before I ask The Question.
Current Environment:
-Windows Small Business Server 2008 SP2
-Exchange server 2008 Sp3 Rollup 5
-CodeTwo Exchange Rules 2007 ( Email signature Software)
What I'm trying to accomplish:
-Migration to Exchange 2013 Sp1
-End goal: Windows Server 2012 R2 Domain controller + Exchange 2013 Sp1 (separate servers)
Error message:
Update Rollup 13 Exchange 2007 SP3 - Setup Ended Prematurely
event id : 1023: Product: Microsoft Exchange Server - Update 'Update Rollup 13 for Exchange Server 2007 Service Pack 3 (KB2788321) 8.3.298.3' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\yttech\AppData\Lo cal\Temp\2 \MSIbd4ae. LOG.
What I did before for this update:
-Disabled CodeTwo service
-Disabled Antivirus
-Took a Backup of the server( ShaddowProtect)
-Added a 2012R2 Domain Controller to the environment
What I did to apply this Rollup:
Launched Command Prompt as Administrator and ran the update= FAILED with the error specified.
-eventually I even Disabled UAC.
-Also tried Rollup 10= fails the same way
What I did not do:
-the execution Policy was restricted; I did not do a set-executionpolicy unrestricted
-I did not stop the Windows SBS Manager service (though the console was closed at the time)
+After this I ran a "Exchange2007-KB<RollupPac kageNumber >-x64-EN.m sp /lxv c:\<filename>.log"... well, now I'm stuck with a 37 MB log file. But I'm not sure what to look for in it... I certainly don't want to read it all... It's ridiculously large.
The only thing in the log that appears in several places seems to be a CAQuietExec Error:
-------------------------- --------
MSI (s) (68:18) [22:56:53:672]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (68!30) [22:56:54:536]: Creating MSIHANDLE (197) of type 790531 for thread 10544
CAQuietExec: Error 0x80070001: Command line returned an error.
MSI (s) (68!30) [22:56:54:539]: Closing MSIHANDLE (197) of type 790531 for thread 10544
MSI (s) (68!30) [22:56:54:540]: Creating MSIHANDLE (198) of type 790531 for thread 10544
CAQuietExec: Error 0x80070001: CAQuietExec Failed
MSI (s) (68!30) [22:56:54:542]: Closing MSIHANDLE (198) of type 790531 for thread 10544
MSI (s) (68:C8) [22:56:54:542]: Closing MSIHANDLE (196) of type 790536 for thread 2028
-------------------------- ---------- --
After Speaking with my colleagues, I have a few things to try, such as:
-set-executionpolicy unrestricted
-disable SBS manager service
-possibly reinstall SP3 and Rollup 5
My question is probably obvious now! How do I get this Rollup to apply? :) Did I make a terrible mistake by adding a 2012R2 Dc (which updated the schema)? Do I really need to reapply the service pack and rollup? or what should I query in that Rolup log to find the issue; I can't seem to find anything relevant by querying "Error"
Thanks,
Adrian
I am having an issue installing Exchange 2007 Sp3 Rollup 13 on an SBS 2008 Server. Let me give you a little background info before I ask The Question.
Current Environment:
-Windows Small Business Server 2008 SP2
-Exchange server 2008 Sp3 Rollup 5
-CodeTwo Exchange Rules 2007 ( Email signature Software)
What I'm trying to accomplish:
-Migration to Exchange 2013 Sp1
-End goal: Windows Server 2012 R2 Domain controller + Exchange 2013 Sp1 (separate servers)
Error message:
Update Rollup 13 Exchange 2007 SP3 - Setup Ended Prematurely
event id : 1023: Product: Microsoft Exchange Server - Update 'Update Rollup 13 for Exchange Server 2007 Service Pack 3 (KB2788321) 8.3.298.3' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\yttech\AppData\Lo
What I did before for this update:
-Disabled CodeTwo service
-Disabled Antivirus
-Took a Backup of the server( ShaddowProtect)
-Added a 2012R2 Domain Controller to the environment
What I did to apply this Rollup:
Launched Command Prompt as Administrator and ran the update= FAILED with the error specified.
-eventually I even Disabled UAC.
-Also tried Rollup 10= fails the same way
What I did not do:
-the execution Policy was restricted; I did not do a set-executionpolicy unrestricted
-I did not stop the Windows SBS Manager service (though the console was closed at the time)
+After this I ran a "Exchange2007-KB<RollupPac
The only thing in the log that appears in several places seems to be a CAQuietExec Error:
--------------------------
MSI (s) (68:18) [22:56:53:672]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (68!30) [22:56:54:536]: Creating MSIHANDLE (197) of type 790531 for thread 10544
CAQuietExec: Error 0x80070001: Command line returned an error.
MSI (s) (68!30) [22:56:54:539]: Closing MSIHANDLE (197) of type 790531 for thread 10544
MSI (s) (68!30) [22:56:54:540]: Creating MSIHANDLE (198) of type 790531 for thread 10544
CAQuietExec: Error 0x80070001: CAQuietExec Failed
MSI (s) (68!30) [22:56:54:542]: Closing MSIHANDLE (198) of type 790531 for thread 10544
MSI (s) (68:C8) [22:56:54:542]: Closing MSIHANDLE (196) of type 790536 for thread 2028
--------------------------
After Speaking with my colleagues, I have a few things to try, such as:
-set-executionpolicy unrestricted
-disable SBS manager service
-possibly reinstall SP3 and Rollup 5
My question is probably obvious now! How do I get this Rollup to apply? :) Did I make a terrible mistake by adding a 2012R2 Dc (which updated the schema)? Do I really need to reapply the service pack and rollup? or what should I query in that Rolup log to find the issue; I can't seem to find anything relevant by querying "Error"
Thanks,
Adrian
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will keep one point for this post so I can explain everything I did to resolve this issue. It will be easier for whoever reads this post to track down the solution. The rest of the 499 Will go to you
ASKER
I will let you guys know how it goes tomorrow morning as I have to do this afterhours