locked
SUP Sync failing RRS feed

  • Question

  • Hi All,

    I have a standalone primary 2012 R2 site with WSUS installed on the same box.

    I am trying to run a SUP sync and getting the following failure.

    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 1/13/2015 12:31:16 PM 6928 (0x1B10)
    sync: WSUS synchronizing categories SMS_WSUS_SYNC_MANAGER 1/13/2015 12:31:19 PM 6928 (0x1B10)
    Sync failed: UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 1/13/2015 12:31:23 PM 5400 (0x1518)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SCCM.manishlab.local SITE=ETS PID=2264 TID=5400 GMTDATE=Tue Jan 13 20:31:23.357 2015 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 1/13/2015 12:31:23 PM 5400 (0x1518)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 1/13/2015 12:31:23 PM 5400 (0x1518)

    There are no errors in Wsusctrl or in WCM.log

    Can you please help?

    Thanks in advance

    Manish


    Tuesday, January 13, 2015 9:16 PM

Answers

  • UPDATE: Microsoft Update Service came back 10 minutes ago and should now be available again.

    Happy Patching!

    HTH, Captain MESO

    • Marked as answer by ManishTyagi123 Wednesday, January 14, 2015 2:23 PM
    Wednesday, January 14, 2015 2:30 AM

All replies

  • Hi,

    I actually get the same message on my Standalone WSUS right now as well, it worked 2 hours ago, so I am suspecting that there could be an issue with the Windows Update service, as it is patch tuesday could be that it is under heavy load.

    Have it worked before?

    Regards,
    Jörgen 


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Tuesday, January 13, 2015 9:43 PM
  • I'm getting the same thing.  It was syncing a few hours ago -now it's not.
    Tuesday, January 13, 2015 9:48 PM
  • I could confirm this. WSUS stopped syncing 4 hours ago with "The upstream server experienced an unexpected error. Please try again at a later time".

    Windows Update Service at Microsoft seems to be down.

    Regards,
    Captain MESO

    Tuesday, January 13, 2015 10:59 PM
  • Also having the same error right now...
    Wednesday, January 14, 2015 12:42 AM
  • Same here, and still having trouble. Windows Server 2012 R2 WSUS.
    Wednesday, January 14, 2015 1:32 AM
  • I have a similar problem. It's nice to think that it might be a problem with Microsoft Updates, and not my server. But, I really need to have a synchronization happen overnight. Please look into this, Microsoft!
    Wednesday, January 14, 2015 1:47 AM
  • UPDATE: Microsoft Update Service came back 10 minutes ago and should now be available again.

    Happy Patching!

    HTH, Captain MESO

    • Marked as answer by ManishTyagi123 Wednesday, January 14, 2015 2:23 PM
    Wednesday, January 14, 2015 2:30 AM
  • I can confirm that my WSUS server is syncing right now, too.

    Cheers!

    Wednesday, January 14, 2015 2:32 AM
  • I too had the issue but it's now up and running.

    Manish, can you confirm that it's fixed on your side so that the thread be closed ?

    Thanks.


    Benoit Lecours | Blog: System Center Dudes


    Wednesday, January 14, 2015 1:57 PM
  • Hi All,

    Thanks for the response.

    I unchecked the  feature pack from SUP classifications and then I was able to run the sync without any issues,

    Not sure if changing the SUP classifications resolved the issue or it got resolved on its own.

    But anyways thank you once again.

    Yes Benoit, we can close this thread now.

    Thanks

    Manish

    Wednesday, January 14, 2015 2:11 PM
  • Resolved now. try it now
    Wednesday, December 7, 2016 4:39 AM