locked
Clients wont update from WSUS - Error Code 8024401C RRS feed

  • Question

  • I can't figure out why clients wont update from wsus server, also server shows " This computer has not reported status in 94 or more days"

    Here is the client log:

    2017-07-25 18:00:30:008 12708 395c Misc ===========  Logging initialized (build: 7.9.9600.18696, tz: -0600)  ===========
    2017-07-25 18:00:30:008 12708 395c Misc  = Process: C:\Windows\system32\wusa.exe
    2017-07-25 18:00:30:008 12708 395c Misc  = Module: C:\Windows\System32\wuapi.dll
    2017-07-25 18:00:30:007 12708 395c COMAPI -----------  COMAPI: IUpdateServiceManager::AddScanPackageService  -----------
    2017-07-25 18:00:30:008 12708 395c COMAPI  - ServiceName = Windows Update Standalone Installer
    2017-07-25 18:00:30:008 12708 395c COMAPI  - ScanFileLocation = C:\ed4c5c85109e681daa224d2dd459\wsusscan.cab
    2017-07-25 18:00:30:013 1052 498 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\4d195d75-ba36-470b-9947-8207503a0608\Source.cab with dwProvFlags 0x00000080:
    2017-07-25 18:00:30:110 1052 498 Misc Microsoft signed: Yes
    2017-07-25 18:00:30:132 1052 498 DtaStor Default service for AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
    2017-07-25 18:00:30:132 1052 498 IdleTmr Incremented idle timer priority operation counter to 2
    2017-07-25 18:00:30:133 12708 395c COMAPI  - Added scan package service, ServiceID = {4D195D75-BA36-470B-9947-8207503A0608} Third party service
    2017-07-25 18:00:30:134 12708 395c COMAPI -------------
    2017-07-25 18:00:30:134 12708 395c COMAPI -- START --  COMAPI: Init Search [ClientId = wusa]
    2017-07-25 18:00:30:134 12708 395c COMAPI ---------
    2017-07-25 18:00:30:134 12708 395c COMAPI -------------
    2017-07-25 18:00:30:134 12708 395c COMAPI -- START --  COMAPI: Search [ClientId = wusa]
    2017-07-25 18:00:30:134 12708 395c COMAPI ---------
    2017-07-25 18:00:30:135 1052 498 IdleTmr WU operation (CSearchCall::Init ID 1377) started; operation # 113450; does use network; is not at background priority
    2017-07-25 18:00:30:135 1052 498 IdleTmr Incremented idle timer priority operation counter to 3
    2017-07-25 18:00:30:135 1052 498 Agent *** START ***  Queueing Finding updates [CallerId = wusa  Id = 1377]
    2017-07-25 18:00:30:135 12708 395c COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = wusa]
    2017-07-25 18:00:30:135 1052 1b94 Agent ***  END  ***  Queueing Finding updates [CallerId = wusa  Id = 1377]
    2017-07-25 18:00:30:136 1052 1b94 Agent *************
    2017-07-25 18:00:30:136 1052 1b94 Agent ** START **  Agent: Finding updates [CallerId = wusa  Id = 1377]
    2017-07-25 18:00:30:136 1052 1b94 Agent *********
    2017-07-25 18:00:30:136 1052 1b94 Agent  * Online = Yes; Ignore download priority = No
    2017-07-25 18:00:30:136 1052 1b94 Agent  * Criteria = "DeploymentAction='Installation'"
    2017-07-25 18:00:30:136 1052 1b94 Agent  * ServiceID = {4D195D75-BA36-470B-9947-8207503A0608} Third party service
    2017-07-25 18:00:30:136 1052 1b94 Agent  * Search Scope = {Machine}
    2017-07-25 18:00:30:136 1052 1b94 Agent  * Caller SID for Applicability: S-1-5-21-305602047-4289685147-2902756900-2119
    2017-07-25 18:00:30:136 1052 1b94 Agent  * RegisterService is set
    2017-07-25 18:00:30:213 1052 1b94 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2017-07-25 18:00:30:213 1052 1b94 PT  + Offline serviceId = {4D195D75-BA36-470B-9947-8207503A0608}
    2017-07-25 18:00:30:214 1052 1b94 PT WARNING: Cached cookie has expired or new PID is available
    2017-07-25 18:00:30:214 1052 1b94 Agent Reading cached app categories using lifetime 604800 seconds
    2017-07-25 18:00:30:214 1052 1b94 Agent Read 0 cached app categories
    2017-07-25 18:00:30:214 1052 1b94 Agent SyncUpdates adding 0 visited app categories
    2017-07-25 18:00:30:257 1052 1b94 Agent Reading cached app categories using lifetime 604800 seconds
    2017-07-25 18:00:30:257 1052 1b94 Agent Read 0 cached app categories
    2017-07-25 18:00:30:257 1052 1b94 Agent SyncUpdates adding 0 visited app categories
    2017-07-25 18:00:30:285 1052 1b94 Agent Reading cached app categories using lifetime 604800 seconds
    2017-07-25 18:00:30:285 1052 1b94 Agent Read 0 cached app categories
    2017-07-25 18:00:30:285 1052 1b94 Agent SyncUpdates adding 0 visited app categories
    2017-07-25 18:00:30:623 1052 1b94 Agent Reading cached app categories using lifetime 604800 seconds
    2017-07-25 18:00:30:623 1052 1b94 Agent Read 0 cached app categories
    2017-07-25 18:00:30:623 1052 1b94 Agent SyncUpdates adding 0 visited app categories
    2017-07-25 18:00:30:778 1052 1b94 Agent Reading cached app categories using lifetime 604800 seconds
    2017-07-25 18:00:30:778 1052 1b94 Agent Read 0 cached app categories
    2017-07-25 18:00:30:778 1052 1b94 Agent SyncUpdates adding 0 visited app categories
    2017-07-25 18:00:30:792 1052 1b94 Agent Reading cached app categories using lifetime 604800 seconds
    2017-07-25 18:00:30:792 1052 1b94 Agent Read 0 cached app categories
    2017-07-25 18:00:30:792 1052 1b94 Agent SyncUpdates adding 0 visited app categories
    2017-07-25 18:00:30:798 1052 1b94 PT  + SyncUpdates round trips: 5
    2017-07-25 18:00:32:198 1052 1b94 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2017-07-25 18:00:32:198 1052 1b94 PT  + Offline serviceId = {4D195D75-BA36-470B-9947-8207503A0608}
    2017-07-25 18:00:32:233 1052 1b94 Agent  * Found 0 updates and 59 categories in search; evaluated appl. rules of 134 out of 297 deployed entities
    2017-07-25 18:00:32:234 1052 1b94 Agent *********
    2017-07-25 18:00:32:234 1052 1b94 Agent **  END  **  Agent: Finding updates [CallerId = wusa  Id = 1377]
    2017-07-25 18:00:32:234 1052 1b94 Agent *************
    2017-07-25 18:00:32:234 1052 1b94 IdleTmr WU operation (CSearchCall::Init ID 1377, operation # 113450) stopped; does use network; is not at background priority
    2017-07-25 18:00:32:234 1052 1b94 IdleTmr Decremented idle timer priority operation counter to 2
    2017-07-25 18:00:32:234 12708 2c70 COMAPI >>--  RESUMED  -- COMAPI: Search [ClientId = wusa]
    2017-07-25 18:00:32:235 12708 2c70 COMAPI  - Updates found = 0
    2017-07-25 18:00:32:235 12708 2c70 COMAPI ---------
    2017-07-25 18:00:32:235 12708 2c70 COMAPI --  END  --  COMAPI: Search [ClientId = wusa]
    2017-07-25 18:00:32:235 12708 2c70 COMAPI -------------
    2017-07-25 18:00:35:119 12708 395c COMAPI -----------  COMAPI: IUpdateServiceManager::RemoveService  -----------
    2017-07-25 18:00:35:119 12708 395c COMAPI  - ServiceId = {4d195d75-ba36-470b-9947-8207503a0608}
    2017-07-25 18:00:35:120 1052 498 IdleTmr Decremented idle timer priority operation counter to 1
    2017-07-25 18:00:35:135 12708 395c COMAPI IUpdateService removing volatile scan package service, serviceID = {4D195D75-BA36-470B-9947-8207503A0608}
    2017-07-25 18:00:35:136 1052 498 Agent WARNING: WU client fails CClientCallRecorder::RemoveService with error 0x80248014
    2017-07-25 18:00:35:136 12708 395c COMAPI WARNING: ISusInternal::RemoveService failed, hr=80248014
    2017-07-25 18:02:17:299 1052 5130 AU Triggering AU detection through DetectNow API
    2017-07-25 18:02:17:299 1052 5130 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
    2017-07-25 18:02:17:299 1052 5130 AU Triggering Online detection (interactive)
    2017-07-25 18:02:17:299 1052 5130 AU Adding timer: 
    2017-07-25 18:02:17:299 1052 5130 AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2017-07-26 00:02:17, not idle-only, not network-only
    2017-07-25 18:02:17:300 1052 20ec AU #############
    2017-07-25 18:02:17:300 1052 20ec AU ## START ##  AU: Search for updates
    2017-07-25 18:02:17:300 1052 20ec AU #########
    2017-07-25 18:02:17:300 1052 20ec SLS Retrieving SLS response from server using ETAG "4V8nqvoeoxgpu+6kKNNNGpLr4BCvPTmaz82CIDm5o5g=_1440"...
    2017-07-25 18:02:17:301 1052 20ec SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=148&L=en-US&P=&PT=0x4&WUA=7.9.9600.18696
    2017-07-25 18:02:17:783 1052 20ec EP FATAL: EP: Failed to obtain element node, error = 0x80245002
    2017-07-25 18:02:17:783 1052 20ec EP FATAL: Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL, error = 0x80245002
    2017-07-25 18:02:17:784 1052 20ec Agent WARNING: Failed to obtain the authorization cab URL for service 855e8a7c-ecb4-4ca3-b045-1dfa50104289, hr=0
    2017-07-25 18:02:17:784 1052 20ec AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
    2017-07-25 18:02:17:784 1052 20ec IdleTmr WU operation (CSearchCall::Init ID 1378) started; operation # 113460; does use network; is not at background priority
    2017-07-25 18:02:17:784 1052 20ec IdleTmr Incremented idle timer priority operation counter to 2
    2017-07-25 18:02:17:784 1052 20ec Agent *** START ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1378]
    2017-07-25 18:02:17:784 1052 20ec AU <<## SUBMITTED ## AU: Search for updates  [CallId = {39F6019D-0A6C-4697-B649-94CD9961EB3C} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2017-07-25 18:02:17:784 1052 1580 Agent ***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1378]
    2017-07-25 18:02:17:784 1052 1580 Agent *************
    2017-07-25 18:02:17:784 1052 1580 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1378]
    2017-07-25 18:02:17:784 1052 1580 Agent *********
    2017-07-25 18:02:17:784 1052 1580 Agent  * Online = Yes; Ignore download priority = No
    2017-07-25 18:02:17:784 1052 1580 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-07-25 18:02:17:784 1052 1580 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2017-07-25 18:02:17:784 1052 1580 Agent  * Search Scope = {Machine & All Users}
    2017-07-25 18:02:17:784 1052 1580 Agent  * Caller SID for Applicability: S-1-5-21-305602047-4289685147-2902756900-2119
    2017-07-25 18:02:17:784 1052 1580 Agent  * RegisterService is set
    2017-07-25 18:02:17:784 1052 1580 EP Got WSUS Client/Server URL: "http://wsus.im.priv:8530/ClientWebService/client.asmx"
    2017-07-25 18:02:17:786 1052 1580 Setup Checking for agent SelfUpdate
    2017-07-25 18:02:17:786 1052 1580 Setup Client version: Core: 7.9.9600.18696  Aux: 7.9.9600.18696
    2017-07-25 18:02:17:786 1052 1580 EP Got WSUS SelfUpdate URL: "http://wsus.im.priv:8530/selfupdate"
    2017-07-25 18:02:17:795 1052 1580 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2017-07-25 18:02:17:799 1052 1580 Misc Microsoft signed: NA
    2017-07-25 18:02:17:799 1052 1580 Misc Infrastructure signed: Yes
    2017-07-25 18:02:17:802 1052 1580 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP4792.tmp with dwProvFlags 0x00000080:
    2017-07-25 18:02:17:805 1052 1580 Misc Microsoft signed: NA
    2017-07-25 18:02:17:805 1052 1580 Misc Infrastructure signed: Yes
    2017-07-25 18:02:17:807 1052 1580 Setup FATAL: GetClientUpdateUrl failed, err = 0x8024D009
    2017-07-25 18:02:17:807 1052 1580 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2017-07-25 18:02:17:807 1052 1580 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2017-07-25 18:02:19:176 1052 1580 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2017-07-25 18:02:19:176 1052 1580 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus.im.priv:8530/ClientWebService/client.asmx
    2017-07-25 18:02:19:176 1052 1580 IdleTmr WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 113461; does use network; is at background priority
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: Nws Failure: errorCode=0x803d0006
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: Original error code: 0x80072ee2
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: There was an error communicating with the endpoint at 'http://wsus.im.priv:8530/ClientWebService/client.asmx'.
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: There was an error receiving the HTTP reply.
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: The operation did not complete within the time allotted.
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: The operation timed out
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: MapToSusHResult mapped Nws error 0x803d0006 to 0x8024401c
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: Web service call failed with hr = 8024401c.
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: Current service auth scheme='None'.
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
    2017-07-25 18:03:20:800 1052 1580 WS FATAL: OnCallFailure failed with hr=0X8024401C
    2017-07-25 18:03:20:800 1052 1580 WS WARNING: NWS retry 1 for transient error 0x8024401C
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: Nws Failure: errorCode=0x803d0006
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: Original error code: 0x80072ee2
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: There was an error communicating with the endpoint at 'http://wsus.im.priv:8530/ClientWebService/client.asmx'.
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: There was an error receiving the HTTP reply.
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: The operation did not complete within the time allotted.
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: There was an error communicating with the endpoint at 'http://wsus.im.priv:8530/ClientWebService/client.asmx'.
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: There was an error receiving the HTTP reply.
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: The operation did not complete within the time allotted.
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: The operation timed out
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: MapToSusHResult mapped Nws error 0x803d0006 to 0x8024401c
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: Web service call failed with hr = 8024401c.
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: Current service auth scheme='None'.
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
    2017-07-25 18:04:23:659 1052 1580 WS FATAL: OnCallFailure failed with hr=0X8024401C
    2017-07-25 18:04:23:659 1052 1580 WS WARNING: NWS retry 2 for transient error 0x8024401C
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: Nws Failure: errorCode=0x803d0006
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: Original error code: 0x80072ee2
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: There was an error communicating with the endpoint at 'http://wsus.im.priv:8530/ClientWebService/client.asmx'.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: There was an error receiving the HTTP reply.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: The operation did not complete within the time allotted.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: There was an error communicating with the endpoint at 'http://wsus.im.priv:8530/ClientWebService/client.asmx'.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: There was an error receiving the HTTP reply.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: The operation did not complete within the time allotted.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: There was an error communicating with the endpoint at 'http://wsus.im.priv:8530/ClientWebService/client.asmx'.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: There was an error receiving the HTTP reply.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: The operation did not complete within the time allotted.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: The operation timed out
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: MapToSusHResult mapped Nws error 0x803d0006 to 0x8024401c
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: Web service call failed with hr = 8024401c.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: Current service auth scheme='None'.
    2017-07-25 18:05:29:121 1052 1580 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
    2017-07-25 18:05:29:121 1052 1580 WS FATAL: OnCallFailure failed with hr=0X8024401C
    2017-07-25 18:05:29:121 1052 1580 IdleTmr WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 113461) stopped; does use network; is at background priority
    2017-07-25 18:05:29:121 1052 1580 PT WARNING: PTError: 0x8024401c
    2017-07-25 18:05:29:121 1052 1580 PT WARNING: GetConfig_WithRecovery failed: 0x8024401c
    2017-07-25 18:05:29:121 1052 1580 PT WARNING: RefreshConfig failed: 0x8024401c
    2017-07-25 18:05:29:121 1052 1580 PT WARNING: RefreshPTState failed: 0x8024401c
    2017-07-25 18:05:29:121 1052 1580 PT  + SyncUpdates round trips: 0
    2017-07-25 18:05:29:121 1052 1580 PT WARNING: Sync of Updates: 0x8024401c
    2017-07-25 18:05:29:121 1052 1580 PT WARNING: SyncServerUpdatesInternal failed: 0x8024401c
    2017-07-25 18:05:29:121 1052 1580 Agent  * WARNING: Failed to synchronize, error = 0x8024401C
    2017-07-25 18:05:29:123 1052 1580 Agent  * WARNING: Exit code = 0x8024401C
    2017-07-25 18:05:29:123 1052 1580 Agent *********
    2017-07-25 18:05:29:123 1052 1580 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1378]
    2017-07-25 18:05:29:123 1052 1580 Agent *************
    2017-07-25 18:05:29:123 1052 1580 Agent WARNING: WU client failed Searching for update with error 0x8024401c
    2017-07-25 18:05:29:124 1052 1580 IdleTmr WU operation (CSearchCall::Init ID 1378, operation # 113460) stopped; does use network; is not at background priority
    2017-07-25 18:05:29:124 1052 1580 IdleTmr Decremented idle timer priority operation counter to 1
    2017-07-25 18:05:29:124 1052 29a0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {39F6019D-0A6C-4697-B649-94CD9961EB3C} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2017-07-25 18:05:29:124 1052 29a0 AU  # WARNING: Search callback failed, result = 0x8024401C
    2017-07-25 18:05:29:124 1052 29a0 AU #########
    2017-07-25 18:05:29:124 1052 29a0 AU ##  END  ##  AU: Search for updates  [CallId = {39F6019D-0A6C-4697-B649-94CD9961EB3C} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2017-07-25 18:05:29:124 1052 29a0 AU #############
    2017-07-25 18:05:29:124 1052 29a0 AU All AU searches complete.
    2017-07-25 18:05:29:124 1052 29a0 AU  # WARNING: Failed to find updates with error code 8024401c
    2017-07-25 18:05:29:124 1052 29a0 AU AU setting next detection timeout to 2017-07-26 05:05:29
    2017-07-25 18:05:29:124 1052 29a0 AU Adding timer: 
    2017-07-25 18:05:29:124 1052 29a0 AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2017-07-26 05:05:29, not idle-only, not network-only
    2017-07-25 18:05:29:124 1052 29a0 AU  # Publishing WNF Per user update count event Count: 35 SID {S-1-5-21-305602047-4289685147-2902756900-2119} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
    2017-07-25 18:05:29:124 1052 29a0 AU  # Publishing WNF Per user update count event Count: 36 SID {S-1-5-21-1645336369-2456997488-292436562-1001} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
    2017-07-25 18:05:29:124 1052 29a0 AU  # Publishing WNF Per user update count event Count: 29 SID {S-1-5-21-305602047-4289685147-2902756900-9190} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
    2017-07-25 18:05:29:125 1052 29a0 AU Currently AUX is enabled - so not show any WU Upgrade notifications.
    2017-07-25 18:05:29:150 1052 29a0 AU IsPerUserUpdateInstallableForAnyLoggedOnUser, found at least 1 logged on user for which the update AC8BA605-5FB4-41BA-B63E-223465AEDF98, revision 1 is applicable
    2017-07-25 18:05:34:123 1052 f14 Report REPORT EVENT: {D72D2407-BB36-469D-B097-8938782A8C89} 2017-07-25 18:05:29:123-0600 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c AutomaticUpdatesWuApp Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
    2017-07-25 18:05:34:123 1052 f14 Report WARNING: Failed to get ProtocolVersion: 8024043d
    2017-07-25 18:05:34:127 1052 f14 Report CWERReporter::HandleEvents - WER report upload completed with WER status 0x8 (hr=0)
    2017-07-25 18:05:34:127 1052 f14 Report WER Report sent: 7.9.9600.18696 0x8024401c(0) 00000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdatesWuApp {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2017-07-25 18:05:34:127 1052 f14 Report CWERReporter finished handling 1 events. (00000000)

    Any help is greatly appreciated!! 



    • Edited by JonnyG81 Wednesday, July 26, 2017 12:47 AM
    Wednesday, July 26, 2017 12:29 AM

Answers

  • You're welcome. Watch out for Version 3.0 in the next month or so. It boasts a 1000-1500 times speed increase (Yes you read that right) in database processing speed.

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

    • Marked as answer by JonnyG81 Friday, August 4, 2017 1:23 AM
    Friday, August 4, 2017 12:51 AM

All replies

  • Hi Sir,

    Have you tried to open the URL from WSUS client computer :

    http://wsus.im.priv:8530/ClientWebService/client.asmx

     

    Best Regards,

    Elton


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

    Thursday, July 27, 2017 8:16 AM
  • Yes, i get a reply

    Client Service

    You have created a service.

    To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:


    svcutil.exe http://wsus.im.priv:8530/ClientWebService/Client.asmx?wsdl
    You can also access the service description as a single file:

    http://wsus.im.priv:8530/ClientWebService/Client.asmx?singleWsdl
    This will generate a configuration file and a code file that contains the client class. Add the two files to your client application and use the generated client class to call the Service. For example:

    C#

    class Test
    {
        static void Main()
        {
            ClientWebServiceClient client = new ClientWebServiceClient();

            // Use the 'client' variable to call operations on the service.

            // Always close the client.
            client.Close();
        }
    }

    Visual Basic

    Class Test
        Shared Sub Main()
            Dim client As ClientWebServiceClient = New ClientWebServiceClient()
            ' Use the 'client' variable to call operations on the service.

            ' Always close the client.
            client.Close()
        End Sub
    End Class

    Saturday, July 29, 2017 9:07 PM
  • Is this Windows 10 1607 RTM? 1607 RTM has a known issue that it will lose communication with any WSUS server. The fix for this is to install a CU past September 2016 as it was fixed in the September 2016 CU. Unfortunately, if the system is already 1607 RTM, you have no choice but to use a 3rd party tool like PDQ Deploy or install the CU Manually on the machine.

    It's best to install the latest CU, but you can install any one past September and then WSUS will be able to communicate again with the machine.

    Also,

    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

    • Proposed as answer by AJTek.caMVP Friday, August 4, 2017 12:50 AM
    Saturday, July 29, 2017 9:23 PM
  • The issue is with all stations on the network about 350 with OS Win 7 and 8, the wsus server was install about 3 months and it worked fine the first but now they don't report back to the wsus.
    Saturday, July 29, 2017 11:27 PM
  • The issue is with all stations on the network about 350 with OS Win 7 and 8, the wsus server was install about 3 months and it worked fine the first but now they don't report back to the wsus.

    Use my script. It is the WSUS server that is causing the problem and my script fixes it.


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

    Saturday, July 29, 2017 11:44 PM
  • Thank you Adam it worked!!!
    Friday, August 4, 2017 12:29 AM
  • You're welcome. Watch out for Version 3.0 in the next month or so. It boasts a 1000-1500 times speed increase (Yes you read that right) in database processing speed.

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

    • Marked as answer by JonnyG81 Friday, August 4, 2017 1:23 AM
    Friday, August 4, 2017 12:51 AM