WSUS content folder & synchronization problem

Article
2020-01-28

Question

_{Tuesday, January 28, 2020 6:00 AM}

Actually, our WSUS content folder was full and that's why to reduce the size of the folder I tried the following steps and after that I am in a big trouble.

1. Close any open WSUS consoles.

2. Go to Administrative Tools – Services and STOP the Update Services service.

3. In Windows Explorer browse to the WSUSContent folder (typically D:\WSUS\WSUSContent or C:\WSUS\WSUSContent)

4. Delete ALL the files and folders in the WSUSContent folder.

5. Go to Administrative Tools – Services and START the Update Services service.

6. Open a command prompt and navigate to the folder: C:\Program Files\Update Services\Tools.

7. Run the command WSUSUtil.exe RESET.

After all the above steps, our WSUS is not synchronizing and no updates are being downloaded at all. Every time showing "Reset Server Node"

Please help me out as soon as possible.

Thanks

All replies (5)

_{Tuesday, January 28, 2020 10:28 AM}

Run cleanup task,

/zh-cn/security-updates/windowsupdateservices/18126013

https://www.prajwal.org/wsus-server-cleanup-wizard/

_{Wednesday, January 29, 2020 1:28 AM}

After all the above steps, our WSUS is not synchronizing and no updates are being downloaded at all. Every time showing "Reset Server Node"

This is a process that takes some time.
Other than noticing that the WSUSContent folder is no longer growing you can also check the SoftwareDistribution.log:

C:\Program Files\Update Services\LogFiles\SoftwareDistribution.log

When you start the reset process, you should see a line towards the bottom of the log which looks like this:

WsusService.13 ExecutionContext.runTryCode State Machine Reset Agent Starting

After waiting for some time, check the log again and search for the text “State Machine Reset Agent Finished”

WsusService.13 ExecutionContext.runTryCode State Machine Reset Agent Finished

Also, consider adjusting the private memory limit of the WSUS web site:

(1) On your WSUS Server, launch the IIS Manager.
(2) Click 'Application Pools' is in the Connections list.
(3) Right click 'WsusPool' and select 'Advanced Settings…'
'General' - 'Queue Length' : 25,000.
'Rapid-Fail Protection' - 'Service Unavailable' Response: TcpLevel
'Rapid-Fail Protection' - 'Failure Interval (minutes)' : 30
'Rapid-Fail Protection' - 'Maximum Failures' : 60
'Recucling' - 'Private Memory limit' : x4 times, or set to 0 (unlimited).
(4) Click 'ok' to save and restart the server.

Hope the above can help you.

Regards,
Yic

Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, January 29, 2020 5:14 AM}

After running the cleanup task, the same problem exists.

Let me share the error with you. Check the below error message which I copied from "copy error to clipboard":

********************************************************************************

The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

System.Net.WebException -- The operation has timed out

Source
System.Web.Services

Stack Trace:
**   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)**
**   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)**
**   at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)**
**   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)**
**   at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet)**
**   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet)**
**   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, UpdateScope updatesToInclude, ComputerTargetScope computersToInclude, UpdateServerStatusPropertiesToGet propertiesToGet)**
**   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetReplicaStatus(UpdateSources updateSources)**
**   at Microsoft.UpdateServices.UI.SnapIn.Common.CachedUpdateServerStatus.GetFreshObjectForCache()**
**   at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.RefreshCache()**
**   at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.GetFromCache()**
**   at Microsoft.UpdateServices.UI.SnapIn.Pages.ServerSummaryPage.backgroundWorker_DoWork(Object sender, DoWorkEventArgs e)**

***************************************************************************************************

Regards

Yousuf

_{Wednesday, January 29, 2020 6:23 AM}

Fortunately, after a looooong time it started working and synchronizing but after some time, it again showed the same behavior.

What I did, I restarted the following in the "services.msc"

WSUS service
Windows Internal database
Windows Update

and in "IIS Manager", I restarted

WSUS Pool

But unfortunately, again I am facing the same previous issue.

any suggestion/advice/instruction would highly be appreciable.

Regards

_{Monday, February 3, 2020 2:30 AM}

Hi,

If continuous cleaning and private memory adjustments in IIS still do not solve your current problem, please consider the following options:

Re-index the WSUS Database through a script.
After completely removing WSUS and related functions, add the WSUS role again.