Previous Next

Thread: II7 w2k8 error 0x80070643

Last post 03-27-2008 12:45 PM by wadeh. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 03-21-2008, 6:25 PM

    • Kanien
    • Top 75 Contributor
    • Joined on 01-31-2008, 12:14 AM
    • Posts 51

    II7 w2k8 error 0x80070643

    I installed FCGI then later went to add ASP and CGI features to the Web Server.  Upon reboot it failed to install the role services and crapped the whole web server.  I tried uninstalling the web server, but it gives same error when attempting to remove.  Any idea how to get past this without a complete reinstall?

     

    Web Server Crash 

  • 03-27-2008, 12:05 PM In reply to

    • HSeiler
    • Top 50 Contributor
    • Joined on 06-10-2002, 8:41 PM
    • Posts 60

    Re: II7 w2k8 error 0x80070643

    Unfortunately this is not a simple IIS setup error, IIS never returns failure during uninstall. The error code 0x80070643 indicates that at this point the CBS component store is corrupted with a failed transaction that it will forever try and process. 

    Two things to try:

    1) OS repair – insert media and start setup.exe,  then choose Upgrade

     

    2) if that does not work then you will need to clean install OS.

     

    Henry Seiler
    IIS Deployment
  • 03-27-2008, 12:45 PM In reply to

    • wadeh
    • Top 50 Contributor
    • Joined on 04-19-2005, 6:17 PM
    • Posts 97

    Re: II7 w2k8 error 0x80070643

    I just wanted to jump in here to clarify a few things.

    I've been chatting with Henry (hseiler) for the last few minutes.  Suggesting a clean install of the OS is very serious business.  If there are any behaviors in FastCGI (or any other part of IIS) that can lead to this, I want to make sure that we look into it.

    What has happened here is that an internal component of the Windows setup engine (the component store that Henry mentioned) has somehow become corrupted.  I've discusssed potential causes for this and he tells me that with the way the IIS component setup works, there is nothing we are doing that will lead to this.  There is also no way a user could induce this situation by setting up something incorrectly.  In the instances we know of where this problem has been seen, it has occurred randomly during install or uninstall of some component.  The specific component does not matter.

    Unfortunately, once the machine is in this state, the Windows installer is broken.  It cannot add or remove any Windows components and it cannot apply updates to the system.

    We have reason to believe that the OS repair that Henry describes may correct the problem, as it rewrites the component store.  It should also preserve the configuration of the machine.  Note that you will need to re-install any OS updates after doing this, since the nature of the repair is to restore OS files from your media.

    Please let us know how the OS repair works for you.  We are interested in confirming that this action corrects the problem (since we've never been able to get our hands on a machine in this state to try it for ourselves.)

    Thanks,

    -Wade

Page 1 of 1 (3 items)
Page view counter