SOLVED Error 0x8024400d Scan failed with error 0x8024400d

[Shibalik Sanyal]

Hi Prajwal,

In our environment, We have around 8K machines and patching of all these clients are being taken care by SCCM. Recently, from last 2 to 3 weeks we are facing an issue where around 200 clients stopped scanning for updates.

In WUAHandler.log, we are getting the below error message,

OnSearchComplete - Failed to end search job. Error = 0x8024400d.
Scan failed with error = 0x8024400d.

So eventually I checked the WindowsUpdate.log, and found the below errors,

2016-02-25 04:25:25:408 344 7d0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://abc123.mydomain.local:8530/ClientWebService/client.asmx
2016-02-25 04:25:26:302 344 7d0 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2016-02-25 04:25:26:302 344 7d0 PT WARNING: SOAP Fault: 0x00012c
2016-02-25 04:25:26:302 344 7d0 PT WARNING: faultstring:Fault occurred
2016-02-25 04:25:26:302 344 7d0 PT WARNING: ErrorCode:InvalidParameters(7)
2016-02-25 04:25:26:302 344 7d0 PT WARNING: Message: parameters.OtherCachedUpdateIDs
2016-02-25 04:25:26:302 344 7d0 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2016-02-25 04:25:26:302 344 7d0 PT WARNING: ID:ede20d2a-2d41-4e62-91c2-573c1fe3351b
2016-02-25 04:25:26:302 344 7d0 PT WARNING: PTError: 0x8024400d
2016-02-25 04:25:26:302 344 7d0 PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
2016-02-25 04:25:26:302 344 7d0 PT WARNING: Sync of Updates: 0x8024400d
2016-02-25 04:25:26:302 344 7d0 PT WARNING: SyncServerUpdatesInternal failed: 0x8024400d
2016-02-25 04:25:26:302 344 7d0 Agent * WARNING: Failed to synchronize, error = 0x8024400D
2016-02-25 04:25:26:303 344 7d0 Agent * WARNING: Exit code = 0x8024400D
2016-02-25 04:25:26:303 344 7d0 Agent WARNING: WU client failed Searching for update with error 0x8024400d
2016-02-25 04:25:26:315 1928 1344 COMAPI - WARNING: Exit code = 0x00000000, Result code = 0x8024400D
2016-02-25 04:25:26:317 1928 1344 COMAPI WARNING: Operation failed due to earlier error, hr=8024400D
2016-02-25 04:25:31:303 344 7d0 Report REPORT EVENT: {96D9598F-A59C-4325-8791-44297CFB4553} 2016-02-25 04:25:26:303-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400d CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400d.

So, upon searching about this error, I have so far done the following,
1. Repaired SCCM Client and even re-installed it
2. Repaired WMI
3. Checked registry and found 2 entries of windows update in HKLM/Software/Microsoft/Windows/Currentversion with different SUSclientids and versionids
5. Compared the settings with another client where scan is successful and deleted the wrong windows update key from registry.
6. Also deleted susclientid and versionid
7. deleted windowsupdate.log
8. Reauthorized Windows Update
9. Registered all the dlls again.
10. Ran Software Update Readiness Tool

Also in WindowsUpdate.log, I am getting error 0x80244010 : Exceeded max server round trips

I have checked different websites and blogs, they are saying to extend the default cache size from 20000 to higher in WSUS.

There are clients facing all other different issues, but we have most clients under this category.

I have run the report, "Troubleshooting 2 - Deployment Errors" and found the error mentioned against the error code 8024400D is "Same as SOAP_E_CLIENT - SOAP client found the message was malformed; fix before resending."

Can you please help with this?

Thanks

 

[Shibalik Sanyal]

Also I have checked the WSUS connectivity from client by doing Telnet <server name> <port> and it is not reflecting any error. Instead, it is opening a blank cmd window. Honestly, I do not know what to do next but as there were no error, I guess the connectivity is there. Also I have tried to open http://abc123.mydomain.local/simpleauthwebservice/simpleauth.asmx, it is connecting to the page. Also I have checked http://abc123.mydomain.local:8530/selfupdate/wuident.cab and I can download the cab file.

 

[Prajwal Desai]

Did you check this - https://blogs.technet.microsoft.com...zation-with-0x80244015-and-0x8024400d-errors/

 

[Shibalik Sanyal]

Hi Prajwal,

Really sorry for the late response. I have checked this article before. I have shared the same thoughts of cleaning up the WSUS or if requires re-install with my L3. Apart from that, is there anything else that I can try from the client end? As I have mentioned earlier that there are other issues as well but when I am checking each machines tagged with different error codes in SCCM reprots, they are basically giving the same error of 8024400D. Right now I am completely clueless as if what can be done next.

Beside this, I would like to inform you one more issue.

There are some clients showing Update Installation "In progress" under Monitoring and that is for the updates from Jan. So there should be something wrong in it because a client should not take two months to install updates. I have checked the Windowsupdate.log, please check the below excerpt

2016-03-03 11:01:25:998 324 d80 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2016-03-03 11:01:25:998 324 d80 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://abc123.mydomain.local:8530/ClientWebService/client.asmx
2016-03-03 11:05:17:122 324 d80 PT WARNING: Exceeded max server round trips: 0x80244010
2016-03-03 11:05:17:122 324 d80 PT WARNING: SyncServerUpdatesInternal failed: 0x80244010
2016-03-03 11:05:17:122 324 a08 AU Can not perform non-interactive scan if AU is interactive-only
2016-03-03 11:05:17:122 324 d80 Agent * WARNING: Exit code = 0x80244010
2016-03-03 11:05:17:122 324 d80 Agent WARNING: WU client failed Searching for update with error 0x80244010
2016-03-03 11:05:17:184 324 d80 Report REPORT EVENT: {910BDE3B-4020-49D7-9DFB-AA6C002331B1} 2016-03-03 11:01:25:254-0000 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244010 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244010.

In WUAHandler.log getting the below error,

OnSearchComplete - Failed to end search job. Error = 0x80072ee6.
Scan failed with error = 0x80072ee6.

Also I have checked the StatusMessage.log. It is sending the status messages of the updates as they are installed (State ID 3 for Topic ID 500). When I checked the report for this machine from SSRS, beside those same updates, there is an error description "Scan tool for this update has failed". So I am completely confused why it is doing so. Any idea?

 

[Prajwal Desai]

Removing WSUS and reinstalling it should fix this issue.

 

[Shibalik Sanyal]

Yes, that is what I've suggested my L3. Let's see what happens as we will do that asap. I'll let you know the results

Thanks

 

[Prajwal Desai]

Were you able to fix this issue ?.

 

[Shibalik Sanyal]

Hi Prajwal,

Sorry for the late response. Actually I am on leave. But as far as the 8024400d issue is concerned, that got fixed by cleaning up wsus server. I have not got the full details as if what has been done. I will post the details as soon as I will join office.

Thanks for your help.

 

[Prajwal Desai]

Thank you. I will mark the thread as solved.