Home

SCCM 1806 "Failed to sync update" message in wsyncmgr.log

%3CLINGO-SUB%20id%3D%22lingo-sub-299048%22%20slang%3D%22en-US%22%3ESCCM%201806%20%22Failed%20to%20sync%20update%22%20message%20in%20wsyncmgr.log%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299048%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAll%20servers%20in%20the%20environment%20(%26nbsp%3BSite%20Server%2C%20SUS%20server%2C%20DP%2C%20and%20Db%20server)%26nbsp%3B%20are%20Server%202016%2C%20patches%20up-to-date%2C%20servers%20running%201806%2C%20including%20the%20hotfix.%26nbsp%3B%20No%20error%20messages%20in%20the%20relevant%20log%20files%20except%20for%20the%20Wsyncmgr.log%20file(below).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20is%20the%20first%20month%20of%20attempting%20to%20work%20with%20SCCM%20to%20perform%20Software%20Updates%2C%20therefore%2C%20and%20deploying%20has%20not%20been%20achieved%20yet.%20%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20include%20Update%20Rollups%20to%20my%20selected%20classifications%20and%20run%20a%20synchronization%2C%20I%20will%20always%20receive%20a%20Synchronization%20failure%20with%20an%20error%20code%20of%200X80131500%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20cleared%20out%20the%20classifications%20from%20my%20Software%20Update%20Point%20by%20modifying%20the%20properties.%26nbsp%3B%20Re-ran%20the%20synchronization%20and%20this%20allowed%20the%20synchronization%20to%20work.%26nbsp%3B%20I've%20had%20the%20following%20selected%20in%20classifications%20and%20the%20sync%20works%26nbsp%3B%20%22Critical%20Updates%2C%20Definition%20Updates%2C%20Security%20Updates%2C%20Tools%2C%20and%20Updates.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20run%20the%20WSUSUtil.exe%20Reset%26nbsp%3B%20and%20this%20didn't%20help.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20a%20Server%202016%20environment%2C%20patches%20up-to-date%2C%20server%20running%201806%2C%20including%20the%20hotfix.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EIn%20the%20Wsyncmgr.log%20file%20on%20the%20site%20server%3C%2FSTRONG%3E%2C%20I%20have%20errors%20like%20the%20following%3A%3C%2FP%3E%3CP%3ESync%20failures%20summary%3A%26nbsp%3BSMS_WSUS_SYNC_MANAGER%26nbsp%3B12%2F10%2F2018%204%3A09%3A49%20AM%26nbsp%3B8364%20(0x20AC)%3CBR%20%2F%3EFailed%20to%20sync%20update%20f13ddae9-edf3-4b5b-a874-14f35a089e8b.%20Error%3A%20The%20Microsoft%20Software%20License%20Terms%20have%20not%20been%20completely%20downloaded%20and~~cannot%20be%20accepted.%20Source%3A%20Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow%26nbsp%3BSMS_WSUS_SYNC_MANAGER%26nbsp%3B12%2F10%2F2018%204%3A09%3A49%20AM%26nbsp%3B8364%20(0x20AC)%3CBR%20%2F%3EFailed%20to%20sync%20update%205e174b97-938e-41b7-9428-b2f9978ddd2d.%20Error%3A%20The%20Microsoft%20Software%20License%20Terms%20have%20not%20been%20completely%20downloaded%20and~~cannot%20be%20accepted.%20Source%3A%20Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow%26nbsp%3BSMS_WSUS_SYNC_MANAGER%26nbsp%3B12%2F10%2F2018%204%3A09%3A49%20AM%26nbsp%3B8364%20(0x20AC)%3CBR%20%2F%3EFailed%20to%20sync%20update%20359c5eeb-b7ff-447a-9986-5d6283a133f3.%20Error%3A%20The%20Microsoft%20Software%20License%20Terms%20have%20not%20been%20completely%20downloaded%20and~~cannot%20be%20accepted.%20Source%3A%20Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow%26nbsp%3BSMS_WSUS_SYNC_MANAGER%26nbsp%3B12%2F10%2F2018%204%3A09%3A49%20AM%26nbsp%3B8364%20(0x20AC)%3C%2FP%3E%3CP%3EHowever%2C%20when%20I%20select%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-299048%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECM%20current%20branch%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-304772%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%201806%20%22Failed%20to%20sync%20update%22%20message%20in%20wsyncmgr.log%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304772%22%20slang%3D%22en-US%22%3EPrior%20to%20submitting%20my%20issue%20to%20the%20community%2C%20I%20researched%20this%20problem%20online%20for%20about%2025%20hours.%20I%20did%20come%20across%20the%20article%20and%20determined%20that%20that%20was%20not%20my%20solution%20since%20my%20security%20settings%20were%20the%20same.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-304614%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%201806%20%22Failed%20to%20sync%20update%22%20message%20in%20wsyncmgr.log%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304614%22%20slang%3D%22en-US%22%3E%3CP%3Ehave%20you%20checked%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.systemcenterdudes.com%2Fthe-microsoft-software-license-terms-have-not-been-completely-downloaded%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.systemcenterdudes.com%2Fthe-microsoft-software-license-terms-have-not-been-completely-downloaded%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
SMCC_SCCM_admin
New Contributor

 

All servers in the environment ( Site Server, SUS server, DP, and Db server)  are Server 2016, patches up-to-date, servers running 1806, including the hotfix.  No error messages in the relevant log files except for the Wsyncmgr.log file(below).

 

This is the first month of attempting to work with SCCM to perform Software Updates, therefore, and deploying has not been achieved yet.  

 

If I include Update Rollups to my selected classifications and run a synchronization, I will always receive a Synchronization failure with an error code of 0X80131500

 

I've cleared out the classifications from my Software Update Point by modifying the properties.  Re-ran the synchronization and this allowed the synchronization to work.  I've had the following selected in classifications and the sync works  "Critical Updates, Definition Updates, Security Updates, Tools, and Updates."

 

I've run the WSUSUtil.exe Reset  and this didn't help.

 

This is a Server 2016 environment, patches up-to-date, server running 1806, including the hotfix.

 

In the Wsyncmgr.log file on the site server, I have errors like the following:

Sync failures summary: SMS_WSUS_SYNC_MANAGER 12/10/2018 4:09:49 AM 8364 (0x20AC)
Failed to sync update f13ddae9-edf3-4b5b-a874-14f35a089e8b. Error: The Microsoft Software License Terms have not been completely downloaded and~~cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow SMS_WSUS_SYNC_MANAGER 12/10/2018 4:09:49 AM 8364 (0x20AC)
Failed to sync update 5e174b97-938e-41b7-9428-b2f9978ddd2d. Error: The Microsoft Software License Terms have not been completely downloaded and~~cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow SMS_WSUS_SYNC_MANAGER 12/10/2018 4:09:49 AM 8364 (0x20AC)
Failed to sync update 359c5eeb-b7ff-447a-9986-5d6283a133f3. Error: The Microsoft Software License Terms have not been completely downloaded and~~cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow SMS_WSUS_SYNC_MANAGER 12/10/2018 4:09:49 AM 8364 (0x20AC)

However, when I select 

2 Replies
Prior to submitting my issue to the community, I researched this problem online for about 25 hours. I did come across the article and determined that that was not my solution since my security settings were the same.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
38 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
12 Replies