Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Massive (and frustrating!) sync failures with WSUS

    Posted on September 12th, 2018 at 09:41 woody Comment on the AskWoody Lounge

    Source: @jamiethornton

    I’m seeing reports all over the web about failed sync on WSUS servers, trying to roll out this month’s patches.

    SoapException: Fault occurred InvalidCookie

    InvalidOperationException: Client found response content type of ”, but expected ‘text/xml’.

    WebException: The operation has timed out.

    The problems arose before this month’s round of security patches — see Günter Born’s report — but admins are seeing even more occurrences since Tuesday.

    Removing Office 2016 and resyncing doesn’t seem to work.

    Anybody out there figure out a way to fix it?

    If that helped, take a second to support AskWoody on Patreon

    Home Forums Massive (and frustrating!) sync failures with WSUS

    This topic contains 15 replies, has 9 voices, and was last updated by  anonymous 1 month, 3 weeks ago.

    • Author
      Posts
    • #217034 Reply

      woody
      Da Boss

      I’m seeing reports all over the web about failed sync on WSUS servers, trying to roll out this month’s patches. SoapException: Fault occurred InvalidC
      [See the full post at: Massive (and frustrating!) sync failures with WSUS]

    • #217044 Reply

      Susan Bradley
      AskWoody MVP

      In the WSUS forums a Microsoft representative states:

       

      https://social.technet.microsoft.com/Forums/ie/en-US/e4eb2aec-229b-4d5c-8b83-01e2d90823d2/wsus-synchronisation-failed?forum=winserverwsus

       

      As far as i know, it is not only you who have encountered this issue. It seems that some of the packages released in the 9/5 of the Office 2016 category have caused this problem. ”

       

      Same issue as you. It seems that the KB4346783 can’t be sync due to a known issue which have not been fixed yet.”

       

      Susan Bradley Patch Lady

      2 users thanked author for this post.
    • #217064 Reply

      nazzy
      AskWoody Lounger

      Attached our corporate WSUS sync log.  I thought the sync issues were fixed after 9/9, but then we had a scheduled sync failure on 9/11, followed by a successful sync 30 mins later.  I have no doubt the problems are on Microsoft’s end and there’s nothing we admins can do until a fix is provided to us.

       

       

       

      Attachments:
      You must be logged in to view attached files.
      1 user thanked author for this post.
    • #217067 Reply

      dportenlanger
      AskWoody Lounger

      Our corporate WSUS servers were exhibiting the same behavior.  I tried the Office check/uncheck manual sync process and it didn’t solve the problem, so I turned Office back on and left it alone.

      Waiting a couple of days fixed the issue.  Literally, I did nothing but watch it for a couple of days and it started working.

      Go figure!

    • #217072 Reply

      mcbsys
      AskWoody Lounger

      On two small WSUS servers, I see sync failures Sept. 6-9, all successful starting Sept. 10.

    • #217104 Reply

      Susan Bradley
      AskWoody MVP

      My sync problems have cleared up, but I was having issues the other day.

      Susan Bradley Patch Lady

    • #217215 Reply

      PerthMike
      AskWoody Lounger

      I did the remove-Off16-synch-readd-Off16 trick on the 10th and it’s synched fine for me since.

      No matter where you go, there you are.

    • #217255 Reply

      Neil Gascoigne
      AskWoody Lounger

      Starting working again for us sometime between 0700 to 1900 (UTC) on 10th September. All synchronisations since then have been successful.

    • #217273 Reply

      anonymous

      Two of the wsus servers i look after stopped synching. On the old 2008 r2 server changing the microsoft url that it connected to in the database got it working again.

      For the 2016 server i did a dirty database check. After fixing that it started synching again.

      • #217282 Reply

        columbia2011
        AskWoody Lounger

        Post please the Microsoft url which you have corrected in the database and also steps to do it in database.

        • #217289 Reply

          anonymous

          Basically to connect to the database this explains it.

          And the sql script to update

          USE SUSDB;
          UPDATE dbo.tbConfigurationB
          SET MUUrl = ‘https://update.microsoft.com/v6’;

          You may want to record what your original url was in MUUrl.  Table tbConfigurationB only has one record so it is easy to look and copy the original url in case you want to go back to it.

          1 user thanked author for this post.
    • #218914 Reply

      nazzy
      AskWoody Lounger

      Getting intermittent sync failures again starting 9/17 for both scheduled AND manual syncs.  Can anyone else confirm?

    • #219061 Reply

      anonymous

      I can confirm that It was working up until 9/21/2018 then all day today fails WSUS sync

       

    • #219228 Reply

      anonymous

      Hi,

      I solved de-selecting Definition Updates” and forcing a manual synch.

      After that, I selected again “Definition Updates” and everything seems to be working as expected.

      Regards.

      P.S. No Office 2016 in my env, Wsus on Wind 2012 R2

      Red.

      1 user thanked author for this post.
    • #219368 Reply

      anonymous

      Hi,

      I de-select Office 2016 and Definition Updates and force a manual synch and it works fine.

      BRIII

       

    • #219373 Reply

      anonymous

      Hi,

      I confirm that only Definition Updates broke synch

      When I de-selct Definition Updates synch wroks

      When I select Definition Updates synch dont work

      BRIII

      1 user thanked author for this post.

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Massive (and frustrating!) sync failures with WSUS

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.

    Your information: