I decided to run the cleanup wizard on my WSUS server recently and it crashes almost immediately with the reset server node error.
I went to PowerShell and I am getting the following error:
Any thoughts on why I am getting the error or how to correct it? The ServerIsInvalid is troubling, but I have no thoughts on how to go about fixing it. The server is fully operational otherwise and is configured to use SSL.
Appreciate any assistance.
Hi,
For the problem, if we try the following command, any difference?
Get-WsusServer | Invoke-WsusServerCleanup -CleanupObsoleteComputers
Alex
Good morning @AlexZhu-MSFT ,
I was hopeful last night when I saw your response. Sadly, when I run the Get-WsusServer first and then pipe it through I get the same error message.
Are you performing the proper WSUS maintenance including but not limited to declining superseded updates, running the SQL Indexing script, etc.?
The Server Cleanup Wizard (SCW) is only 1 component of WSUS Maintenance.
https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/
Good Morning Adam,
Yes, in fact after years of fumbling through WSUS administration it was your article\webpage (which I am having trouble pulling up at the moment, not sure if it is my end or web hosting, but after a while I am getting error 500) that I used to stand my current one up a couple of years ago.
Additionally, I think I had tried using SSL in the past to no avail until I stumbled onto your guide. Much appreciated for that by the way.
I keep my WSUS very clean. I have very strict and narrow automatic approval rules, decline 90% of the stuff that comes through, and only accept updates to systems I run.
In addition to the above PS error I get this when I try to run it from the GUI:
I've already whacked the wsus file to no avail.
What's your private memory limit set to?
https://www.ajtek.ca/wsus/wsus-system-requirements-what-should-i-plan-for/
Assuming this is virtual, what's your vCPUs set to?
And yes, our site was having issues this morning. We're working with our host to resolve them. It's currently up.
Yes, it is a virtual server with 4 CPUs and 8GB of memory with 4 of it dedicated to the WSUS application pool.
Is the WsusPool application pool started? If not, start it. If it is, increase it to 8GB and restart it.
If you have WAM, from the WAM Shell:
.\Clean-WSUS.ps1 -SetApplicationPoolMemory 8192
This also restarts the App Pool so you don't need to do it yourself.
Then try it again.
Yes, it was running. I stopped the service. Granted it 8GB of private memory and restarted the App Pool.
Same problem persists with both the GUI and the PS command.
Proxy server or firewall in the mix?
No proxy server. There is a border firewall, but it only controls ingress traffic at the site IP. Internally is mostly handled by the windows firewall and rules set in GPO.
Just to test I tried putting an Allow Any on the server to no avail.
It is a standalone WSUS with no downstream servers. I've got pretty much no issues receiving updates from MS or having machines connecting for patching....just running the clean up commands. The error message along with how quickly both the GUI and PS commands fail is....perplexing, but certainly appears to be something with the server itself.
Verify that the settings in Windows are accurately reporting no proxy server:
From PowerShell:
Write-Output "Proxy: $(netsh winhttp show proxy)"
Appears Windows is reporting correctly.
This thing is really bizarre.
Any 3rd party AV/Firewall installed on the WSUS server? Disable it? Uninstall it?
Nope, just the standard Windows firewall governed by GPO. For a test I disabled it and still had no luck.
7 people are following this question.
