WSUS sync issue

WSUS sync issue Event ID 10022, log error:

2018-09-04 09:42:41.059 UTC Error WsusService.60 SoapUtilities.LogException USS ThrowException: Actor = , Method = "http://www.microsoft.com/SoftwareDistribution/GetUpdateData", ID=349eb315-f9da-4550-82c5-f31a8b977c0d, ErrorCode=InvalidCookie, Message=Cookie decryption failed. Error: Deserialization failed after decryption. Error: invalid header
Parameter name: buffer.
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.GetAndSaveUpdateMetadata(List`1 updates)
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()

Restarted services, disabled windows firewall, the sync starts and then stops at random % completions and doesn't complete

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Craig SummersAuthor Commented: 2018-09-04

I removed the drivers from the classifications and the sync ran successfully. I have added them back in now and running it again to see what happens.WSCONTENT folder has new modified dates after the successful run, nothing yet, currently at 41% sync after adding drivers back, but it has failed at 80% before

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial

rahul yadavCommented: 2018-09-04

When synchronization fails, status message ID 6703 is created by WSUS Synchronization Manager (the SMS_WSUS_SYNC_MANAGER component in Component Status) and log file entries are recorded on the site server. Status message ID 6703 contains different error messages depending on the problem that occurs.

LVL 48

DonNetwork AdministratorCommented: 2018-09-05

Have you tried unchecking critical updates(temporarily) ?

https://www.reddit.com/r/SCCM/comments/9d4u6q/software_update_point_sync_fail_just_me/?sort=new

LVL 37

Seth SimmonsSr. Systems AdministratorCommented: 2018-10-31

No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: Craig Summers (https:#a42671958)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer

WSUS sync issue

Who is Participating?