The WSUS content directory is not accessible. The remote server returned an error: (503) Server Unavailable | Windows Server 2016
Environment
Summary
In the beginning, planned to migrate WSUS from WSUS 3.2 as:
Got different errors, however. Finally, and simply, have modified the Internal DNS to redirect all to the New WSUS.
Then, just a few days. Another question, this one: Error: 12072: Windows Server Update Services Application
Question
Restarted IIS, SQL, and the Update Services Service. Not work.
Event Logs:
Solution
Launch IIS Manager
Open "Application Pools"
Right click "WsusPool"
Select "Advanced Settings..."
Change (General) Queue Length from 1,000 (Default) to 25,000
Change (Rapid-Fail Protection) Service Unavailable from HttpLevel (Default) to Reponse to TcpLevel
Change (Rapid-Fail Protection) Failure Internal (minutes) from (Default) 5 to 30
Change (Rapid-Fail Protection) Maximum Failures from (Default) 5 to 30
"OK"
CLI "iisreset"
References
Update
- Windows Server 2016
- Windows Server Update Services (WSUS)
Summary
In the beginning, planned to migrate WSUS from WSUS 3.2 as:
#@ref https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/mt772341(v=ws.11)
"Originally, support for WSUS 3.0 SP2 was scheduled to end in 2017. However, this was not aligned with the support lifecycle for Windows Server 2008 R2, which is supported until January 14, 2020. As a result, the support lifecycle for WSUS 3.0 SP2 has been extended to January 14, 2020."
Although this gives additional time to migrate from WSUS 3.0 SP2 to later versions, performing this migration for all WSUS servers across a large organization is by no means an overnight operation. Therefore, now is the time to start planning this migration to WSUS 4.0 to take advantage of new functionality available in that version:
Support for deployment of Windows 10 feature updates (added via KB3159706). (WSUS 3.0 only supports the installation of Windows 10 quality updates, i.e. monthly patches.)
"Originally, support for WSUS 3.0 SP2 was scheduled to end in 2017. However, this was not aligned with the support lifecycle for Windows Server 2008 R2, which is supported until January 14, 2020. As a result, the support lifecycle for WSUS 3.0 SP2 has been extended to January 14, 2020."
Although this gives additional time to migrate from WSUS 3.0 SP2 to later versions, performing this migration for all WSUS servers across a large organization is by no means an overnight operation. Therefore, now is the time to start planning this migration to WSUS 4.0 to take advantage of new functionality available in that version:
Support for deployment of Windows 10 feature updates (added via KB3159706). (WSUS 3.0 only supports the installation of Windows 10 quality updates, i.e. monthly patches.)
Got different errors, however. Finally, and simply, have modified the Internal DNS to redirect all to the New WSUS.
Then, just a few days. Another question, this one: Error: 12072: Windows Server Update Services Application
Question
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\.
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\.
Restarted IIS, SQL, and the Update Services Service. Not work.
Event Logs:
Log Name: Application
Source: Windows Server Update Services
Date: 15/9/2018 7:04:35 PM
Event ID: 12072
Task Category: 9
Level: Error
Keywords: Classic
User: N/A
Computer: wsus.office.local
Description:
The WSUS content directory is not accessible.
System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)
Source: Windows Server Update Services
Date: 15/9/2018 7:04:35 PM
Event ID: 12072
Task Category: 9
Level: Error
Keywords: Classic
User: N/A
Computer: wsus.office.local
Description:
The WSUS content directory is not accessible.
System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)
wsus.office.local 12012 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12072 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12052 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12022 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12002 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12042 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12032 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 13042 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12072 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12052 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12022 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12002 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12042 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 12032 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
wsus.office.local 13042 Error Windows Server Update Services Application 15/9/2018 7:04:35 PM
Solution
Launch IIS Manager
Open "Application Pools"
Right click "WsusPool"
Select "Advanced Settings..."
Change (General) Queue Length from 1,000 (Default) to 25,000
Change (Rapid-Fail Protection) Service Unavailable from HttpLevel (Default) to Reponse to TcpLevel
Change (Rapid-Fail Protection) Failure Internal (minutes) from (Default) 5 to 30
Change (Rapid-Fail Protection) Maximum Failures from (Default) 5 to 30
"OK"
CLI "iisreset"
References
- Windows Server 2012 R2 WSUS Issue: Clients cause the WSUS App Pool to become unresponsive with HTTP 503: https://blogs.msdn.microsoft.com/the_secure_infrastructure_guy/2015/09/02/windows-server-2012-r2-wsus-issue-clients-cause-the-wsus-app-pool-to-become-unresponsive-with-http-503/
Update