locked
Some workstations not reporting status to WSUS on SBS 2008 Server. Giving error 8024400E when checking for updates RRS feed

  • Question

  • We have a domain network of around 50 workstations and an SBS 2008 domain controller.

    Within the WSUS console on the server five of the workstations (all Windows 7 Pro) show "This computer has not reported status yet” All of the other workstations report their status and receive updates fine.

    On the problematic workstations if we open the Windows Updates program and check for updates we get the following error message immediately:

    Code 8024400E - Windows Update encountered an unknown error

    We've been troubleshooting this for a few days and we've tried everything that we can find, including running all of the WSUS reset routines on the workstations, including the duplicate SID resets and registry adjustments.

    Today we installed a fresh copy of Windows 7 Pro on a workstation to test and this system also gives the same error code above almost immediately after checking for updates. This suggests that the issue is possibly with the WSUS software on the server.

    If we try and obtain updates direct from Microsoft it gets the updates fine.

    The build number of WSUs on the server is 3.2.7600.256.

    Below is a copy of the WindowsUpdate log file from one of the problematic workstations.

    Thanks in advance.

    2017-05-25 11:28:29:811 1368 1bc0 Misc ===========  Logging initialized (build: 7.6.7601.23735, tz: +0100)  ===========
    2017-05-25 11:28:29:811 1368 1bc0 Misc   = Process: C:\Windows\system32\svchost.exe
    2017-05-25 11:28:29:811 1368 1bc0 Misc   = Module: c:\windows\system32\wuaueng.dll
    2017-05-25 11:28:29:811 1368 1bc0 Service *************
    2017-05-25 11:28:29:811 1368 1bc0 Service ** START **  Service: Service startup
    2017-05-25 11:28:29:811 1368 1bc0 Service *********
    2017-05-25 11:28:29:811 1368 1bc0 Agent   * WU client version 7.6.7601.23735
    2017-05-25 11:28:29:811 1368 1bc0 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2017-05-25 11:28:29:811 1368 1bc0 Agent   * Access type: No proxy
    2017-05-25 11:28:29:811 1368 1bc0 Agent   * Network state: Connected
    2017-05-25 11:29:06:417 1368 1004 Report CWERReporter::Init succeeded
    2017-05-25 11:29:06:417 1368 1004 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2017-05-25 11:29:06:417 1368 1004 Agent   * Prerequisite roots succeeded.
    2017-05-25 11:29:06:417 1368 1004 Agent ***********  Agent: Initializing global settings cache  ***********
    2017-05-25 11:29:06:417 1368 1004 Agent   * WSUS server: http://ourservername:8530
    2017-05-25 11:29:06:417 1368 1004 Agent   * WSUS status server: http://ourservername:8530
    2017-05-25 11:29:06:417 1368 1004 Agent   * Target group: (Unassigned Computers)
    2017-05-25 11:29:06:417 1368 1004 Agent   * Windows Update access disabled: No
    2017-05-25 11:29:06:417 1368 1004 DnldMgr Download manager restoring 0 downloads
    2017-05-25 11:29:06:417 1368 1004 AU ###########  AU: Initializing Automatic Updates  ###########
    2017-05-25 11:29:06:417 1368 1004 AU   # WSUS server: http://ourservername:8530
    2017-05-25 11:29:06:417 1368 1004 AU   # Detection frequency: 1
    2017-05-25 11:29:06:417 1368 1004 AU   # Approval type: Pre-install notify (Policy)
    2017-05-25 11:29:06:417 1368 1004 AU   # Auto-install minor updates: Yes (Policy)
    2017-05-25 11:29:06:417 1368 1004 AU   # Will interact with non-admins (Non-admins are elevated (Policy))
    2017-05-25 11:29:06:463 1368 1bc0 Report ***********  Report: Initializing static reporting data  ***********
    2017-05-25 11:29:06:463 1368 1bc0 Report   * OS Version = 6.1.7601.1.0.65792
    2017-05-25 11:29:06:463 1368 1bc0 Report   * OS Product Type = 0x00000030
    2017-05-25 11:29:06:479 1368 1bc0 Report   * Computer Brand = Dell Inc.
    2017-05-25 11:29:06:479 1368 1bc0 Report   * Computer Model = Latitude 3570
    2017-05-25 11:29:06:479 1368 1bc0 Report   * Bios Revision = 1.1.4
    2017-05-25 11:29:06:479 1368 1bc0 Report   * Bios Name = BIOS Date: 01/17/16 23:41:43 Ver: 01.01.04
    2017-05-25 11:29:06:479 1368 1bc0 Report   * Bios Release Date = 2016-01-17T00:00:00
    2017-05-25 11:29:06:479 1368 1bc0 Report   * Locale ID = 2057
    2017-05-25 11:29:07:306 1368 1004 AU Successfully wrote event for AU health state:0
    2017-05-25 11:29:07:306 1368 1004 AU Initializing featured updates
    2017-05-25 11:29:07:306 1368 1004 AU Found 0 cached featured updates
    2017-05-25 11:29:07:306 1368 1004 AU Successfully wrote event for AU health state:0
    2017-05-25 11:29:07:306 1368 1004 AU Successfully wrote event for AU health state:0
    2017-05-25 11:29:07:306 1368 1004 AU AU finished delayed initialization
    2017-05-25 11:29:07:306 1368 1004 AU Triggering AU detection through DetectNow API
    2017-05-25 11:29:07:306 1368 1004 AU Triggering Online detection (interactive)
    2017-05-25 11:29:07:306 1368 1bc0 AU #############
    2017-05-25 11:29:07:306 1368 1bc0 AU ## START ##  AU: Search for updates
    2017-05-25 11:29:07:306 1368 1bc0 AU #########
    2017-05-25 11:29:07:306 1368 1bc0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {B4464B60-ED05-4B4C-81F8-511FC1BA5592}]
    2017-05-25 11:29:07:306 1368 dac Agent *************
    2017-05-25 11:29:07:306 1368 dac Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2017-05-25 11:29:07:306 1368 dac Agent *********
    2017-05-25 11:29:07:306 1368 dac Agent   * Online = Yes; Ignore download priority = No
    2017-05-25 11:29:07:306 1368 dac 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"
    2017-05-25 11:29:07:306 1368 dac Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2017-05-25 11:29:07:306 1368 dac Agent   * Search Scope = {Machine}
    2017-05-25 11:29:07:306 1368 dac Setup Checking for agent SelfUpdate
    2017-05-25 11:29:07:306 1368 dac Setup Client version: Core: 7.6.7601.23735  Aux: 7.6.7601.23735
    2017-05-25 11:29:07:369 1368 dac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2017-05-25 11:29:07:384 1368 dac Misc  Microsoft signed: NA
    2017-05-25 11:29:07:384 1368 dac Misc WARNING: Cab does not contain correct inner CAB file.
    2017-05-25 11:29:07:384 1368 dac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2017-05-25 11:29:07:384 1368 dac Misc  Microsoft signed: NA
    2017-05-25 11:29:07:400 1368 dac Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
    2017-05-25 11:29:07:400 1368 dac Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2017-05-25 11:29:07:400 1368 dac Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2017-05-25 11:29:07:447 1368 dac PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2017-05-25 11:29:07:447 1368 dac PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ourservername:8530/ClientWebService/client.asmx
    2017-05-25 11:29:07:462 1368 dac PT WARNING: Cached cookie has expired or new PID is available
    2017-05-25 11:29:07:462 1368 dac PT Initializing simple targeting cookie, clientId = c99cbf8f-239d-49ad-9b4a-783fc425d8f7, target group = , DNS name = computername.ourdomain.local
    2017-05-25 11:29:07:462 1368 dac PT   Server URL = http://ourservername:8530/SimpleAuthWebService/SimpleAuth.asmx
    2017-05-25 11:29:07:587 1368 dac PT WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2017-05-25 11:29:07:587 1368 dac PT WARNING: SOAP Fault: 0x000190
    2017-05-25 11:29:07:587 1368 dac PT WARNING:     faultstring:Fault occurred
    2017-05-25 11:29:07:587 1368 dac PT WARNING:     ErrorCode:InternalServerError(5)
    2017-05-25 11:29:07:587 1368 dac PT WARNING:     Message:(null)
    2017-05-25 11:29:07:587 1368 dac PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2017-05-25 11:29:07:587 1368 dac PT WARNING:     ID:f78b7521-5ea9-4944-be06-c4954e03ad23
    2017-05-25 11:29:07:587 1368 dac PT WARNING: PTError: 0x8024400e
    2017-05-25 11:29:07:587 1368 dac PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400e
    2017-05-25 11:29:07:587 1368 dac PT WARNING: Sync of Updates: 0x8024400e
    2017-05-25 11:29:07:587 1368 dac PT WARNING: SyncServerUpdatesInternal failed: 0x8024400e
    2017-05-25 11:29:07:587 1368 dac Agent   * WARNING: Failed to synchronize, error = 0x8024400E
    2017-05-25 11:29:07:603 1368 dac Agent   * WARNING: Exit code = 0x8024400E
    2017-05-25 11:29:07:603 1368 dac Agent *********
    2017-05-25 11:29:07:603 1368 dac Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2017-05-25 11:29:07:603 1368 dac Agent *************
    2017-05-25 11:29:07:603 1368 dac Agent WARNING: WU client failed Searching for update with error 0x8024400e
    2017-05-25 11:29:07:603 1368 1fc AU >>##  RESUMED  ## AU: Search for updates [CallId = {B4464B60-ED05-4B4C-81F8-511FC1BA5592}]
    2017-05-25 11:29:07:603 1368 1fc AU   # WARNING: Search callback failed, result = 0x8024400E
    2017-05-25 11:29:07:603 1368 1fc AU   # WARNING: Failed to find updates with error code 8024400E
    2017-05-25 11:29:07:603 1368 1fc AU #########
    2017-05-25 11:29:07:603 1368 1fc AU ##  END  ##  AU: Search for updates [CallId = {B4464B60-ED05-4B4C-81F8-511FC1BA5592}]
    2017-05-25 11:29:07:603 1368 1fc AU #############
    2017-05-25 11:29:07:603 1368 1fc AU Successfully wrote event for AU health state:0
    2017-05-25 11:29:07:603 1368 1fc AU AU setting next detection timeout to 2017-05-25 11:27:44
    2017-05-25 11:29:07:603 1368 1fc AU Successfully wrote event for AU health state:0
    2017-05-25 11:29:07:603 1368 1fc AU Successfully wrote event for AU health state:0


    • Edited by CoolGeezer Thursday, May 25, 2017 3:37 PM
    Thursday, May 25, 2017 3:36 PM

All replies

  • Hi,

    According to your description, my understanding is that it some workstations failed to install/check Windows Update using WSUS on SBS.

    Please try to run “wuauclt /resetauthorization /detectnow”.

    Besides, on the problematic client, please open CMD and select Run as Administrator. Type below command, each line end with enter:
    net stop wuauserv
    ren c:/windows/SoftwareDistribution softwaredistribution.old
    net start wuauserv

    Also, make sure that below services are running on the client, or, you may try to manually re-start the service and check the result:
    Windows Update
    Background Intelligent Transfer Service
    Cryptographic Service
    Software Protection

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, May 26, 2017 8:50 AM
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Saturday, June 3, 2017 7:37 AM
  • Eve

    Thanks for your initial reply. Unfortunately I have already tried your suggestions and they did not work.

    Monday, June 5, 2017 1:31 PM
  • My script should help fix it for you. It more than likely has to do with lack of maintenance on the WSUS Server, specifically declining superseded updates.

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    What it does:

    1. Remove all Drivers from the WSUS Database.
    2. Shrink your WSUSContent folder's size by declining superseded updates.
    3. Remove declined updates from the WSUS Database.
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    5. Compress Update Revisions.
    6. Remove Obsolete Updates.
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
    9. Run the Recommended SQL database Maintenance script on the actual SQL database.
    10. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

    .\Clean-WSUS.ps1 -FirstRun

    and then

    .\Clean-WSUS.ps1 -InstallTask

    If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Tuesday, June 6, 2017 12:31 AM
  • Thanks Adam I'll give this a go.
    Tuesday, June 20, 2017 3:51 PM
  • Adam

    Our SBS 2008 server has PowerShell v2.0 installed. From looking around online it appears that upgrading PowerShell on SBS 2008 to version 3 can cause problems with Exchange and some of the wizards that the OS uses.

    Wednesday, June 21, 2017 8:27 AM
  • From my Pre-reqs

     

        - For SBS:

            - This script WILL work on SBS - you must install the pre-requisites above depending on your underlying OS. .NET 4 is

              backwards compatible and I have a lot of users who have installed it on SBS and use the script.

     

    Please see my comments (OverDrive) and the run through here:

     

    https://community.spiceworks.com/topic/1999958-need-help-getting-rid-of-wsuscontent-files

     

    Everything revolves around old information.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Wednesday, June 21, 2017 4:01 PM