[German]A short message for administrators who use WSUS for update distribution. Currently there seems to be synchronization issues with WSUS (various versions) as well as SCCM again. Here is some information about this topic. Addendum: Might be fixed.
WSUS sync – issues in Sept. 2018
Issues with the synchronization of the WSUS are nothing really new. I had pointed out such a case in early September in the blog post Office 2016 September 4, 2018 updates breaks WSUS sync. After the release of Microsoft’s September 2018 updates, administrators discovered that WSUS failed to synchronize updates. New updates do not arrive at WSUS or are not synchronized. Those affected had error logs of this type:
SoapException: Fault occurred at
(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters) at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.
ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity updateIds) at
WebserviceGetUpdateData(UpdateIdentity updateIds, List`1 allMetadata, List`1 allFileUrls, Boolean isForConfig) at
GetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData) at
After some time Microsoft got these problems under control, so that WSUS works again.
WSUS Sync issues since December 4, 2018?
I don’t use WSUS, so I just publish my observations. Since a few hours, some new comments arrived at my blog post Office 2016 September 4, 2018 updates breaks WSUS sync, claiming WSUS sync issues again. A user writes:
Server 2019 with WSUS 10.0.17763.1, same problem, unchecked Office 2016, Office 365 client and Office 2019 – still same problem.
Syncronizing 0% – then fails.
If I uncheck “everything” then only check “Windows” it syncronizes 24 % then fails.
Another user reported problems with Windows Server 2016 WSUS 10.0.14393.2007. The Microsoft update URL https[://]fe2.update[.]microsoft[.]com causes trouble when synchronizing. This seems to be responsible for the synchronization of the Windows 10 updates. If it deselects the Windows 10 updates, WSUS can synchronize again.
Microsoft has cloud issues again
This time, the cause seems to be cloud related that occur at Microsoft. In this comment user Andre points out a discussion at reddit.com. Two days ago, an affected person reported that his WSUS had a synchronization error and is causing the following error.
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.
Here the deselection of components has not brought any improvement. However, the reddit.com thread contains the information that Microsoft has issues with its Azure servers that provide updates for WSUS.
Microsoft Premier Support has confirmed it’s a bug on their end. No ETA yet on a resolution.
So it’s a bug on the part of Microsoft – so you couldn’t do anything. When the bug is fixed is not known at the moment.
Addendum: Microsoft fixed the issue
Within this Technet forum thread users also discuss the issue. Microsoft employee Ray Jia then posted that the issue had been fixed:
Microsoft has fixed it and the sync works now. However, it is not the first time that one product causes the synchronizing failure. In my memory, it is office 2016 last time.
Cookies helps to fund this blog: Cookie settings