Asked by:

WSUS Server Node not connecting

Question

I have a WSUS server that had been working properly until a couple hours ago. I'm pretty sure some updates went through for the server and now I'm surprised with my wsus snap-in not working any more. I cleared the mmc folder contents in %appdata% and also
the cache and checked that WWW service was not set to interact with the desktop. Any ideas? Please see the error below.

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

System.IndexOutOfRangeException -- Index was outside the bounds of the array.

Ann thanks for the reply, and the answer is yes the server had the KB installed and I did went through the steps outlined in the KB article however it still is showing the issue. I've seen several articles detailing issues in WSUS after this KB is installed
my server was healthy before it.

1. Remove all Drivers from the WSUS Database.
2. Shrink your WSUSContent folder's size by declining superseded updates.
3. Remove declined updates from the WSUS Database.
4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
5. Compress Update Revisions.
6. Remove Obsolete Updates.
7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
9. Run the Recommended SQL database Maintenance script on the actual SQL database.
10. Run the Server Cleanup Wizard.

It will email the report out to you or save it to a file, or both.

Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

.\Clean-WSUS.ps1 -FirstRun

and then

.\Clean-WSUS.ps1 -InstallTask

If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.

It looks like my problem has somehow shifted to the WSUS AppPool just stopping, in consequence of course my WSUS console and services are also halted. The current memory limit is set to 18GB out of the 6-12GB recommended threshold. I really appreciate some
insight on this if anyone knows how to fix it.

Below is the error on the WSUS console:

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.

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

System.IO.IOException -- The handshake failed due to an unexpected packet format.

System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.

Source
Microsoft.UpdateServices.Administration

Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

Thanks for the link, it basically summarizes the two scenarios that I previously covered on my replies before. I appreciate the guidance but I believe that something else might be going on with this server.

At this point I would try Vudu if it could help figure out what the real issue is. I'm getting ready to deploy a replacement for that WSUS but it's extremely frustrating not being able to figure it out. As for your script, can you provide a link so I can
take a look at it. I greatly appreciate everyone helping on this one.