WSUS pool reached its memory limit
Symptoms
Application log:

Self-update is not working.
The Reporting Web Service is not working.
The API Remoting Web Service is not working.
The Server Synchronization Web Service is not working.
The Client Web Service is not working.
The SimpleAuth Web Service is not working.
The DSS Authentication Web Service is not working.
The WSUS content directory is not accessible.
System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
System log:


Every minute an informational event: A worker process serving application pool ‘WsusPool’ has requested a recycle because it reached its private bytes memory limit.
Until the service gives up: Application pool ‘WsusPool’ is being automatically disabled due to a series of failures in the process(es) serving that application pool.
After restarting the application pool, the error came back within 10–20 minutes.
Solution
Increase the Private Memory Limit: IIS Manager → Server → Application Pools → WsusPool →
Advanced Settings → Recycling → Private Memory Limit (KB).

After raising the limit everything ran without problems.

This server delivers Windows updates to more than 10,000 clients.
Originally published on anyresearch.net. These are notes from real-world admin work – test before you use them in production.