locked
Selecting product Office 2016 causes sync failure RRS feed

  • Question

  • I'm have SCCM 1802 and WSUS installed on a fully patched Windows Server 2012R2 VM. The Software Update Point role is installed and synchronizations work fine except if I select the product Office 2016. Selecting other versions of Office (2010, 2013) work but not 2016.

    If I select Office 2016, these errors appear in wsyncmgr.log:

    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
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=[SCCM-SERVER.FQDN] SITE=XXX PID=2012 TID=3404 GMTDATE=Thu Sep 06 20:56:32.583 2018 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
    Sync failed. Will retry in 60 minutes

    This is an excerpt from SoftwareDistribution.log

    2018-09-06 20:56:29.801 UTC	Error	WsusService.53	SoapUtilities.LogException	USS ThrowException: Actor = https://fe2.update.microsoft.com/v6/ServerSyncWebService/ServerSyncWebService.asmx, Method = "http://www.microsoft.com/SoftwareDistribution/GetUpdateData", ID=7d349caf-0978-42cd-9460-e45ca5ec57a7, ErrorCode=InternalServerError, Message=
       at Microsoft.UpdateServices.Internal.SoapUtilities.LogException(SoapException e)
       at Microsoft.UpdateServices.Internal.WebServiceCommunicationHelper.ProcessWebServiceProxyException(SoapHttpClientProtocol& webServiceObject, Exception exceptionInfo)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List`1 allMetadata, List`1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProcess()
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2018-09-06 20:56:29.801 UTC	Error	WsusService.53	SoapUtilities.LogException	USS ThrowException: Actor = https://fe2.update.microsoft.com/v6/ServerSyncWebService/ServerSyncWebService.asmx, Method = "http://www.microsoft.com/SoftwareDistribution/GetUpdateData", ID=7d349caf-0978-42cd-9460-e45ca5ec57a7, ErrorCode=InternalServerError, Message=
       at Microsoft.UpdateServices.Internal.SoapUtilities.LogException(SoapException e)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProcess()
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2018-09-06 20:56:29.801 UTC	Info	WsusService.53	CatalogSyncAgentCore.UpdateSyncResultAndGenerateReportingEvent	CatalogSyncThreadProcess: report subscription USS internal error
    2018-09-06 20:56:29.801 UTC	Info	WsusService.53	EventLogEventReporter.ReportEvent	EventId=386,Type=Error,Category=Synchronization,Message=Synchronization failed. Reason: Fault occurred.
    2018-09-06 20:56:29.801 UTC	Info	WsusService.50	ThreadEntry	ThreadHelper.ThreadStart
    2018-09-06 20:56:29.801 UTC	Info	WsusService.50	CatalogSyncAgent.WaitUntilSyncFinishedOrCancelled	Agent signalled done.
    2018-09-06 20:56:29.801 UTC	Info	WsusService.50	CatalogSyncAgent.SetSubscriptionStateWithRetry	Firing event SyncFailToStart...
    2018-09-06 20:56:29.817 UTC	Info	WsusService.50	CatalogSyncAgent.WakeUpWorkerThreadProc	Found no more jobs. CatalogSyncAgent quits but will run rollup before terminating ...
    2018-09-06 20:56:29.817 UTC	Info	WsusService.50	CatalogSyncAgent.UpdateServerHealthStatusBasedOnError	ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running

    I've tried running wsusutil.exe reset but it doesn't make any difference. I removed SUP role, uninstalled WSUS then added WSUS and SUP role again, this also didn't make a difference.

    I do not have the Upgrades classification selected.

    Any suggestions?


    • Edited by oxfordtom Thursday, September 6, 2018 9:45 PM
    Thursday, September 6, 2018 9:36 PM

All replies

  • Hello sir,

    Glad to provide help with your issue.

    As far as i know, it is not only you who have encountered this issue. I have tested it earlier in my lab, and it fails as you describe. And there are more reports about it as following:

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

     

    It seems that some of the packages released in the 9/5 of the Office 2016 category have caused this problem. I have already reported this to MS, and I am sure they will solve it soon. Currently, I recommend not selecting Office 2016 for the time being to avoid failure and waiting for an official fix.
     
    Hope my answer could help you.
     
    Best Regards,
    Ray  


    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 7, 2018 12:50 AM
  • I've the same problem with two of my WSUS Servers. Windows Server 2016 and fully patched.
    Friday, September 7, 2018 7:01 AM
  • Glad it's not just me!

    Thanks for confirming, and especially for the link to the other thread.

    Friday, September 7, 2018 10:12 AM
  • I noticed the same issue with WSUS on 2008R2/2012R2 which started from 06/09/18. WebException timeout error. Tried to recheck Office 2016 and WSUS script to delete old and expired updates. No effects. Seems Microsoft update servers on maintenance to be ready for Windows 10 1809. Any comments?
    Saturday, September 8, 2018 10:53 AM
  • Syncing is now working for me.  I had the exact same issue.  No fixes resolved it.  Microsoft must have resolved the issue.  I'm not happy Bob.  Not happy.  Next time I'll check the forums first before I spend hours troubleshooting.
    Sunday, September 9, 2018 3:47 PM
  • Hello sir,

    It seems like that Microsoft has fixed this issue, and i could sync successfully in my lab now (9/10). So please check again in your environment again and it should work now.

     
    Hope my answer could help you.
     
    Best Regards,
    Ray  


    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by N. van Dael Monday, September 10, 2018 6:11 AM
    Monday, September 10, 2018 1:02 AM
  • Yes, all of our WSUS servers syncs again at this time.

    Looks it has been solved by Microsoft.

    Monday, September 10, 2018 6:09 AM