locked
Unable to Update FCS Client 0x80070652 0x80070643 RRS feed

  • Question

  • I have one server that errors out every time I try to install the client update.  All other updates install fine on that machine and client updates for all other machines install fine.  This is machine specific.  This server is Server 2012 and I'm running WSUS from Server 2012, Role.

    Here's my WindowsUpdate Log:

    2012-12-04    11:16:53:044    7724    1fd0    Handler    :::::::::::::
    2012-12-04    11:16:53:044    7724    1fd0    Handler    :: START ::  Handler: Command Line Install
    2012-12-04    11:16:53:044    7724    1fd0    Handler    :::::::::
    2012-12-04    11:16:53:044    7724    1fd0    Handler      : Updates to install = 1
    2012-12-04    11:16:53:262    7724    1fd0    Handler      : WARNING: Command line install completed. Return code = 0x80070652, Result = Failed, Reboot required = false
    2012-12-04    11:16:53:262    7724    1fd0    Handler      : WARNING: Exit code = 0x8024200B
    2012-12-04    11:16:53:262    7724    1fd0    Handler    :::::::::
    2012-12-04    11:16:53:262    1052    17d8    AU    >>##  RESUMED  ## AU: Installing update [UpdateId = {F01C7565-27CA-4D68-9694-DA5CE2FF6B12}]
    2012-12-04    11:16:53:262    7724    1fd0    Handler    ::  END  ::  Handler: Command Line Install
    2012-12-04    11:16:53:262    1052    17d8    AU      # WARNING: Install failed, error = 0x80070643 / 0x80070652
    2012-12-04    11:16:53:262    7724    1fd0    Handler    :::::::::::::
    2012-12-04    11:16:53:262    1052    222c    Agent    *********
    2012-12-04    11:16:53:262    1052    222c    Agent    **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2012-12-04    11:16:53:262    1052    17d8    AU    Install call completed.
    2012-12-04    11:16:53:262    1052    222c    Agent    *************
    2012-12-04    11:16:53:262    1052    17d8    AU      # WARNING: Install call completed, reboot required = No, error = 0x00000000
    2012-12-04    11:16:53:262    1052    17d8    AU    #########
    2012-12-04    11:16:53:262    1052    17d8    AU    ##  END  ##  AU: Installing updates [CallId = {5EF53443-6F46-45C5-868A-E7BC47CB50D9}]
    2012-12-04    11:16:53:262    1052    17d8    AU    #############

    Does anyone have any idea what could be causing this?  I've stopped WU and BITS and blew out the softwaredist folder as well deleted the machine from WSUS and readded it.  The problem persists.

    I would appreciate any help!

    Tuesday, December 4, 2012 7:41 PM

Answers

  • So then I'm not going to get any help from Microsoft. "Not supported" and "doesn't work" are two completely different things. FCS works on Server 2012 and Win8. I've got 9 months of solid testing to attest to that. In addition to my 24 servers I also have over 100 Win8 machines running FCS just fine. I figured official support would come later after it's release like Exchange 2010 eventually will. Which is why we decided to move forward with it. I guess not.

    There is no such thing as updating to FEP. You need to buy it. We are in no position to write a check for something simply because Microsoft choose to not support a product that works just fine. As for this machine, I guess I'll just have to reload it. Clearly something has just gone wrong with it.

    I'll just have to deal with a product that works with no support until we can buy something else.

    Unfortunately your second link has nothing to do with this. What was that for? I don't think you understood what I meant by "mirror". I was simply stating they are identical spec wise.

    EDIT:

    Typical, reloaded and working fine.  I hate having that as an answer but it doesn't look like anyone will able to figure this out without official support to back it up.

    • Edited by JEmlay Saturday, December 8, 2012 12:34 AM
    • Marked as answer by JEmlay Saturday, December 8, 2012 12:34 AM
    Friday, December 7, 2012 5:44 PM

All replies

  • A little more info on the error:

    Microsoft Forefront Client Security has encountered an error trying to update signatures.
         Previous Engine Version: 1.1.9002.0
         Error code: 0x80070652
         Error description: Another installation is already in progress. Complete that installation before proceeding with this install.

    I can reboot the server and this one definition update will install however, as soon as a new update comes down, that one fails.  Rinse, repeat.

    I can only get one definition update per boot.

    EDIT:

    Since when do definition updates not install on pending reboot status?  All my machines install definitions regardless of reboot pending.  Also, if there's a reboot pending status then why are all other updates installing just fine?


    • Edited by JEmlay Wednesday, December 5, 2012 6:38 PM
    Tuesday, December 4, 2012 8:21 PM
  • Hi,

    Thank you for the post.

    As far as understand, FCS is not supported on windows server 2012, http://blogs.technet.com/b/configmgrteam/archive/2012/09/10/support-questions-about-windows-8-and-windows-server-2012.aspx

    Regards,


    Nick Gu - MSFT

    Thursday, December 6, 2012 3:47 PM
  • Well....it works fine on my other 23 servers with Server 2012.  This one server is an exact mirror of another server (hardware, software, everything) and that other server also works fine.

    Also, your link is about SCC and Endpoint.  My problem is with the FCS Client.

    Thanks for the reply though!

    Thursday, December 6, 2012 6:24 PM
  • Hi,

    Thank you for the update.

    FCS is not supported on windows server 2012/windows 8, so you need to update to FEP or SCEP. if you want to deploy FEP, please install this update adds: http://support.microsoft.com/kb/2758685. As for install FCS on image machine, the duplicate SUSClientID would be affect, you need to delete the SUSClientID before imaging.

    http://support.microsoft.com/kb/903262

    Regards,


    Nick Gu - MSFT


    Friday, December 7, 2012 2:54 AM
  • So then I'm not going to get any help from Microsoft. "Not supported" and "doesn't work" are two completely different things. FCS works on Server 2012 and Win8. I've got 9 months of solid testing to attest to that. In addition to my 24 servers I also have over 100 Win8 machines running FCS just fine. I figured official support would come later after it's release like Exchange 2010 eventually will. Which is why we decided to move forward with it. I guess not.

    There is no such thing as updating to FEP. You need to buy it. We are in no position to write a check for something simply because Microsoft choose to not support a product that works just fine. As for this machine, I guess I'll just have to reload it. Clearly something has just gone wrong with it.

    I'll just have to deal with a product that works with no support until we can buy something else.

    Unfortunately your second link has nothing to do with this. What was that for? I don't think you understood what I meant by "mirror". I was simply stating they are identical spec wise.

    EDIT:

    Typical, reloaded and working fine.  I hate having that as an answer but it doesn't look like anyone will able to figure this out without official support to back it up.

    • Edited by JEmlay Saturday, December 8, 2012 12:34 AM
    • Marked as answer by JEmlay Saturday, December 8, 2012 12:34 AM
    Friday, December 7, 2012 5:44 PM