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

Bob (ISI) 51 Reputation points

2021-02-09T15:16:35.153+00:00

Someone must have some realistic feedback from MS on what is going on here. Please post here if someone has some legitimate feedback or a solution to this outside of scrapping SBS and 2008 servers.
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Vandrey Trindade 86 Reputation points

2021-02-09T20:49:41.707+00:00

I'm also looking for a fix!

Windows Server 2008 SP2.
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-10T01:11:01.313+00:00

Is anyone running SSL on their WSUS Server? Yes, I see the "44.154 Info WsusService.19 ServerCertificateValidator.VerifyServerCertificate SSL validation succeeded." but no one has currently said that they have WSUS using SSL.

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/changes-to-improve-security-for-windows-devices-scanning-wsus/ba-p/1645547
Was this answer helpful?
Vandrey Trindade 86 Reputation points

2021-02-10T11:02:52.067+00:00

Hi @Adam J. Marshall

I'm not using WSUS with SSL.

Adam J. Marshall 11,031 Reputation points MVP

2021-02-10T14:08:38.513+00:00

Just a thought - try enabling SSL on your local WSUS server. While I agree, requesting external updates from Microsoft shouldn't have any issues, with all the work they are doing to enhance security, perhaps there's a way they can see you don't have SSL enabled on your local WSUS server and are blackholing the connection?

Vandrey Trindade 86 Reputation points

2021-02-10T14:28:51.977+00:00

Hey @Adam J. Marshall

I'll have to check how to enable SSL on WSUS first.
If I have time today I'll take a look into it.

Adam J. Marshall 11,031 Reputation points MVP

2021-02-10T14:59:09.143+00:00

I link to the official documentation in my blog series - https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-7-ssl-setup-for-wsus-and-why-you-should-care/
I also link to another MVP Blog article on how to easily enable it with PowerShell.

Bob (ISI) 51 Reputation points

2021-02-10T15:23:28.423+00:00

Could someone please confirm how to enable SSL on the WSUS 3.2 server to save me some time digging it up online?

Vandrey Trindade 86 Reputation points

2021-02-10T17:31:13.477+00:00

Hi @Adam J. Marshall

Since my server is a Windows Server 2008 SP2 I couldn't use the PowerShell solution.
But I've created a self-signed certificate under IIS, enabled it.
Restarted the server and the same problem happens.

Information displayed on my WSUS console:
Type: Local/SSL
Port: 8531
User role: Administrator
Version: 3.2.7600.325

It seems that that is not the problem after all...

Vandrey Trindade 86 Reputation points

2021-02-10T17:32:06.183+00:00

@Bob (ISI)

I've used this:
https://jackstromberg.com/2013/11/enabling-ssl-on-windows-server-update-services-wsus/

Bob (ISI) 51 Reputation points

2021-02-10T22:01:16.597+00:00

Thank you!

Peter Groom 16 Reputation points

2021-02-10T22:17:51.587+00:00

@Bob (ISI) can you post here if it works after enabling SSL?

Vandrey Trindade 86 Reputation points

2021-02-10T22:26:40.187+00:00

I enabled it on Windows Server 2008 SP2 and it has the same problem.
Sign in to comment

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

2021-02-10T06:46:19.353+00:00

I met exactly same problem on WSUS 3.0 SP2 host that's managing Windows Server 2012 hosts update.

Fortunately, we already had the WSUS 6.3 environment on the same subnet for the hosts running Windows Server 2016 and above.

So we chose Windows Server 2012 products on WSUS 6.3 host (and synchronized), then changed upstream of WSUS 3.0 from Microsoft to the WSUS 6.3 host.

It's not completely same (and I'm not convinced) but it looks working again for now.
Was this answer helpful?

1 person found this answer helpful.
Martijn Kwak 6 Reputation points

2021-02-11T09:38:58.147+00:00

This seems to work for us as well.
Thanks Yasuo for testing this out.

Overal it is sad, that to get rid of Windows 7, I actually have to pollute the new environment, as well as the old. On the downstream server, I'm getting all the updates, also for Windows 10/Windows Server 2019 on the new environment I had to add Windows 7.

Any time infested in trying to fix the old Windows 7 clients not updating, is taken away from the time available to get the new environment running.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Peter Turnansky 1 Reputation point

2021-02-10T13:37:01.877+00:00

Hello, any update please ? I`m facing the same issue

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)
Was 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