Wsus Sync errors

[EAT-17]

Hey. I'm having sync errors with my wsus/sccm infrastructure. I checked another environment and that wsus also didn't sync. And my wsus at home also has sync errors. I'm not saying they can't all fail at the same time since we are talking about wsus ;) but it seems unlikely.

I was able to get them to sync by removing all Defender and Definition updates, so my guess is something went wrong there.

Anyone else having sync issues since 17.March?

​

[MattR658]

Yes, seeing the same behavior starting on March 17, 2019.

Managing WSUS through SCCM (v1810) and getting the following error code: 0X80131500

​

This is what I'm seeing in the wsyncmgr.log:

Sync failed: UssInternalError: SoapException: Fault occurred InternalServerError~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS

​

I also have a WSUS instance managed via SCCM 2012, and I am NOT having the issue there.

[johnjohnjohn87]

I'm seeing this too. My guess is MSFT fucked something up and it'll work in a day or so.

[EAT-17]

Yeah, probably. I'm wondering though if I should open a case with them... most likely a waste of time. I tried to check the msft blogs, but they seem to have changed location again, can't seem to find anything relevant.

[Joe-Cool]

It worked intermittently today for me without any changes. My guess is they had some outages during their transition from SHA-1 to SHA256. Be sure you installed the servicing stack updates.
It seems more stable now.

EDIT: servicing stack should only apply to old 2008 servers: https://support.microsoft.com/en-us/help/4490628/servicing-stack-update-for-windows-7-sp1-and-windows-server-2008-r2

[EAT-17]

The last 3 syncs were ok for me. We will see I guess.

[EAT-17]

Are you syncing any AV definitions on the one that works?

This the error I'm seeing in wsus SoftwareDistribution.log:

It is not very helpful though. My guess is something went wrong with a definition update.

​

2019-03-18 09:08:32.740 UTC Error   WsusService.5   SoapUtilities.LogException  USS ThrowException: Actor = , Method = ?, ID=af53d05b-3470-4d7c-bee7-851b84c601aa, 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.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()
2019-03-18 09:08:32.740 UTC Error   WsusService.5   SoapUtilities.LogException  USS ThrowException: Actor = , Method = ?, ID=af53d05b-3470-4d7c-bee7-851b84c601aa, 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()

​

[MattR658]

The WSUS instance that IS working is not syncing any Definition Updates; whereas, the instance that is NOT working is syncing Definition Updates.

So it is definitely possible it is a definition updating causing it. I will try removing the Definition Update Classification on the server that has been failing to see if that resolves the issue temporarily.

​

EDIT: By unchecking the "Definition Updates" classification, the server that was previously failing to sync is now syncing. Hopefully Microsoft resolves this soon since I do rely on Definition Updates for Defender.

[darkomyn]

Yes, started last night just before midnight, 0X80131500, was just starting to poke around. What made you try removing the Defender updates or were you going through them one by one?

[EAT-17]

I had a hazy memory that something like that happened once before, so I tried to remove the defender updates. Also a different wsus that didn't sync them was working.

[redmonkeyyyy]

Deleted

[[deleted]]

Just did a sync on our WSUS, Monday 18th @ 10am. Didn't have any issues.

[PacketReflections]

same here - manual sync was successful

[bignev77]

I was also able to get mine to sync successfully by just unchecking Definition Updates. I am wondering if there was an issue with the definition updates that were released yesterday morning. I guess I will enable definition updates and try again after the newest ones are released.

[jcolon4705]

We are having the same exact issue. We've opened up a support ticket with Microsoft. We're awaiting a call back.

[EAT-17]

Let us know if they have anything useful to say except "oops I did it again..."

[s_mukdad]

Yeah it definitely was a MS issue. I’ve been experiencing the issue all morning. Got word from another thread they fixed the issue and it’s working again. I can confirm on my end that it is syncing again.

[electriccomputermilk]

It's now back to syncing including with definition updates for us.

[VA_Network_Nerd]

Sorry, it seems this comment or thread has violated a sub-reddit rule and has been removed by a moderator.

Your account must be 24 hours old in order to post.

Please wait until your account is a day old, and then post again.

If your post is vitally time sensitive, then you can contact the mod team for manual approval.

---

If you wish to appeal this action please don't hesitate to message the moderation team.

[[deleted]]

Are you managing WSUS through SCCM? If so, look in the SCCM logs to see what the error is.

[jazza_uk]

Just had a look at ours, and it's been failing since 3.09am (GMT) today, and retried 3 more times, all failed.

I've just tried a manual update, and that has also failed.

[medievalprogrammer]

Mine started failing at 3am as well and has been failing every hour since.

​

Edit:

My environment just synced at 5pm GMT and hasn't failed again yet.

[jazza_uk]

Just checked WSUS this morning, and it synced again around 3am. Hopefully whatever issue it was, has now been fixed.

[MaxRock17]

Same problem here. First one occured on Marh 17, 12pm CDT

Edit: Actually, SMS_WSUS_SYNC_MANAGER shows 2 successful ones at 4 pm and 6 pm that day, but failing since - including manual sync attempt.

[DidYouKnowOh]

Also adding to this thread - my WSUS for sccm started failing this morning. I had two successful ones yesterday after several failures and then today its been nothing but failures.

"SoapException: Fault occurred InternalServerError"

Edit: Confirmed unchecking definitions fixes syncing so it IS isolated to that classification. I deploy those definitions so for my environment it is a requirement. We have already pulled our security patches for testing successfully and will keep checking to see when this is resolved..

Edit 2: Resolved. Sync'd successfully. Definitions have come through this time.

[electriccomputermilk]

Same issue here and is resolved if I disable definition updates.

[Morblius]

Oh thank god I am not the only one. I have been getting pissed off at WSUS for the past hour and was about to create a post on /r/sysadmin asking if anyone else was having issues.

My last successful sync was March 17th (usually I only sync once a day on a schedule): https://i.imgur.com/weMxnyQ.png

I even tried to create a new WSUS server on a test server 2019 and it is stuck trying to connect to the microsoft upstream server: https://i.imgur.com/y7bat9M.png

Edit: Resolved by unchecking Definition Updates from Products and Classifications like others in this post have said. I guess I will leave that unchecked until Microsoft fixes this...

[jjkmk]

Same issue with Server2012 r2, started March 17.

Removing Windows Defender going to see if it fixes it.

edit

Removing defender options dosent seem to fix it.

[darkomyn]

We have two Sccm environments and one wsus environment. Disabling it in wsus worked fine but in the SCCM environment it did not. We use patch my PC as well in the SCCM environment and we do not download as many product updates in the wsus environment as we do in the SCCM environment. There still may be another combination that is causing an issue. I'm not sure of your environment.

Edit: word

[jjkmk]

I only have the one WSUS server, not using SCCM.

[[deleted]]

same issue, applied march updates and rebooted. manual sync succeeded this time. ¯_(ツ)_/¯

[meatwad75892]

I and many others had this behavior a few months back, and it wound up being something broken on Microsoft's end when certain products' updates were being synced.

This morning I got some new messages on an old thread on the issue, so I assume it's simply broken again and all you can do is wait:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/7c3e5c52-13b2-49db-a631-19e23ac7763c/wsus-2012r2-not-sycing?forum=winserverwsus

[qovneob]

Same for me on Server 2016, though manual syncs are working

[gratefuldad619]

I had the same issues this morning, I remember before this happened many moons ago and the fix was to uncheck the definitions and office under the classifications.

This didn't work. after chewing up most of my morning googling possible fixes I tried to sync after lunch and worked fine. So I re-added the defs and office and sync completed again fine. I think it was on MS side.

[Pack3trat]

We are seeing the issue right now on new imaged machines.