{"id":6860,"date":"2018-09-06T16:15:53","date_gmt":"2018-09-06T14:15:53","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=6860"},"modified":"2024-10-01T15:19:45","modified_gmt":"2024-10-01T13:19:45","slug":"office-2016-september-3-2018-updates-breaks-wsus-sync","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2018\/09\/06\/office-2016-september-3-2018-updates-breaks-wsus-sync\/","title":{"rendered":"Office 2016 September 4, 2018 updates breaks WSUS sync"},"content":{"rendered":"

\"Windows[German<\/a>]Just a brief short note for administrators in WSUS environments observing synchronization failures since a few days. It's not your WSUS, it's probably caused by broken Office 2016 updates.<\/p>\n

<\/p>\n

\"\"Last Tuesday (09\/04\/2018) Microsoft released a new batch of non security updates for Microsoft Office (see my blog post Microsoft Office-Updates (September 3, 2018)<\/a>).<\/p>\n

WSUS fails during update synchronization<\/h2>\n

Shortly after my blog post was published, the first user comments<\/a> arrived within my German blog. Several users claiming, that these updates do not arrive at WSUS, due to the fact that WSUS couldn't synchronize. German blog reader Markus K. wrote:<\/p>\n

No Office updates were synced on WSUS v3.x (2008 R2), no success manually either. The synchronization fails.<\/p>\n

The WSUS v10.x (Server 2016) has received all Office updates.<\/p><\/blockquote>\n

This is not an isolated case, as other users confirm this error. At first glance, it looks as if only WSUS v3.x under Windows Server 2008 R2 is affected. But also the Small Business Server 2011 with WSUS 3.x and Windows Server 2012 R2 are probably affected. The same applies to Windows Server 2016 with WSUS v10.0.14393.2007 (although Marcus wrote above, that his Windows Server 2016 managed the synchronization).<\/p>\n

It's probably Office 2016 updates<\/h2>\n

German blog reader Michael R. mentioned within this comment<\/a>, that there is a problem with the new Office 2016 updates released by Microsoft on Sept. 4, 2018. Michael wrote:<\/p>\n

This is probably a problem with the new Office 2016 updates.
\nAfter removing Office 2016 from the product selection in WSUS, synchronization with Microsoft works again. I manually imported the missing Office 2016 updates.<\/p><\/blockquote>\n

He left a link to this Technet forum thread<\/a> at Microsoft, where the issues has been discussed also. I guess, blog reader Markus K. mentioned above is the thread starter. He wrote:<\/p>\n

as of today synchronization fails on our 2008 R2 v3.x WSUS (2016 v10.x WSUS synced fine!) with following error:<\/p>\n

SoapException: Fault occurred at
\nSystem.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse
\n(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at
\nSystem.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.
\nServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds) at
\nMicrosoft.UpdateServices.ServerSync.CatalogSyncAgentCore.
\nWebserviceGetUpdateData(UpdateIdentity[] updateIds, List`1 allMetadata, List`1 allFileUrls, Boolean isForConfig) at
\nMicrosoft.UpdateServices.ServerSync.CatalogSyncAgentCore.
\nGetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData) at
\nMicrosoft.UpdateServices.ServerSync.CatalogSyncAgentCore.
\nExecuteSyncProtocol(Boolean allowRedirect)<\/p><\/blockquote>\n

There is an error reported in the SOAP connection used by WSUS to the Microsoft servers. In the error string, I still mean that the synchronization fails when retrieving the metadata. If you go through the thread in the Technet forum, you will find a post where a user reached a partial synchronization:<\/p>\n

Just tried again: the Synchronisation now works up to about 20% and then stops with the same error message. Then I deselected the updates for Office 2002-2016 in products\/classifications and tried to synchronize again and everything now works fine. So there seems to be an error in the Office update files.<\/p><\/blockquote>\n

From that point on, 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.<\/p>\n

Addendum:<\/strong> Microsoft has re-released some Office 2016 updates – maybe it fixes some issues, see\u00a0Fix for Office 2016 updates related WSUS sync issues?<\/a><\/p>\n

Similar articles:<\/strong>
\nOffice 2016 September 3, 2018 updates breaks WSUS sync<\/a>
\nWindows 10: Flash update for Insider and more WSUS issues
\nIs Windows Server 2019 Essentials the last one?<\/a>
\nWindows Defender reports osk.exe as malware<\/a>
\nWindows 10 Support extended to 30 months (sometimes)<\/a>
\nWow! Windows 7 get extended support until January 2023<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Just a brief short note for administrators in WSUS environments observing synchronization failures since a few days. It's not your WSUS, it's probably caused by broken Office 2016 updates.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,11,22],"tags":[47,125,195,569],"class_list":["post-6860","post","type-post","status-publish","format-standard","hentry","category-issue","category-office","category-update","tag-issue","tag-office","tag-update","tag-wsus"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/6860","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=6860"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/6860\/revisions"}],"predecessor-version":[{"id":35166,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/6860\/revisions\/35166"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=6860"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=6860"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=6860"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}