WSUS Sync failure

JimSym 201

SBS2011
WSUS 3.2.7600.226

WSUS sync has started to fail over the last few weeks, initially intermittentl, now I cannot get it to complete at all.
Update source is Microsoft

Console error: Unable to resolve the specified upstream server name.

“WebException: The request failed with HTTP status 404: Not Found.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(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.GetAuthConfig()
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

This seems to be the key bit of the server log

2021-02-06 07:51:26.046 UTC Info w3wp.29 ClientImplementation..ctor Initializing ClientWebService ProcessID = 18412, Process Start Time = 2/6/2021 6:17:59 AM, Product Version = 3.2.7600.325
2021-02-06 07:51:26.065 UTC Info w3wp.29 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
2021-02-06 07:51:26.362 UTC Info WsusService.18 SusService.ValidateServerCertificate CheckValidationResult Succeeds: CertOK
2021-02-06 07:51:26.366 UTC Info WsusService.18 ServerCertificateValidator.IsHostAllowedException Requested host: sws1.update.microsoft.com
2021-02-06 07:51:26.367 UTC Info WsusService.18 ServerCertificateValidator.VerifyServerCertificate SSL validation succeeded.
2021-02-06 07:51:26.546 UTC Warning WsusService.18 WebServiceCommunicationHelper.ProcessWebServiceProxyException ProcessWebServiceProxyException found Exception was WebException. Action: Retry. Exception Details: System.Net.WebException: The request failed with HTTP status 404: Not Found.

So it is connecting to sws1.update.microsoft.com, and SSL validation succeeds. It fails after that with some proxy error.

(I realise that this server should be replaced, and work is in hand to migrate to Azure.)

Any help appreciated. Have been unable to fault the installation.

Thanks

Sam 71 Reputation points

2021-02-09T01:43:37.167+00:00

Same issue here
WSUS Version: 3.2.7600.226
Windows Server 2008 R2 Enterprise

Failed 2021-02-04 06:56:44.560 UTC:

44.154 Info WsusService.19 SusService.ValidateServerCertificate CheckValidationResult Succeeds: CertOK
44.154 Info WsusService.19 ServerCertificateValidator.IsHostAllowedException Requested host: sws1.update.microsoft.com
44.154 Info WsusService.19 ServerCertificateValidator.VerifyServerCertificate SSL validation succeeded.
44.560 Warning WsusService.19 WebServiceCommunicationHelper.ProcessWebServiceProxyException ProcessWebServiceProxyException found Exception was WebException. Action: Retry. Exception Details: System.Net.WebException: The request failed with HTTP status 404: Not Found.

<snip>

Previous day's success was at 2021-02-03 06:29:56.530 UTC
Paul Kroitor 6 Reputation points

2021-02-10T20:05:31.847+00:00

Does anyone know if simply disabling the WSUS service on SBS2011 works?

We have other WSUS servers; switching the workstations to use them would be straightforward, I imagine, but what about switching the SBS box itself over to a different update server?
JimSym 201 Reputation points

2021-02-10T22:19:28.313+00:00

@Paul Kroitor ·

No need to disable. Re-point clients to new WSUS Server. Delete all computers in old WSUS. Change Sync in old WSUS to Manual (no schedule). It will just tick away idly.
Bob (ISI) 51 Reputation points

2022-01-19T15:51:43.367+00:00

Good day, is anyone having the same syncing issue from back last fall? Mine has quit for about 10 days now without any changes to configuration. Message indicating the MS update servers are too busy??

If anyone has any intel, please share.
Adam J. Marshall 9,386 Reputation points MVP

2022-01-19T16:34:15.947+00:00

WSUS 3 is dead (when attempting to sync directly to Microsoft)
https://www.ajtek.ca/blog/no-more-synchronization-for-wsus-3-0-service-pack-2/

47 answers

Adam J. Marshall 9,386 Reputation points MVP

2021-02-10T17:46:42.493+00:00

I've pinged my MVP contacts - let's see if that helps.
Please sign in to rate this answer.

4 people found this answer helpful.
Vandrey Trindade 86 Reputation points

2021-02-10T20:48:25.24+00:00

@Adam J. Marshall

if I import this month Windows 10 updates manually, by the time that Microsoft fix this, it will see that those updates are already there and approved?
BTW, thanks for the SSL tip. It didn't fix this specific problem, but at least my machines are searching for updates correctly and safer now =]

Adam J. Marshall 9,386 Reputation points MVP

2021-02-10T21:14:22.553+00:00

Yes, imported updates will stay and be accounted for when this is resolved.
Regarding the SSL - you should really watch that video on part 7 of my blog series - quite the eye opener of how if you don't have SSL enabled how they can do man in the middle attacks.

Adam J. Marshall 9,386 Reputation points MVP

2021-02-10T23:41:01.517+00:00

I take it since you're importing it, you've set the proper SchUseStrongCrypto for .NET.

If not, run the following from an Admin PowerShell Prompt:
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value "1" -PropertyType DWORD -Force

Vandrey Trindade 86 Reputation points

2021-02-11T12:21:14.813+00:00

Hi @Adam J. Marshall

I've just added it to the registry.
I'll boot the server and try again to check.

Vandrey Trindade 86 Reputation points

2021-02-11T12:52:12.22+00:00

Yup, same thing.
Error number: 80131509
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Shlomi Cohen 11 Reputation points

2021-02-07T12:08:27.827+00:00

I have the same issue.
It look like problem with the source server "Not found".
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Laszlo.Kakas 16 Reputation points

2021-02-07T12:34:34.32+00:00

Having the same issue here on SBS 2011. According to logs since: 2021-02-04 20:00:06.831 UTC
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Peter Groom 16 Reputation points

2021-02-08T04:29:55.417+00:00

Same issue here, SBS2011. Last successful sync was on 5/2/2021 but has been slowly failing for some time.
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
MartinBell 11 Reputation points

2021-02-10T17:01:19.59+00:00

Maybe it helps to raise attention by MS if every reader of this thread gives an upvote to the initial posting, here:
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

WSUS Sync failure

47 answers

Your answer