Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2256
  • Last Modified:

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\Local\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<RollupPackageNumber>-x64-EN.msp /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
0
Yardstick
Asked:
Yardstick
  • 3
2 Solutions
 
Simon Butler (Sembee)ConsultantCommented:
Rollup 10 is the minimum that you require for Exchange 2013 coexistence.

The CodeTwo product or AV are the most likely causes of the problems. Disabling it usually not enough, in some cases you have to unregister the product. Check with the vendor for guidance.

You cannot reinstall service packs for Exchange, although you can reinstall rollups. Rollups usually come in Windows Update, so the installation has probably been failing for a while.

Usually I would suggest a fresh download of the rollup, as errors in the download are very common. However you have in effect tried that with the rollup 10 installation.

The log generated by the failure should be enough, without actually turning the logging on. Therefore try it again without the logging enabled, but when the error comes up, look at the log mentioned.

Ensure that temp files is empty before you start, no SBS console running. Disabling the service cannot hurt, although it isn't something you always have to do.

Simon.
0
 
YardstickAuthor Commented:
Ok I'll try to to uninstall the CodeTwo Product, do a set-executionpolicy unrestricted and run the Rollup again. I will leave the antivirus as we have it on many exchange servers and we do not have this issue when installing rollups or SPs

I will let you guys know how it goes tomorrow morning as I have to do this afterhours
0
 
YardstickAuthor Commented:
Thank you Simon,
Your were right: Unregistering the CodeTwo  Transport Extensions helped resolve my issue. 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
Step 1: I launched EMS as Administrator and did a set-executionpolicy unrestricted ( you may be able to get away with using "remotesigned" to be a little more secure but I chose unrestricted)

Step 2: If you have a Spamfilter/Signature Creator or any other 3rd party software that has uses exchange extensions, you should Unregister them.
-in my case I opened CodeTwo Exchange Rules 2007 and: under settings->Transport Agent -clicked "uninstall" ; under system Items update -clicked "disable"

Step 3: I disabled the following services:
-Windows SBS manager Service -not sure if did anything but it did not hurt
-Our Server monitoring agent - if have a monitoring agent on your server such as Kaseya,Labtech,Nable you may want to do that as well
-disabled the CodeTwo services - Email signature software
-Disabled the scheduled backup Job from the backup manager ( just so it does not start on you while the Rollup is running... if the update takes a little longer)

Step 4: Went back to the EMS( which was still running as Administrator) and ran the rollup:  D:\_Migration_Temp>.\Exchange2007-KB2917522-x64-EN.msp

Note: If owa does not work after the rollup then navigate to your Exchange Bin directory via the management shell – usually C:\Program Files\Microsoft\Exchange Server\Bin and  type ".\UpdateOWA.ps1" -no quotes.

Step 5: I reinstalled the CodeTwo Extensions, started all services and ... we are in business!
0
 
YardstickAuthor Commented:
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
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now