Share via

Patching Completion not reported

Duchemin, Dominique 2,006 Reputation points
2023-05-12T21:15:03.1333333+00:00

Hello,

I have several servers where the patching was completed but they never reported the completion to the Configuration manager Console...

I checked:

WUAHandler.log

OnSearchComplete - Failed to end search job. Error = 0x8024401c. WUAHandler 5/12/2023 2:09:08 PM 5676 (0x162C) Scan failed with error = 0x8024401c. WUAHandler 5/12/2023 2:09:08 PM 5676 (0x162C)

Also in the WindowsUpdate.log

2023/05/12 14:14:10.8225591 1012 6456 Agent * START * Queueing Finding updates [CallerId = CcmExec Id = 1392] 2023/05/12 14:14:10.8225650 1012 6456 Agent Removing service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 from sequential scan list 2023/05/12 14:14:10.8225680 1012 6456 Agent Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is not in sequential scan list 2023/05/12 14:14:10.8225723 1012 6456 Agent Added service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 to sequential scan list 2023/05/12 14:14:10.8226999 1012 5956 Agent Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is in sequential scan list 1600/12/31 16:00:00.0000000 8124 7196 Unknown( 12): GUID=eb73583d-5481-33b4-202d-9bb270eddffa (No Format Information found). 2023/05/12 14:14:10.8240204 1012 1992 Agent * END * Queueing Finding updates [CallerId = CcmExec Id = 1392] 2023/05/12 14:14:10.8250128 1012 1992 Agent * START * Finding updates CallerId = CcmExec Id = 1392 2023/05/12 14:14:10.8250141 1012 1992 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = Yes 2023/05/12 14:14:10.8250150 1012 1992 Agent Criteria = (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')"" 2023/05/12 14:14:10.8250265 1012 1992 Agent ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed 2023/05/12 14:14:10.8250273 1012 1992 Agent Search Scope = {Machine} 2023/05/12 14:14:10.8250295 1012 1992 Agent Caller SID for Applicability: S-1-5-18 2023/05/12 14:14:10.8250303 1012 1992 Agent Include potentially superseded updates is set 2023/05/12 14:14:10.8250303 1012 1992 Agent RegisterService is set 2023/05/12 14:14:10.8259255 1012 1992 Misc Got WSUS Client/Server URL: https://SU-SCCM-P1.ad:8531/ClientWebService/client.asmx"" 2023/05/12 14:14:10.8285435 1012 1992 WebServices Proxy Behavior set to 1 for service url https://SU-SCCM-P1.ad:8531/ClientWebService/client.asmx 2023/05/12 14:14:10.8287811 1012 1992 ProtocolTalker WSUS certificate store is empty 2023/05/12 14:14:10.8287820 1012 1992 WebServices WSUS TLS cert-pinning mandatory: No 2023/05/12 14:14:10.8287829 1012 1992 ProtocolTalker Proxy Behavior set to 1 for service url https://SU-SCCM-P1.ad:8531/ClientWebService/client.asmx 2023/05/12 14:14:11.3952926 1012 1992 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://SU-SCCM-P1.ad:8531/ClientWebService/client.asmx 2023/05/12 14:14:11.3952977 1012 1992 ProtocolTalker OK to reuse existing configuration 2023/05/12 14:14:11.3953024 1012 1992 ProtocolTalker Cached cookie has expired or new PID is available 2023/05/12 14:14:11.3953152 1012 1992 Misc Got WSUS SimpleTargeting URL: https://SU-SCCM-P1.ad:8531"" 2023/05/12 14:14:11.3976469 1012 1992 WebServices Proxy Behavior set to 1 for service url https://SU-SCCM-P1.ad:8531/SimpleAuthWebService/SimpleAuth.asmx 2023/05/12 14:14:11.3978747 1012 1992 ProtocolTalker WSUS certificate store is empty 2023/05/12 14:14:11.3978756 1012 1992 WebServices WSUS TLS cert-pinning mandatory: No 2023/05/12 14:14:11.3978765 1012 1992 ProtocolTalker Proxy Behavior set to 1 for service url https://SU-SCCM-P1.ad:8531/SimpleAuthWebService/SimpleAuth.asmx 2023/05/12 14:14:11.3979537 1012 1992 ProtocolTalker Initializing simple targeting cookie, clientId = c1216479-257d-4b89-9da7-0850a2bced18, target group = <NULL>, DNS name = vipsccmdp01.ad 2023/05/12 14:14:11.3979545 1012 1992 ProtocolTalker Server URL = https://SU-SCCM-P1.ad:8531/SimpleAuthWebService/SimpleAuth.asmx 2023/05/12 14:14:11.3979818 1012 1992 WebServices Auto proxy settings for this web service call. 2023/05/12 14:14:32.4026829 1012 1992 WebServices WS error: There was an error communicating with the endpoint at 'https://SU-SCCM-P1.ad:8531/SimpleAuthWebService/SimpleAuth.asmx'. 2023/05/12 14:14:32.4027050 1012 1992 WebServices WS error: The operation timed out 2023/05/12 14:14:32.4027063 1012 1992 WebServices Web service call failed with hr = 8024401c. 2023/05/12 14:14:32.4027068 1012 1992 WebServices Current service auth scheme=0. 2023/05/12 14:14:32.4027072 1012 1992 WebServices Current Proxy auth scheme=0. 2023/05/12 14:14:34.4038314 1012 1992 WebServices Auto proxy settings for this web service call. 2023/05/12 14:14:55.4088124 1012 1992 WebServices WS error: There was an error communicating with the endpoint at 'https://SU-SCCM-P1.ad:8531/SimpleAuthWebService/SimpleAuth.asmx'. 2023/05/12 14:14:55.4088367 1012 1992 WebServices WS error: The operation timed out 2023/05/12 14:14:55.4088380 1012 1992 WebServices Web service call failed with hr = 8024401c. 2023/05/12 14:14:55.4088384 1012 1992 WebServices Current service auth scheme=0. 2023/05/12 14:14:55.4088388 1012 1992 WebServices Current Proxy auth scheme=0. 2023/05/12 14:14:57.4094780 1012 1992 WebServices Auto proxy settings for this web service call. 2023/05/12 14:15:18.4144849 1012 1992 WebServices WS error: There was an error communicating with the endpoint at 'https://SU-SCCM-P1.ad:8531/SimpleAuthWebService/SimpleAuth.asmx'. 2023/05/12 14:15:18.4145092 1012 1992 WebServices WS error: The operation timed out 2023/05/12 14:15:18.4145109 1012 1992 WebServices Web service call failed with hr = 8024401c. 2023/05/12 14:15:18.4145114 1012 1992 WebServices Current service auth scheme=0. 2023/05/12 14:15:18.4145118 1012 1992 WebServices Current Proxy auth scheme=0. 2023/05/12 14:15:18.4145271 1012 1992 WebServices Failed in NwsCallWithRetries( _clientId, _targetGroupName, _dnsName, &_result -> HRESULT { return SimpleAuthService::SimpleAuthSoap_GetAuthorizationCookie( NWSCALL_HEAD_PARAMS, _clientId, _targetGroupName, _dnsName, &_result, NWSCALL_TAIL_PARAMS); }, pcTransientErrorRetries): 0X8024401C 2023/05/12 14:15:18.4146667 1012 1992 ProtocolTalker Failed to initialize Simple Targeting Cookie 0x8024401c 2023/05/12 14:15:18.4146696 1012 1992 ProtocolTalker PopulateAuthCookies failed 0x8024401c 2023/05/12 14:15:18.4146705 1012 1992 ProtocolTalker RefreshCookie failed 0x8024401c 2023/05/12 14:15:18.4146726 1012 1992 ProtocolTalker RefreshPTState failed 0x8024401c 2023/05/12 14:15:18.4146735 1012 1992 ProtocolTalker SyncUpdates round trips: 0 2023/05/12 14:15:18.4146739 1012 1992 ProtocolTalker Sync of Updates 0x8024401c 2023/05/12 14:15:18.4146769 1012 1992 ProtocolTalker SyncServerUpdatesInternal failed 0x8024401c 2023/05/12 14:15:18.4159445 1012 1992 Agent Failed to synchronize, error = 0x8024401C 2023/05/12 14:15:18.4291546 1012 1992 Agent Exit code = 0x8024401C 2023/05/12 14:15:18.4291554 1012 1992 Agent * END * Finding updates CallerId = CcmExec Id = 1392

Any idea?

Thanks,

Dom

Microsoft Configuration Manager
0 comments

8 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. AllenLiu-MSFT 44,496 Reputation points Microsoft Vendor
    2023-05-15T06:29:54.48+00:00

    Hi, @Duchemin, Dominique

    Thank you for posting in Microsoft Q&A forum.

    0x8024401c means Same as HTTP status 408 - the server timed out waiting for the request.

    You may try to change some settings on the wsus server like this thread:

    https://community.spiceworks.com/topic/1970827-wsus-on-server-2016-windows-10-1607-client-0x8024401c-error

    And try to repair the wsus agent with:

    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f

    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIdValidation /f

    net stop wuauserv

    move %windir%\windowsupdate.log %windir%\windowsupdate.old.log

    move %windir%\SoftwareDistribution %windir%\SoftwareDistributionold

    regsvr32 /s atl.dll

    regsvr32 /s wucltui.dll

    regsvr32 /s wups.dll

    regsvr32 /s wuaueng.dll

    regsvr32 /s wuapi.dll

    regsvr32 /s msxml3.dll

    regsvr32 /s mssip32.dll

    regsvr32 /s initpki.dll

    regsvr32 /s softpub.dll

    net start wuauserv

    wuauclt /resetauthorization /detectnow

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

  2. Adam J. Marshall 9,381 Reputation points MVP
    2023-05-16T16:27:38.4033333+00:00

    The reporting does start with the client system - the Windows Update Agent (See https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/), but the other side of it is that the WSUS server needs to be also working properly to receive the information. Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

    Most issues are resolved by doing the proper maintenance that WSUS requires.

  3. Duchemin, Dominique 2,006 Reputation points
    2023-05-16T16:46:08.12+00:00

    Hello,

    Yes the Maintenance is done monthly and for this particular issue it has even been done several times\

    Thanks,

    Dom

    0 comments
  4. Adam J. Marshall 9,381 Reputation points MVP
    2023-05-16T16:54:32.2766667+00:00

    There was an error communicating with the endpoint at 'https://SU-SCCM-P1.ad:8531/SimpleAuthWebService/SimpleAuth.asmx'. 2023/05/12 14:14:32.4027050 1012 1992 WebServices WS error: The operation timed out

    IIS issues relating to WSUS. Check the WSUS Application Pool, and all the other adjustments Microsoft suggests for IIS on their guide for WSUS (linked in part 8 of my blog series above).

  5. Duchemin, Dominique 2,006 Reputation points
    2023-05-19T00:20:35.5666667+00:00

    Hello,

    The Application Pool have been changed accordingly to the request in part 8 above...

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

    but no change for the reporting still not working...

    Thanks,
    Dom

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.