locked
WSUS on Windows Server 2012R2 - clients not reporting RRS feed

  • Question

  • I have the following setup:

    Windows Server 2012 R2 Domain Controller with the WSUS Server role installed.

    All Windows 7 Pro SP1 Clients:

    24 clients connect and report and receive updates

    6 clients connect, WSUS console shows a current "Last Contact" date and "not yet reported" under "Last Status Report" These clients do not receive updates

    the 24 clients that receive updates are running Windows Update Agent 7.6.7600.256

    the 6 clients that are not reporting and not receiving updates are running Windows Update Agent 7.6.7600.320

    a sample of the WindowsUpdate.log from a client that is not reporting:

    2015-02-11 10:08:14:713 1036 1dc AU AU setting next sqm report timeout to 2015-02-12 15:08:14
    2015-02-11 11:32:50:253 1036 1dc AU #############
    2015-02-11 11:32:50:253 1036 1dc AU ## START ##  AU: Search for updates
    2015-02-11 11:32:50:253 1036 1dc AU #########
    2015-02-11 11:32:50:253 1036 1dc AU <<## SUBMITTED ## AU: Search for updates [CallId = {DBD27B0C-F93F-43D2-BFC1-58394D79FB08}]
    2015-02-11 11:32:50:253 1036 ef0 Agent *************
    2015-02-11 11:32:50:253 1036 ef0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-02-11 11:32:50:253 1036 ef0 Agent *********
    2015-02-11 11:32:50:253 1036 ef0 Agent   * Online = Yes; Ignore download priority = No
    2015-02-11 11:32:50:253 1036 ef0 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"
    2015-02-11 11:32:50:253 1036 ef0 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2015-02-11 11:32:50:253 1036 ef0 Agent   * Search Scope = {Machine}
    2015-02-11 11:32:50:269 1036 ef0 Setup Checking for agent SelfUpdate
    2015-02-11 11:32:50:284 1036 ef0 Setup Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
    2015-02-11 11:32:52:593 1036 ef0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2015-02-11 11:32:52:609 1036 ef0 Misc  Microsoft signed: NA
    2015-02-11 11:32:52:609 1036 ef0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPCEFC.tmp with dwProvFlags 0x00000080:
    2015-02-11 11:32:52:624 1036 ef0 Misc  Microsoft signed: NA
    2015-02-11 11:32:52:640 1036 ef0 Setup WARNING: SelfUpdate check failed to download package information, error = 0x80246002
    2015-02-11 11:32:52:640 1036 ef0 Setup FATAL: SelfUpdate check failed, err = 0x80246002
    2015-02-11 11:32:52:640 1036 ef0 Agent   * WARNING: Skipping scan, self-update check returned 0x80246002
    2015-02-11 11:32:52:655 1036 ef0 Agent   * WARNING: Exit code = 0x80246002
    2015-02-11 11:32:52:655 1036 ef0 Agent *********
    2015-02-11 11:32:52:655 1036 ef0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-02-11 11:32:52:655 1036 ef0 Agent *************
    2015-02-11 11:32:52:655 1036 ef0 Agent WARNING: WU client failed Searching for update with error 0x80246002
    2015-02-11 11:32:52:671 1036 f70 AU >>##  RESUMED  ## AU: Search for updates [CallId = {DBD27B0C-F93F-43D2-BFC1-58394D79FB08}]
    2015-02-11 11:32:52:671 1036 f70 AU   # WARNING: Search callback failed, result = 0x80246002
    2015-02-11 11:32:52:671 1036 f70 AU   # WARNING: Failed to find updates with error code 80246002
    2015-02-11 11:32:52:671 1036 f70 AU #########
    2015-02-11 11:32:52:671 1036 f70 AU ##  END  ##  AU: Search for updates [CallId = {DBD27B0C-F93F-43D2-BFC1-58394D79FB08}]
    2015-02-11 11:32:52:671 1036 f70 AU #############
    2015-02-11 11:32:52:671 1036 f70 AU Successfully wrote event for AU health state:0
    2015-02-11 11:32:52:671 1036 f70 AU AU setting next detection timeout to 2015-02-11 21:32:52
    2015-02-11 11:32:52:671 1036 f70 AU Setting AU scheduled install time to 2015-02-12 06:00:00
    2015-02-11 11:32:52:671 1036 f70 AU Successfully wrote event for AU health state:0
    2015-02-11 11:32:52:671 1036 f70 AU Successfully wrote event for AU health state:0
    2015-02-11 11:32:57:647 1036 ef0 Report REPORT EVENT: {0E083F99-73CD-4A2E-8916-0FC7F89A7888} 2015-02-11 11:32:52:640-0500 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80246002 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80246002.
    2015-02-11 11:32:57:647 1036 ef0 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2015-02-11 11:32:57:647 1036 ef0 Report WER Report sent: 7.6.7600.320 0x80246002 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
    2015-02-11 11:32:57:647 1036 ef0 Report CWERReporter finishing event handling. (00000000)
    2015-02-11 11:42:17:706 1036 ef0 PT WARNING: Cached cookie has expired or new PID is available
    2015-02-11 11:42:17:706 1036 ef0 PT Initializing simple targeting cookie, clientId = 1afdb948-fcc1-44c8-949a-58764a182a7b, target group = , DNS name = dell-43.zcadom.zevcohen.com
    2015-02-11 11:42:17:706 1036 ef0 PT   Server URL = HTTP://192.168.10.1:8530/SimpleAuthWebService/SimpleAuth.asmx
    2015-02-11 11:42:17:722 1036 ef0 Report Uploading 1 events using cached cookie, reporting URL = HTTP://192.168.10.1:8530/ReportingWebService/ReportingWebService.asmx
    2015-02-11 11:42:17:722 1036 ef0 Report Reporter successfully uploaded 1 events.

    There is a line in bold text that shows an error. Every client that does not report has the same error.

    Update 2938066 is installed on the WSUS server.

    As a test I attempted to install the 7.6.7600.256 Windows Update Agent on one of the problem machines, but I cannot uninstall the .320 version and I cannot install the .256 version on top of the .320 version.

    The WSUS Role has already been completely removed and reinstalled on the Windows 2012 R2 server. Only the PC's running .320 version of the Windows Update Agent have an issue, but I don't know if the issue is with the workstation or the WSUS server. The problem workstations can download and install updates directly from Microsoft Update, just not from the WSUS server. I have been unable to find any specific info on this issue. Can anyone help with this?

    Thanks

    Wednesday, February 11, 2015 8:17 PM

All replies

  • Hi,

    0x80246002 means that the file digest did not match the expected value.

    This problem may occur if Windows Update or Microsoft Update determines there is a file hash mismatch when you try to search for available updates from the Windows Update Web site or from the Microsoft Update Web site.

    To resolve this issue, please make a bat file with the command below, then run the bat file with Administrator privilege.

    • net stop wuauserv
    • cd %systemroot%\SoftwareDistribution
    • ren Download Download.old
    • net start wuauserv

    For detailed information, please refer to the link below:

    http://support.microsoft.com/kb/958056/en-us

    Best Regards.


    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Saturday, February 14, 2015 12:29 PM
  • I tried this step and it did not fix the issue. However, what did fix the issue was uninstalling Update 2938066 from the WSUS server. After I uninstalled that update and rebooted the WSUS server, the clients that were showing "not yet reported" started showing up as reported.
    • Proposed as answer by Steven_Lee0510 Friday, February 20, 2015 8:28 AM
    Monday, February 16, 2015 2:07 PM
  • Hi,

    Glad to hear that your issue is resolved and thanks for the sharing!

    Best Regards.


    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, February 20, 2015 8:30 AM
  • You're welcome. Of course, it leads to another question...

    Why uninstalling an update fixes an issue. Why should an update to WSUS cause any problems?

    Friday, February 20, 2015 1:47 PM
  • You're welcome. Of course, it leads to another question...

    Why uninstalling an update fixes an issue. Why should an update to WSUS cause any problems?

    The answer relates to this statement "Only the PC's running .320 version of the Windows Update Agent have an issue, but I don't know if the issue is with the workstation or the WSUS server."

    That version of WUA does not work with the patch that you removed (2938066) since it hardened WSUS. Made the hash stronger. Once all your workstations in your environment get the latest WUA that DOES work with the patch that hardens WSUS then it will be ok. The tricky part is to get ALL the computers to get the updates WUA.

    Friday, February 20, 2015 3:59 PM
  • Do we know if there is a later version of WUA that works with the WSUS 2938066 patch? Obviously the .256 version does, and obviously the .320 version doesn't. As far as I can find, the .320 version is the latest version. I'm also curious about a statement from the 2938066 support document that states:

    "The WUA on computers that are managed by this WSUS server will be automatically upgraded as needed after you apply this update"

    Unless I'm missing something, this statement tells me that WSUS will automatically update the WUA on the client. The WUA .256 clients that have always worked did not get their WUA updated after I originally installed the 2938066 update. This also tells me that the .256 WUA is the correct one that works with WSUS and the 2938066 patch and the WUA .320 does not work with the 2938066 patch. It seems to me (again unless I am missing something) that Microsoft releasing a WUA that does not work with the 2938066 patch would documented or acknowledged by Microsoft.

    Friday, February 20, 2015 5:05 PM