Either change this to “0” (as shown below) to set no memory limit, or increase the limit to the value you prefer. In the “Advanced Settings” window, scroll down until you see “Private Memory Limit (KB)”.On the right hand side under “Application Pools” heading, right-click on “WsusPool” and select “Advanced Settings”.On the left hand side under “Connections”, expand the server, and select “Application Pools”.On the server running WSUS and IIS, open the “Internet Information Services (IIS) Manager” inside of the “Windows Administrative Tools” (found in the start menu, or Control Panel).To resolve this issue, we need to adjust the max Previously, I noticed database corruption on a WSUS SQL Express database when this issue occurred, so I recommend applying the fix on a fresh install of WSUS. Ultimately I believe this causes the IIS worker process to crash since it has run out of memory, and the pending command (whether it’s a synchronization or something else) fails to complete. This issue occurs because the WSUS application pool in IIS “WsusPool” has reached it’s maximum private memory limit and attempts to recycle the memory usage. WSUS 503 Error: Connection Error The Problem You will also see the below error message when attempting to use the WSUS MMC. : The remote server returned an error: (503) Server Unavailable.Īt ()Īt .HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |