locked
KB3041687 and Windows Server 2003 0x80070643 RRS feed

  • Question

  •       

    There's still 119 days of support left on Server 2003 and we are working to eliminate the last few in our environment but we still have problems that no one seems to be addressing.

    I am getting error code 0x80070643 on every Server 2003 installation we have.  What links I have found regarding this error all point to .Net 4  and reinstalling it.  On the first two servers .Net 4 had not been installed so I tried adding it and then patching to current levels.  I still get the 0x80070643 error when KB3041687 tries to install again.  I haven't dug into the other servers but none of them run .Net 4 apps so I don't expect to find .Net 4 installed there either.

    Anyone have any ideas on what I can try to repair this patch?  Where else to look?

    Monday, March 16, 2015 7:26 PM

Answers

  • Just worked out a work around!

    1. Run the update.
    2. While the update is running, copy SCEPInstall.exe from the %windir%\softwaredistribution\download\install\ folder.
    3. Once the update fails, uninstall SCEP.
    4. Install SCEP using the copied install in step 2.

    It's a kludge but it got the result I needed.

    • Proposed as answer by Andrew.JR Friday, March 27, 2015 12:49 PM
    • Marked as answer by Michael Plakus Friday, March 27, 2015 1:11 PM
    Friday, March 27, 2015 12:31 PM

All replies

  • This is for the botched/fixed SCEP/FEP update from Feb 2015 ?

    I'd log a case for this one..


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Monday, March 16, 2015 8:43 PM
  • I was having the same problem on two 2003 servers.  But i was able to get it to install by running the FEPInstall.exe file manually from %windir%\softwaredistribution\download\install\fepinstall.exe.  It ran, seemed to just go away during the upgrade, but then I checked the GUI after a few minutes of waiting and it said it was version 4.7.209.0.  Windows Update still detects it but the About version doesn't lie!
    Tuesday, March 24, 2015 12:43 PM
  • I received the same error when running the update this way.  I did have a difference in that I am using scepinstall.exe instead of fepinstall.exe.  
    Tuesday, March 24, 2015 1:04 PM
  • Michael, did you find a resolution for this?  We are experiencing the same problem on our 2003 servers.
    Friday, March 27, 2015 11:44 AM
  • So far no resolution.  It's just driving us to get rid of 2003 even faster than before. 108 days of "support" and counting.
    Friday, March 27, 2015 12:19 PM
  • Just worked out a work around!

    1. Run the update.
    2. While the update is running, copy SCEPInstall.exe from the %windir%\softwaredistribution\download\install\ folder.
    3. Once the update fails, uninstall SCEP.
    4. Install SCEP using the copied install in step 2.

    It's a kludge but it got the result I needed.

    • Proposed as answer by Andrew.JR Friday, March 27, 2015 12:49 PM
    • Marked as answer by Michael Plakus Friday, March 27, 2015 1:11 PM
    Friday, March 27, 2015 12:31 PM
  • I had the same result, thanks!  I was previously trying to use the file to update it manually, but a reinstall using that file actually worked.
    Friday, March 27, 2015 12:49 PM