wsus connection error

Hi @g sanjay ,

The quickest solution to get Windows Update in WSUS working again is to restart the server. When the frequency went up, I was able to catch one of the instances and do some troubleshooting. Although I can't get into the console on the server, I see that the WSUS service reports fine. If I execute the "iisreset" command, everything starts working again. This helps resolve issues quickly.

There are threads reporting similar issues. The main symptom is that the IIS worker process consumes more RAM than is available. The default limit is set to 1843200KB or 1.8GB. When the problem occurred, the IIS worker process was using more than 2GB of RAM. My server had more RAM available so the solution was to raise the amount of memory available to IIS. Steps as follows:

1. Open IIS and select Application Pool.
2. Right-click on the WsusPool and select Advanced Settings.
3. Change the Private Memory Limit (KB) to a higher number that fits your server specifications or ‘0’, which means no limit, instead of the hard-coded 1843200.
4. Go back under Application Pools, right-click on the WsusPool again and select "Recycle..."

Maybe when you try restarting all the required services, the problem will get resolved.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the email notification for this thread.

Best regards,
Yurong Dai

Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

You always have the option to re-install WSUS

https://www.ajtek.ca/wsus/how-to-remove-wsus-completely-and-reinstall-it/