WSUS Sync failure

Anonymous

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?
Anonymous

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 11,031 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

Sam 71 Reputation points

2021-02-09T10:58:41.31+00:00

Hi RitaHu-MSFT.

I understand that 'Out-of-Support' is an important milestone, and I respect it. Microsoft can't be expected to support old things.
In common usage, a different milestone is 'End-of-Life' - that one has another meaning altogether.
Are you saying that because we have reached WSUS/win2008R2/SBS2011 'End-of-Support' that it's OK for WSUS to stop working?

It looks like a change at sws1.update.microsoft.com has killed the product. It is not End-of-Support, it is End-of-Life.
Worse still, that EoL breaks security patching for everything behind the WSUS server.
Was this answer helpful?

1 person 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.
Dale S 6 Reputation points

2021-02-09T02:28:42.547+00:00

We're having the same issue since 2021-02-05; our last successful sync was 2021-02-04 10:45:04.327 UTC.

WSUS Version: 3.2.7600.226
Windows Server 2008 R2 Standard

Our failures look like all the others in this thread. Our last successful looks like this:

2021-02-04 10:45:04.327 UTC Info WsusService.27 ServerCertificateValidator.IsHostAllowedException Requested host: sws1.update.microsoft.com
2021-02-04 10:45:04.327 UTC Info WsusService.27 ServerCertificateValidator.VerifyServerCertificate SSL validation succeeded.
2021-02-04 10:45:04.592 UTC Info WsusService.27 CatalogSyncAgentCore.SyncConfigUpdatesFromUSS Category Sync: Filter: <filter SyncAnchor="2021-02-02 18:45:03.336" GetConfig="1"></filter>
2021-02-04 10:45:05.076 UTC Info WsusService.27 CatalogSyncAgentCore.SyncConfigUpdatesFromUSS Need 182 config updates, 0 are new
2021-02-04 10:45:05.092 UTC Info WsusService.27 CatalogSyncAgentCore.SyncConfigUpdatesFromUSS Category Sync: New Config Anchor: 2021-02-03 18:45:04.645
Was this answer helpful?

1 person 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.
Adam J. Marshall 11,031 Reputation points MVP

2021-02-08T20:22:06.13+00:00

Also, possible issue here:
https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/wsus-synchronization-fails-with-soapexception
Was this answer helpful?

1 person found this answer helpful.
Anonymous

2021-02-08T20:28:29.233+00:00

Thanks

No, its not that one. If you look at the OP you will see it is succesfully connecting the correct MS server.
Requested host: sws1.update.microsoft.com

That is, correct according to that article!

Bob (ISI) 51 Reputation points

2021-02-08T21:31:51.853+00:00

I just checked the last forwarding traffic from my SBS when trying to sync with MS and it checked the following sites: I think these are current?

sws1.update.microsoft.com
statsfe2.update.microsoft.com
go.microsoft.com
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Adam J. Marshall 11,031 Reputation points MVP

2021-02-08T20:17:35.473+00:00

Do you have TLS1.0 enabled? If not, make sure you enable TLS1.0 and 1.1. If you recently disabled these to try to harden security on your server, this may be the reason.

Server 2012+ supports TLS 1.2, but I don't believe Server 2008 or 2008R2 does and you have to keep old TLS ciphers open.
Was this answer helpful?

1 person found this answer helpful.
Anonymous

2021-02-08T20:26:44.08+00:00

Thanks

No recent changes have been made to the installation, the TLS stuff was done ages ago.

Sync failure is a recent issue, and it looks to me like something at MS end, a redirect failing perhaps.

Jim

Bob (ISI) 51 Reputation points

2021-02-08T21:00:31.393+00:00

Does seem that way doesn't it Jim however we are quickly approaching a week since the last successful synchronization with MS. You would think they would have been on top of this issue by now with the number of SBS and 2008 servers out there still?

I really do not want to have to update all workstations to point directly to windows update site. It was so easy to manage from WSUS.

Bob

Laszlo.Kakas 16 Reputation points

2021-02-08T22:30:52.89+00:00

Yes, same here... TLS was enabled years ago and no recent change and suddenly the WSUS sync failing for multiple SBS owners around the globe. It seems something were moved away on MS servers. I have the same error "404 not found" in my WSUS logs as @Bob (ISI) @Anonymous @Shlomi Cohen @Peter Groom See attached log file. [65418-wsus-error.txt][1] [1]: /answers/storage/temp/65418-wsus-error.txt

Bob (ISI) 51 Reputation points

2021-02-08T23:09:50.603+00:00

Thank you for confirming anonymous user you and others are also seeing the same thing so we are all not wasting more hours trying to dismantle and rebuild our WSUS setup. Ugh. If anyone obtains some useful updates or information please post here!

Bob
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Bob (ISI) 51 Reputation points

2021-02-08T17:56:59.973+00:00

When I try un-selecting all products and classifications and press OK the window turns red, not allowing it to save without anything selected. I tried changing things up on both products and classes however it still didn't work with manual sync. One thing to note when trying to step through the configuration wizard method and the Upstream server set to 'Microsoft Update' and Proxy not checked, next step is 'Start Connecting' after a couple of seconds mine comes back with 'Unable to resolve the the upstream server name and if you click on details the below is shown.

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..
Was this answer helpful?

1 person 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.

WSUS Sync failure

47 answers

Your answer