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
  • Born: September non-security Office updates blamed for WSUS synchronization failures

    Posted on September 6th, 2018 at 10:01 woody Comment on the AskWoody Lounge

    It looks like this may have just been solved, but Günter Born reports that this month’s non-security Office patches are causing update server synchronization failures:

    There is an error reported in the SOAP connection used by WSUS to the Microsoft servers.

    it was clear that it had to do with the Office patchday and the released updates. Further attempts were made to narrow down the Office 2016 category updates as a root cause. As soon as users remove this category from the update synchronization, the synchronization works again.

    Anybody else seeing the problem?

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

    Home Forums Born: September non-security Office updates blamed for WSUS synchronization failures

    This topic contains 28 replies, has 9 voices, and was last updated by  anonymous 1 week, 4 days ago.

    • Author
      Posts
    • #215612 Reply

      woody
      Da Boss

      It looks like this may have just been solved, but Günter Born reports that this month’s non-security Office patches are causing update server synchron
      [See the full post at: Born: September non-security Office updates blamed for WSUS synchronization failures]

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

      JCCWsusser
      AskWoody Lounger

      No problem on mine, v6.2 with Office 2016 enabled. Worked every night for last 2 weeks.

    • #215625 Reply

      anonymous

      I’ve had sync errors on WSUS, got Office 2010 updates but not newer versions. The other updates (Win7, Win10, .Net, IE11) came down even with sync errors, i’m pushing them out without the missing Office updates.

      July updates also showed up, along with August in WSUS, I declined all July updates.

    • #215633 Reply

      jabeattyauditor
      AskWoody Lounger

      No issues here – WSUS running on Server 2016 with Windows 7 Pro and 10 Pro (1803) clients, most with MSI-based Office 2016 installed. Everything is syncing properly.

    • #215651 Reply

      anonymous

      Thanks! I thought my WSUS was syncing correctly (MMC for WSUS sated it had succeeded), but if I manually synced, it stalled at 0% and never finished. I had to unselect Office 2016 product, sync, reselect Office 2016, and then re-sync. WSUS is on Windows Server 2012 R2. Thank you!

    • #215769 Reply

      ch100
      AskWoody MVP

      It happens on 2012R2 WSUS but not 2016 WSUS. The reason is different entry for the MUURL in the WSUS database. Why do they use different update URLs?

    • #215777 Reply

      gborn
      AskWoody MVP

      It happens on 2012R2 WSUS but not 2016 WSUS. The reason is different entry for the MUURL in the WSUS database. Why do they use different update URLs?

      I’ve seen also reports claiming the same issue with 2016 WSUS.

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

      anonymous

      Initially opened the thread in the technet forums.

      https://social.technet.microsoft.com/Forums/en-US/7dda7d74-f900-448e-9257-246def7517a9/2008r2-wsus-v327600283-sync-error-starting-with-september-5th-2018?forum=winserverwsus

      So lets see if on PatchTuesday the problems are resolved. A manual import of Office 2016 updates won’t make anyone happy…

    • #215918 Reply

      anonymous

      Three independent 2012R2 WSUS servers here.  One has Office products selected including 2016.  The other two servers have no Office products selected.

      All three have been experiencing synch failures since 9/6/18 ~18:00 EDT and continue to do so now 9/7/18 ~13:30 EDT.

      From our point of view this is not related to Office / Office 2016 selection.

      Jim

      • #215939 Reply

        anonymous

        I concur…I have this same issue across all 2012 and 2016 WSUS instances I manage.  Manual sync does not work whether you select or unselect Office 2016 or any older versions.  What is the fix for this?  Do we just wait for MS to issue a patch for WSUS?

    • #215960 Reply

      nazzy
      AskWoody Lounger

      Our 2016 WSUS server has been failing syncs since late-evening of 9/6.

      Update:  unchecking the “Office 2016” product in Products & Classifications in WSUS options  does NOT fix the sync problem.  Stays at “Synchronizing 0%”   🙁

      Also tried restarting WSUS service several times to no avail.

      • This reply was modified 2 weeks, 2 days ago by  Kirsty.
      • This reply was modified 2 weeks, 2 days ago by  Kirsty.
      • This reply was modified 2 weeks, 2 days ago by  nazzy.
      • #215990 Reply

        ch100
        AskWoody MVP

        I think there is a way around it by setting the sync to manual and switch on and off to reset the server. Regardless, it should be resolved by now and I believe this is related to the preparations for the imminent release of 1809 which somehow failed, but it would not be for the first time.
        Has anybody noticed the release of Flash updates for 1809 in WSUS or SCCM?
        Date released 7/09/2018 (7th September in non-US date format)
        2018-08 Security Update for Adobe Flash Player for Windows 10 version 1809 KB4460093
        in three versions, one for each CPU architecture.

        EDIT: Now Windows 2016 seems to be failing, but the reasons are likely different, related as I mentioned to the release of the new OS. Need some patience and do not change any settings unless Microsoft advises to do so.

        • This reply was modified 2 weeks, 2 days ago by  ch100.
      • #216065 Reply

        gborn
        AskWoody MVP

        Our 2016 WSUS server has been failing syncs since late-evening of 9/6. Update: unchecking the “Office 2016” product in Products & Classifications in WSUS options does NOT fix the sync problem. Stays at “Synchronizing 0%” . Also tried restarting WSUS service several times to no avail.

        It seems, that there is a new sync issue with WSUS since Sept. 6th 2018. You haven’t posted some error details, but I guess, it’s a WebException timeout error. I’ve covered this within my new article Windows 10: Flash update for Insider and more WSUS issues

        • This reply was modified 2 weeks, 1 day ago by  gborn.
        • This reply was modified 2 weeks, 1 day ago by  Kirsty.
    • #216052 Reply

      anonymous

      Now seems to be failing on Server 2008, 2008R2, 2012R2 and 2016, but not every server, every time. Removing Office 2016 initially seemed to solve things, but now seems to make no difference.

    • #216071 Reply

      columbia2011
      AskWoody Lounger

      My WSUS servers on 2008R2 and 2012R2 failed to sync since 07/09/18. Does somebody get any info about issue from Microsoft? I don’t want manually import any updates from catalogue on Patch Tuesday.

    • #216079 Reply

      anonymous

      Magically resolved for me… no entry in the WSUS blog! I call that transparent….

    • #216091 Reply

      anonymous

      2016 Server has not sync’ed since 9/6.  Tried all the recommendations..office deselect, memory pool adjustments reboot and nothing helps.  I also tried a manual import of the latest security essentials definitions and it will not work either.

    • #216135 Reply

      columbia2011
      AskWoody Lounger

      Did anybody get an official answer from Microsoft about WSUS sync issue? Will they solve a problem before patch Tuesday?!

    • #216272 Reply

      columbia2011
      AskWoody Lounger

      Colleagues, can you check the progress of the synchronization for today? I still have the event log all red from 07/09/18 and the synchronization is in the Failed state. I want to clarify: it’s just me or everyone? I’m in Eastern Europe.
      —–
      WebException: The operation has timed out
      at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
      at Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)
      at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
      at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetRevisionIdList(Cookie cookie, ServerSyncFilter filter)
      at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetRevisionIdList(ServerSyncFilter filter, Boolean isConfigData)
      at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

      • #216346 Reply

        ch100
        AskWoody MVP

        It is everyone on and off.
        Do not change any setting on your side.

    • #216308 Reply

      anonymous

      We had a 2016 WSUS server that would not sync since 9/6. This morning it finally completed a sync at 5:30am est. It also completed a manual sync as well. I had tried all the recommendation over the past few days and nothing had worked. Microsoft must have done something on their side…

    • #216366 Reply

      columbia2011
      AskWoody Lounger

      I confirmed that WSUS is working fine. Service restored. Synchronization is working. I have not doing anything in configurations.There are no errors. Since morning. Microsoft has done something on Update Servers.

    • #216475 Reply

      PerthMike
      AskWoody Lounger

      Started to fail on my WSUS server on 09/07, passed once on the 8th, then failed again. Removed Off16 this morning for a manual synch, worked… Added Off16 back in, manual synch, still working!

      Happy days.

       

      No matter where you go, there you are.

      • #216476 Reply

        PerthMike
        AskWoody Lounger

        Further, when the synch worked again after adding Off16 back in, it showed two expired Off16 updates, KB4018385 (32bit and 64bit flavours). Could be that those expiries (expirings?) are choking the chutes.

        No matter where you go, there you are.

    • #216506 Reply

      anonymous

      Win2012R2 -synchronizations on 7-th and 8-th of September failed, it started to sync correctly on 9-th. There was no config change or reboot on WSUS server.

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

      nazzy
      AskWoody Lounger

      UPDATE: WSUS 2016

      Autosync on 9/7:  after several sync failures during the day, we had a successful sync at 11:20 pm PST

      Autosync on 9/9, after several sync failures during the day, we had a successful sync at 11:20 pm PST

      Manual sync on 9/10 at 10:40 am PST,  successful sync.

      No changes to wsus server, no reboots.  Office 2016 product had always been checked.

      I believe the problem is/was on Microsoft’s end.

      • This reply was modified 1 week, 6 days ago by  nazzy.
      1 user thanked author for this post.
      • #216965 Reply

        anonymous

        Ongoing Sync issues for me.
        Win 2012 R2

        Failed from 7/9/2018 to 9/9/2018
        worked 10th and 11th
        Failing again on the 12th.

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

    Reply To: Born: September non-security Office updates blamed for WSUS synchronization failures

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

    Your information: