none
WSUS Client failed to report back to the WSUS server

    Question

  • I have seen several question and discussion on this issue, i am experiencing similar issue. One of the WSUS client is stopped reporting back to WSUS server since last 1 months. Let me explain my insfrasture of WSUS. we have a WSUS server and all the clients they get Windows Security patch from WSUS server. So we not downloading any windows update from microsoft site directly. i have tried all the basic troubleshooting steps to fix the issue. but its still have same issue. few error i have seen on windowsupdate.log file 

    2012-07-13 09:33:16:733 408 2814 Report WARNING: Failed to open event cache file at C:\Windows\SoftwareDistribution\EventCache\{0572DD0D-D068-4833-A0EA-2681451236CE}.bin for reading with hr = 80070002.
    2012-07-13 09:33:16:733 408 2814 Report WARNING: Failed to open event cache file at C:\Windows\SoftwareDistribution\EventCache\{3A257481-CF81-4FD4-A34F-3A2B26F57CB4}.bin for reading with hr = 80070002.
    2012-07-13 09:33:16:733 408 2814 Report WARNING: Failed to open event cache file at C:\Windows\SoftwareDistribution\EventCache\{193E0BE8-E039-4C66-BA2E-165A5A4CBF1C}.bin for reading with hr = 80070002.
    2012-07-13 09:33:16:733 408 2814 Report WARNING: Failed to open event cache file at C:\Windows\SoftwareDistribution\EventCache\{CE2A5AB8-E45A-42E8-B4E5-AEB987C3B109}.bin for reading with hr = 80070002.

    ---------------------------------

    2012-07-13 09:33:19:853 408 2814 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
    2012-07-13 09:33:19:853 408 2814 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193

    -----------------------------

    2012-07-13 09:33:21:991 408 2814 Report REPORT EVENT: {A84497E7-3823-4292-9028-684637116C88} 2012-07-13 09:33:16:983-0400 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
    2012-07-13 09:33:21:991 408 2814 Report REPORT EVENT: {AA62CB2A-FF2E-4615-AAB5-07C60BDF31D4} 2012-07-13 09:33:20:040-0400 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80244018 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80244018.
    2012-07-13 09:33:21:991 408 2814 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2012-07-13 09:33:22:006 408 2814 Report WER Report sent: 7.6.7600.256 0x80244018 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
    2012-07-13 09:33:22:006 408 2814 Report CWERReporter finishing event handling. (00000000)
    2012-07-13 09:36:51:218 408 2814 PT WARNING: GetConfig failure, error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status code = 403
    2012-07-13 09:36:51:218 408 2814 PT WARNING: PTError: 0x80244018
    2012-07-13 09:36:51:218 408 2814 PT WARNING: GetConfig_WithRecovery failed: 0x80244018
    2012-07-13 09:36:51:218 408 2814 PT WARNING: RefreshConfig failed: 0x80244018
    2012-07-13 09:36:51:218 408 2814 PT WARNING: RefreshPTState failed: 0x80244018
    2012-07-13 09:36:51:218 408 2814 PT WARNING: PTError: 0x80244018

    any advice on this will be highly appreciated

    Monday, July 16, 2012 5:17 PM

Answers

  • i could resolve the issue. it was going to proxy and the proxy information was taking from winhttp proxy. i used below command to flush the winhttp proxy inoformation. 

    "netsh.exe winhttp reset proxy"

    Thanks again for looking into this issue.

    • Marked as answer by x3650 Thursday, July 19, 2012 7:23 PM
    Thursday, July 19, 2012 7:23 PM

All replies

  • It would help, significantly, to see these errors in the full context of everything else that happened. But generally speaking here, this client is encountering HTTP 403 errors trying to communicate with the WSUS server. Since the issue is only occuring on this machine, the most likely cause is that somebody changed something on this machine and probably with regard to the proxy configuration.

    So the first thing to do is to determine that the client has a valid configuration, and to what extent communication is being impacted. The SolarWinds Diagnostic Tool may be helpful in this regard.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Tuesday, July 17, 2012 4:30 PM
    Moderator
  • Hi,

    How many computers are affected?

    ********************************************************************

    2012-07-13 09:33:19:853408 2814Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
    2012-07-13 09:33:19:853408 2814Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193

    *******************************************************************

    From the error message above, it seems that the file info query and download request failed with the same error code.

    *******************************************************************

    2012-07-13 09:33:21:991408 2814Report REPORT EVENT: {A84497E7-3823-4292-9028-684637116C88}2012-07-13 09:33:16:983-0400 1202 102{00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdatesSuccess Content InstallReboot completed.
    2012-07-13 09:33:21:991408 2814Report REPORT EVENT: {AA62CB2A-FF2E-4615-AAB5-07C60BDF31D4}2012-07-13 09:33:20:040-0400 1148 101{D67661EB-2423-451D-BF5D-13199E37DF28} 1 80244018 SelfUpdate FailureSoftware Synchronization Windows Update Client failed to detect with error 0x80244018.

    *******************************************************************

    Please make sure that there is no third party software installed on the target PC. Also you need to verify the computer management for WSUS in Update Service console.

    Regards,
    James


    James Xiong

    TechNet Community Support

    Wednesday, July 18, 2012 7:25 AM
    Moderator
  • Please make sure that there is no third party software installed on the target PC.

    WHAT!?

    Also you need to verify the computer management for WSUS in Update Service console.

    The client is failing to communicate with the WSUS server, as evidenced by the WindowsUpdate.log entries. What would this accomplish?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Wednesday, July 18, 2012 6:38 PM
    Moderator
  • Please make sure that there is no third party software installed on the target PC.

    WHAT!?

    Also you need to verify the computer management for WSUS in Update Service console.

    The client is failing to communicate with the WSUS server, as evidenced by the WindowsUpdate.log entries. What would this accomplish?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Towards the third party software here I mean, it might be related to the firewall related software. Ports or other background scanning software. I think it could be checkpoint here.

    From the original post, "One of the WSUS client is stopped reporting back to WSUS server since last 1 months".

    So I think the WSUS client connected to the WSUS server once upon a time, the computer should be included in the list of the computer console. And the PC with lost status connection will be displayed like that:

    I'm not sure what happened towards this affected PC. Maybe the PC is out of domain or other unexpected behaviour. In my opinion, look into the ADUC to verify the computer property/status is also a good point to check.

    Sorry for confusion, guys. Also, correct me if I was wrong, Thx.

    Regards,

    James


    James Xiong

    TechNet Community Support

    Thursday, July 19, 2012 7:37 AM
    Moderator
  • Thanks for reply back, i am so sorry for late responce. was stuck with some other issue. i am looking the proxy configuration. 

    Would like to know one more information, do we use proxy server while downloading patch from local proxy server.

    Thanks

    Thursday, July 19, 2012 5:27 PM
  • i could resolve the issue. it was going to proxy and the proxy information was taking from winhttp proxy. i used below command to flush the winhttp proxy inoformation. 

    "netsh.exe winhttp reset proxy"

    Thanks again for looking into this issue.

    • Marked as answer by x3650 Thursday, July 19, 2012 7:23 PM
    Thursday, July 19, 2012 7:23 PM
  • Towards the third party software here I mean, it might be related to the firewall related software.
    Then please be THAT specific in your response. Explain to the poster WHY you're recommending something like that. Although, as noted in my response, the HTTP 403 -- out of nowhere -- is almost always caused by somebody changing something. In this case, it looks like somebody applied an incorrect WinHTTP proxy configuration to the client -- easily fixed by the netsh winhttp reset proxy command -- and no 3rd party software involved at all.
    I think it could be checkpoint here.
    Always possible -- but not in seven years of doing this have I ever seen the WUAgent receive an HTTP 403 error because of a locally installed firewall, much less a Checkpoint firewall!

    From the original post, "One of the WSUS client is stopped reporting back to WSUS server since last 1 months".

    So I think the WSUS client connected to the WSUS server once upon a time

    well.. yes... that would be expected.
    the computer should be included in the list of the computer console. And the PC with lost status connection will be displayed like that:
    All correct -- but it doesn't provide any useful diagnostic information! It only confirms what we've already seen from the WindowsUpdate.log -- the client isn't talking to the WSUS server!
    I'm not sure what happened towards this affected PC.
    The same thing that has happened to a thousand other WSUS clients over the past seven years that record HTTP 403 errors suddenly:
    • Somebody changed the client proxy configuration
    • Somebody added a proxy server and didn't configure the client
    • Somebody changed the proxy server configuration and did not update the client configuration.
    Hint: You will not likely see any *new* errors here that we haven't already seen a thousand times before, and typically at least once a month, if not once a week. The only new error I've seen in two years is the 0x800B0001 being caused because the WSUS server is not updated with KB2720211.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Friday, July 20, 2012 1:42 AM
    Moderator
  • i could resolve the issue. it was going to proxy and the proxy information was taking from winhttp proxy. i used below command to flush the winhttp proxy inoformation. 

    "netsh.exe winhttp reset proxy"

    Thanks again for looking into this issue.

    Glad to know the issue got fixed in the end. Thanks for your time and sharing.

    I believe other buddies will get benefit from your resolution towards the similar scenario. Good day~

    Regards,

    James


    James Xiong

    TechNet Community Support

    Friday, July 20, 2012 1:52 AM
    Moderator