locked
Client is not getting available under WSUS RRS feed

  • Question

  • Client is not getting available under WSUS, below are error listed in WindowsUpdate.log file:

    2018-10-15 15:35:09.5317245 4848  11548 WebServices     WS error: There was an error communicating with the endpoint at 'http://domain.com/wsusdmz/ClientWebService/client.asmx'.
    2018-10-15 15:35:09.5317268 4848  11548 WebServices     WS error: There was an error receiving the HTTP reply.
    2018-10-15 15:35:09.5317315 4848  11548 WebServices     WS error: The operation did not complete within the time allotted.
    2018-10-15 15:35:09.5317376 4848  11548 WebServices     WS error: There was an error communicating with the endpoint at 'http://domain.com.com/wsusdmz/ClientWebService/client.asmx'.
    2018-10-15 15:35:09.5317418 4848  11548 WebServices     WS error: The server returned HTTP status code '503 (0x1F7)' with text 'Service Unavailable'.
    2018-10-15 15:35:09.5317450 4848  11548 WebServices     WS error: The service is temporarily overloaded.
    2018-10-15 15:35:09.5317516 4848  11548 WebServices     WS error: There was an error communicating with the endpoint at 'http://domain.com.com/wsusdmz/ClientWebService/client.asmx'.
    2018-10-15 15:35:09.5317572 4848  11548 WebServices     WS error: The server returned HTTP status code '503 (0x1F7)' with text 'Service Unavailable'.
    2018-10-15 15:35:09.5317614 4848  11548 WebServices     WS error: The service is temporarily overloaded.
    2018-10-15 15:35:09.5317884 4848  11548 WebServices     WS error: The operation timed out
    2018-10-15 15:35:09.5317987 4848  11548 WebServices     *FAILED* [8024401C] Web service call
    2018-10-15 15:35:09.5318015 4848  11548 WebServices     Current service auth scheme=0.
    2018-10-15 15:35:09.5318043 4848  11548 WebServices     Current Proxy auth scheme=0.
    2018-10-15 15:35:09.5318239 4848  11548 IdleTimer       WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 160) stopped; does use network; is at background priority
    2018-10-15 15:35:09.5318388 4848  11548 ProtocolTalker  *FAILED* [8024401C] GetConfig_WithRecovery failed
    2018-10-15 15:35:09.5318486 4848  11548 ProtocolTalker  *FAILED* [8024401C] RefreshConfig failed
    2018-10-15 15:35:09.5318523 4848  11548 ProtocolTalker  *FAILED* [8024401C] RefreshPTState failed
    2018-10-15 15:35:09.5318589 4848  11548 ProtocolTalker  SyncUpdates round trips: 0
    2018-10-15 15:35:09.5318612 4848  11548 ProtocolTalker  *FAILED* [8024401C] Sync of Updates
    2018-10-15 15:35:09.5318738 4848  11548 ProtocolTalker  *FAILED* [8024401C] SyncServerUpdatesInternal failed
    2018-10-15 15:35:09.5388176 4848  11548 Agent           *FAILED* [8024401C] Synchronize


    • Edited by RSA111 Monday, October 15, 2018 10:32 AM
    Monday, October 15, 2018 10:30 AM

All replies

  • Hello,
     
    1> Check your GPO or Registry to make sure that the address of WSUS server is correct. If possible, you could upload some screenshot to ensure that.
     
    2> If there are firewalls or AV on the clients or server, you could temporarily disable them and check the result.
     
    3> Check the connectivity between WSUS and clients. Check if you could get the wuident.cab by browsing "Http://yourwsusserver:8530/selfupdate/wuident.cab on the affected clients.
     
    4> On the WSUS server, increase the WsusPool Queue Length to 2000 and set the WsusPool Private Memory limit to 0 (unlimited). Then reset the IIS. Make sure the WSUS service and the World Wide Web Publishing Service are running. 
     
    5> On the affected clients, run following script in the elevated CMD and check the result.
     
    net stop bits
    net stop wuauserv
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
    rd /s /q "C:\WINDOWS\SoftwareDistribution"
    net start bits
    net start wuauserv
    wuauclt /resetauthorization /detectnow
    usoclient.exe startscan
     
    Hope my answer could help you and look forward to your feedback.
     
    Best Regards,
    Ray

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 16, 2018 1:35 AM
  • Thank you Ray for your response. Issue fixed, our DNS records was pointing to old WSUS server, which we changed and its started communicating..

    Rahul Sapke.

    Tuesday, October 16, 2018 6:40 AM
  • Hello,
     
    Glad to hear that.
     
    Best Regards,
    Ray

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 16, 2018 8:29 AM