Forum Discussion
WSUS Sync Failing
Within the last hour or so I have carried up a cleanup of our WSUS and reindexed the database as per this article https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/
Once complete I re-enable the SUP schedule and WSUS has not been able to Sync since. Our SCCM Version is 1702 with the hotfix, hosted on a Server 2012r2 system. WSUS content is within a SQL database.
WCM.log;
"System.Net.WebException: The request failed with HTTP status 403: Target service not allowed.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)"
WsusCtrl.log does not seem to indicate any proxy related errors;
"No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name ####### and Proxy Port ##"
9 Replies
So it would appear that this issue is only when a proxy is specified within the site system properties of the primary site server
I am just wondering why this would all of a sudden start happening it would appear as a result of carrying out the WSUS cleanup and database reindex as per the link provided? Unless just a mere coincidence
Also On the proxy logs I am not even seeing an attempt from the SCCM server to access the Windows update URL's only https://fef.msub05.manage.microsoft.com/ which is intune and passes successfully.
When I remove the proxy I can see connection to https://fe2.update.microsoft.com/
Continuing to investigate.
Well noticed that too and was hoping. Bad news is this didn't fix our Problem, Contacting MS Support now.
Greetings
mike
hi,
facing exact the same Problem also right now. also after a wsus Cleanup.
Any solution for this yet?
- Hi I am no expert of WSUS but I'd recommend checking the Virtual Memory usage of WSUS App pool. Because if it consumes all of your virtual memory then you start getting all sorts of errors including but not limited to WSUS console crashing and .Net related access denials. So I would recommend increasing the limit of the Private Memory Limit (KB) to a higher number.
