locked
windows server 2016 Connecting local WSUS services ,EP: error: 0x8024500C : - failed to get SLS data RRS feed

  • Question

  • windows server 2016 Connecting local WSUS services ,USE GPO ,connect to http://192.168.77.175:8530

    in my domain ,win 7,2008r2,2012r2,win10 get update successfull

    my domain uses ie proxy

    windows server 2016 windowsupdate.log:

    2018/10/16 10:34:42.4605885 1684  15108 Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 2

    2018/10/16 10:34:42.4605893 1684  15108 Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
    2018/10/16 10:34:42.4605902 1684  15108 Agent           Criteria = IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1""
    2018/10/16 10:34:42.4605943 1684  15108 Agent           ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
    2018/10/16 10:34:42.4605947 1684  15108 Agent           Search Scope = {Machine}
    2018/10/16 10:34:42.4605978 1684  15108 Agent           Caller SID for Applicability: S-1-5-21-1057776969-3995467611-557851033-500
    2018/10/16 10:34:42.4605983 1684  15108 Agent           ProcessDriverDeferrals is set
    2018/10/16 10:34:42.4605987 1684  15108 Agent           RegisterService is set
    2018/10/16 10:34:42.4633218 1684  15108 Misc            EP: error: 0x8024500C : - failed to get SLS data
    2018/10/16 10:34:42.4633258 1684  15108 Misc            Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL, error = 0x8024500C
    2018/10/16 10:34:42.4633294 1684  15108 Agent           Failed to obtain the authorization cab URL for service 7971f918-a847-4430-9279-4a52d1efe18d, hr=0
    2018/10/16 10:34:42.4633298 1684  15108 Agent           Caller UpdateOrchestrator failed to opt in to service 7971f918-a847-4430-9279-4a52d1efe18d, hr=0X8024500C
    2018/10/16 10:34:42.4639167 1684  15108 Misc            EP: error: 0x8024500C : - failed to get SLS data
    2018/10/16 10:34:42.4639220 1684  15108 Misc            Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL, error = 0x8024500C
    2018/10/16 10:34:42.4639287 1684  15108 ProtocolTalker  PTError: 0x8024500c
    2018/10/16 10:34:42.4639314 1684  15108 ProtocolTalker  Initialization failed for Protocol Talker Context 0x8024500c
    2018/10/16 10:34:42.4838414 1684  15108 Agent           Exit code = 0x8024500C
    2018/10/16 10:34:42.4838419 1684  15108 Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 2

    Tuesday, October 16, 2018 2:47 AM

All replies

  • Hi,

    -Check whether the client shows up and report to the WSUS;

    -Please disable the proxy and try to test again;

    -Moreover, you can try the following command:
    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
    net start bits
    net start wuauserv
    wuauclt /resetauthorization /detectnow

    Best regards,
    Johnson
    =====================
    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    • Edited by Johnson ZDH Tuesday, October 16, 2018 7:17 AM
    Tuesday, October 16, 2018 7:11 AM
  • disable proxy。

    After running the command, the client still fails. There is no change in the content of the update log.

    In WSUS,the client(2016 server),all  approved patches are not applicable.

    Wednesday, October 17, 2018 1:15 AM
  • Hi,

    In the client side of the server 2016, you can check for update from the Microsoft.

    Moreover, mark sure there are patches that are designed for the server 2016 in the approved patches.
    In the server 2016 client, you can try to uncheck the "Defer feature updates" through path:settings>updates and security>advanced option. Then check for update from the WSUS.

    Best regards,
    Johnson
    =====================
    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Wednesday, October 17, 2018 1:56 AM
  • Hi
    my 2016 con not connect to internet,WSUS USE PROXY to connect internet。
    "Defer feature updates" is not checked。


    Wednesday, October 17, 2018 3:45 AM
  • Hello,
     
    Please double check your GPO or registry to make sure the address of WSUS server is correct.
     
    Then check your GPO, if you have enabled any policies in "Windows Update for Business", if yes, disable them.
     
    Then run following script in 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
     
    If issue persists, please upload your GPO setting by running "rsop.msc" or "gpresult /h", and the result of following PowerShell script.
     
    Get-BitsTransfer -AllUsers
     
    Looking 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.

    Wednesday, October 17, 2018 7:40 AM
  • Hi, 

    was this issue resolved? I have a same problem

    Saturday, February 8, 2020 1:02 PM