A Repair Blog Written By Gurus

Setup failed while installing sub-component Exchange ActiveSync with error code 0xC0070643

In the process of set­ting up a new 2003 Exchange Server, we were con­fronted with the fol­low­ing error while installing Ser­vice Pack 2.

Setup failed while installing sub-component Exchange ActiveSync with error code 0xC0070643 (please con­sult the instal­la­toin logs for a detailed descrip­tion). You may can­cel the instal­la­tion or try the failed setup again.

Dig­ging into the instal­la­tion logs we see that the setup is fail­ing while attempt­ing to install MSXML:

[18:52:22] Call­ing MSXML installer with com­mand line: “msiexec /i msxml3.msi /q reboot=“ReallySuppress”“
[18:52:22] Process cre­ated … wait­ing (-1)
[18:52:23] Process has exited with 0x000643
[18:52:23] The command

msiexec /i msxml3.msi /q reboot=“ReallySuppress”

failed, return­ing error code 1603 (Fatal error dur­ing instal­la­tion.). — ID:31136 — ScCre­ateProcess (f:\tisp2\admin\src\libs\exsetup\hiddenw1.cxx:1821)
Error code 0XC0070643 (1603): Fatal error dur­ing installation.

The event logs sub­se­quently tells us:

Event Type: Error
Event Source: Msi­In­staller
Event ID: 1013
Descrip­tion:
Prod­uct: Microsoft XML Parser — Your sys­tem has newer ver­sion of MSXML3 SP5 than the ver­sion you are attempt­ing to install. Setup will quit.

The way we solved our issue, is as follows:

1. Get a copy of the Win­dows Installer pack­age for the ver­sion of MSXML 3 you have installed.
2. Place a copy inside Exchsrvr\bin
3. Rename the exist­ing msxml3.msi to msxml3.msi.backup
4. Make a copy of the lat­est ver­sion MSXML Win­dows Installer file and rename it to msxml3.msi. This will leave you with msxml3.msi and msxml3sp?.msi (in my case msxml3sp7.msi).
5. Click Retry on the error win­dow, and it should con­tinue as planned.

In our case we need MSXML.msi from sp1 815kb, instead of the sp2 ver­sion at 1.8 mb

Spe­cial thanks to Mexi Rob for the help on this issue. :-)

This entry was posted on Saturday, November 22nd, 2008 at 11:14 am and is filed under Server 2003 and tagged with , , , , , , , , , , , , , , , , , , , , , , , , , . You can skip to the end and leave a response. Pinging is currently not allowed.

Was this article helpful? Here's a few related articles which may also interest you.

Related Posts:

12 Comments to “Setup failed while installing sub-component Exchange ActiveSync with error code 0xC0070643”

  1. Kevin K. says:
    August 6, 2009 at 5:52 am

    Thanks a lot, you solved my problem.

  2. Admin says:
    August 10, 2009 at 6:23 pm

    No prob­lem. We’re glad our posts are help­ing peo­ple. We love hear­ing replies like yours.

  3. rick says:
    June 2, 2010 at 6:25 am

    Thank you for this post…i would have never fig­ured this one out

  4. Admin says:
    June 2, 2010 at 7:48 am

    We’re just glad to hear our posts are help­ing peo­ple. Thanks for your comment.

  5. ITAdmin1 says:
    December 17, 2010 at 9:01 am

    Per­fect solu­tion. Wasn’t clear though once the cur­rent file is renamed do we leave the updated file as msxml3.msi or do we delete it and revert the file msxml3.msi.old back to msxml3.msi?

  6. Admin says:
    January 13, 2011 at 10:10 am

    No you shouldn’t revert the file. If this fix solved your prob­lem, then the file we used to replace msxml.msi would be the cor­rect file for your sys­tem. Revert­ing it would undoubtably cause errors down the road.

    Our rea­son­ing for this is that if at some point in the future a prob­lem arises, and you need to do some type of repair, repair install, etc… You’ll already hav­ing the cor­rect files in place, and you’re repair efforts will more than likely be suc­cess­ful. Thanks for your reply, and good luck in your efforts.

  7. Tyler says:
    January 24, 2011 at 9:44 am

    This looks like just what I need. How do I tell which MSXML ver­sion I need? I looked in Add remove pro­grams and I don’t have any MSXML 3 ver­sion listed. I can only find the exchange install log and not the setup log.

  8. Tyler says:
    January 24, 2011 at 9:55 am

    Thanks, I had MSXML 4 sp2 and MSXML 6 installed, so I just used MSXML6 and the install com­pleted suc­cess­fully. Thank you so much. :)

  9. Admin says:
    January 25, 2011 at 9:46 am

    Glad we could help. :-)

  10. Mo says:
    June 20, 2011 at 3:45 pm

    Thx you very much. I almost went nuts of that error.

    Thx men.

  11. Dave Saunders says:
    June 22, 2011 at 2:47 pm

    That was unbe­liev­able — hardly ever is the panic of see­ing a halt like that so thor­oughly solved as fol­low­ing those direc­tions. Really appre­ci­ate you putting those out there for us.

  12. Richard says:
    August 24, 2011 at 4:37 am

    Thanks for that, your solu­tion worked a treat!!

Leave a Comment