This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 55.00000000000001%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDD%3C/text%3E%3C/svg%3E)
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
what does wsusutil checkhealth say?
also, try re-setting up SSL just 2 steps:
Hello @Adam Marschall
"WSUSUTIL": Should it be run on the Client or on the Software Update point server?
Thanks,
Dom
SUP - where WSUS is located as wsusutil is a utility for WSUS
Hello,
I tried on the SUP Server:
C:\Program Files\Update Services\Tools>wsusutil.exe checkhealth
Done. Please check event log for events with source "Windows Server Update
Services."
Which event log? System? Application? WindowsUpdateClient?
I tried the three of them and filer "Windows Server Update Services" and ll came back empty!!!
Thanks,
Dom
I finally got something after rerunning the command and waiting15 minutes !!!
Thanks,
Dom
We are fully HTTPS so using SSL.
Thanks,
Dom
Remember, WSUS uses BOTH HTTP and HTTPS when SSL is enabled. You can't turn off HTTP or you will encounter problems. Think of it like FTP using port 21 for the command channel and port 20 (or random above 1024 for passive FTP) for the data channel.
Yes I understand but if I have 73% success for the SUP Deployment it seems for me it is correctly configured... isn't it?
What do you mean by "turn off HHTP"? where this could be done? SUP Server? Network? Firewall?
This is an environment which is in place since 2007 ...
Thanks,
Dom
Hello,
WSUSUtil.exe CheckHealth on the SUP Server:
Log Name: Application
Source: Windows Server Update Services
Date: 5/19/2023 1:00:00 PM
Event ID: 12072
Task Category: 9
Level: Error
Keywords: Classic
User: N/A
Computer: VRPSCCMSU01.ad
Description:
The WSUS content directory is not accessible.
System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Server Update Services" />
<EventID Qualifiers="0">12072</EventID>
<Level>2</Level>
<Task>9</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-05-19T20:00:00.517831800Z" />
<EventRecordID>196973</EventRecordID>
<Channel>Application</Channel>
<Computer>VRPSCCMSU01.ad</Computer>
<Security />
</System>
<EventData>
<Data>The WSUS content directory is not accessible.
System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)</Data>
</EventData>
</Event>
-------------------------------------------------------------
Log Name: Application
Source: Windows Server Update Services
Date: 5/19/2023 1:00:00 PM
Event ID: 10032
Task Category: 7
Level: Error
Keywords: Classic
User: N/A
Computer: VRPSCCMSU01.ad
Description:
The server is failing to download some updates.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Server Update Services" />
<EventID Qualifiers="0">10032</EventID>
<Level>2</Level>
<Task>7</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-05-19T20:00:00.516830600Z" />
<EventRecordID>196972</EventRecordID>
<Channel>Application</Channel>
<Computer>VRPSCCMSU01.ad</Computer>
<Security />
</System>
<EventData>
<Data>The server is failing to download some updates.</Data>
</EventData>
</Event>
-------------------------------------------------------------
Log Name: Application
Source: Windows Server Update Services
Date: 5/19/2023 1:00:00 PM
Event ID: 13032
Task Category: 6
Level: Error
Keywords: Classic
User: N/A
Computer: VRPSCCMSU01.ad
Description:
Many client computers have not reported back to the server in the
last 30 days. 9037 have been detected so far.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Server Update Services" />
<EventID Qualifiers="0">13032</EventID>
<Level>2</Level>
<Task>6</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-05-19T20:00:00.515828900Z" />
<EventRecordID>196971</EventRecordID>
<Channel>Application</Channel>
<Computer>VRPSCCMSU01.ad</Computer>
<Security />
</System>
<EventData>
<Data>Many client computers have not reported back to the server in the
last 30 days. 9037 have been detected so far.</Data>
</EventData>
</Event>
-------------------------------------------------------------
Log Name: Application
Source: Windows Server Update Services
Date: 5/19/2023 1:00:00 PM
Event ID: 13001
Task Category: 6
Level: Warning
Keywords: Classic
User: N/A
Computer: VRPSCCMSU01.ad
Description:
Client computers are installing updates with a higher than 10 percent
failure rate. This should be monitored.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Server Update Services" />
<EventID Qualifiers="0">13001</EventID>
<Level>3</Level>
<Task>6</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-05-19T20:00:00.514830500Z" />
<EventRecordID>196970</EventRecordID>
<Channel>Application</Channel>
<Computer>VRPSCCMSU01.ad</Computer>
<Security />
</System>
<EventData>
<Data>Client computers are installing updates with a higher than 10 percent
failure rate. This should be monitored.</Data>
</EventData>
</Event>
See my comment above - HTTP is the issue - IIS needs to allow both HTTP and HTTPS for WSUS to work. Everything should be adjusted using wsusutil and NOT DONE MANUALLY in IIS.
Check your permissions - https://www.ajtek.ca/wsus/wsus-permissions-wsuscontent-registry-and-iis/
Nothing is done IIS all settings are done in Configuration Manager Console.
Hello,
the SUP Synchronizations are successful.
We have 33,000+ Clients so 9,037 failures it is high but not abnormal... Is it possible to split the failures by owners or groups or collections they are in...?
2023-05-19_13-41-22 SUP Configuration 01.png
Thanks,
Dom