If you are applying this fix on a Server Core install, you’ll need to connect remotely to the IIS instance to apply the fix.I have an 8 channel NVR model number K9608-2W and 6 cameras connected. The issue should now be resolved and your WSUS server should no longer be crashing.
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)
Event ID: 12072 - Windows Server Update Servicesĭescription: The WSUS content directory is not accessible.Event ID: 12052 - Windows Server Update Servicesĭescription: The DSS Authentication Web Service is not working.Event ID: 12042 - Windows Server Update Servicesĭescription: The SimpleAuth Web Service is not working.Event ID: 12022 - Windows Server Update Servicesĭescription: The Client Web Service is not working.Event ID: 12032 - Windows Server Update Servicesĭescription: The Server Synchronization Web Service is not working.