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-11T17:06:42.127+00:00

What we need is MS to re-enable allowing WSUS 3.2X to retrieve updates rather than just cutting us all off. Very frustrating.
Was this answer helpful?

1 person found this answer helpful.
Bob (ISI) 51 Reputation points

2021-02-11T20:47:47.813+00:00

Well look at that, same here, mine is now syncing finally! Taking awhile but it's connecting anyway! Someone flipped the switch back on by the looks of it. Imagine how many WSUS 3.X servers are live and pulling updates now.
Sign in to comment

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

2021-02-11T07:23:22.77+00:00

Same here, but I have to add more - when I try to add update manually thru the WSUS console, I get an error 80131509.
Was this answer helpful?

1 person found this answer helpful.
Adam J. Marshall 11,031 Reputation points MVP

2021-02-11T13:14:49.337+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

Eugene Flash 6 Reputation points

2021-02-11T13:26:06.847+00:00

Yes, this happens with SchUseStrongCrypto enabled (and disabled too).

Adam J. Marshall 11,031 Reputation points MVP

2021-02-11T13:26:55.517+00:00

Also, have you changed the URL to

http://catalog.update.microsoft.com/... &Protocol=1.8

https://techcommunity.microsoft.com/t5/windows-servicing/known-issue-with-importing-updates-from-the-microsoft-update/m-p/163830

Vandrey Trindade 86 Reputation points

2021-02-11T13:28:21.993+00:00

Mine already uses 1.8

Vandrey Trindade 86 Reputation points

2021-02-11T13:31:19.263+00:00

I'm trying to import updates using PowerShell, but since I activated SSL I'm not able to connect to the server anymore.

How I used before SSL:

[reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration") | Out-Null $WSUS = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer()

What I'm trying now:

[reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration") | Out-Null $WSUS = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer("server.domain.local", $false,443)

Any ideas?

Vandrey Trindade 86 Reputation points

2021-02-11T13:53:13.637+00:00

I was able to connect by using this:
[reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration") | Out-Null
$WSUS = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer("server.domain.local", $true,443)

When I tried to import the update using:
$wsus.ImportUpdateFromCatalogSite("a8761130-35b6-41ce-8b67-2d35bb2d0846", "AMD64_X86_ARM-all-windows10.0-kb4601050-x64-ndp48_04c8736f250c06b3787d7d9ec366f011c6f8ca91.msu")

It returns the same 404 error:
Exception calling "ImportUpdateFromCatalogSite" with "2" argument(s): "The request failed with HTTP status 404: Not
Found."
At line:1 char:1
$wsus.ImportUpdateFromCatalogSite("a8761130-35b6-41ce-8b67-2d35bb2d0846", "AMD64 ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : NotSpecified: (:) [], MethodInvocationException
FullyQualifiedErrorId : WebException

Eugene Flash 6 Reputation points

2021-02-11T13:58:27.927+00:00

it's already 1.8

Adam J. Marshall 11,031 Reputation points MVP

2021-02-11T15:10:21.923+00:00

Just a thought - switch it to 1.2 - I doubt it will work, but I know that change was for newer versions as indicated by the link above.

Vandrey Trindade 86 Reputation points

2021-02-11T15:12:48.197+00:00

I tried to change it to 1.2 when I tested it for the first time.
It says that the WSUS server is not compatible or something.
Sign in to comment

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

2021-02-10T14:20:06.807+00:00

Same problem since here. We have over 100 synchronizations dating back to 11/13/20. All were successful until 1/29/21. Failures are consistent since 2/4/21. Also the same error in trying to reconfigure using the Configuration Wizard and testing the connection using the Start Connecting button in the middle of the Wizard. All while trying to connect to Microsoft Update.

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?

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

WSUS Sync failure

47 answers

Your answer