ConfigMgr software update scan fails with 0x8024401c (WUAHandler) while WSUS logs InvalidParameters / OtherCachedUpdateIDs

PHUC Huynh 0 Reputation points
2026-11-17T08:20:14.37+00:00

image (2)

Error ConfigMgr clients fail the software update scan with 0x8024401c. WUAHandler.log shows "OnSearchComplete - Failed to end search job. Error = 0x8024401c" and "Scan failed with error = 0x8024401c". ScanAgent.log shows the same error. The failure occurs 6–8 seconds after the search starts.

Evidence

  • From an affected client, DNS resolves, and Selfupdate/wuident.cab, ClientWebService/wusserverversion.xml and SimpleAuthWebService/SimpleAuth.asmx all open on port 8530.
  • WSUS SoftwareDistribution.log (13–17 Nov) has 4,628 warnings from about 149 clients: ErrorCode=InvalidParameters, Message=parameters.OtherCachedUpdateIDs (ClientWebService/client.asmx)
  • It also has 192 SQL warnings: Number 515, "Cannot insert NULL into column 'RevisionID', table '@AtLeastOneBundle'".
  • Cleanup on 14 Nov processed 22,145 updates. Later runs show about 6,350.

Questions

  1. Is InvalidParameters / OtherCachedUpdateIDs the cause of the client 0x8024401c?
  2. Should I check or increase maxCachedUpdates and maxInstalledPrerequisites in the ClientWebService web.config, or is another limit involved?
  3. Could the SQL 515 warnings or the large catalog also cause this? What else should I check on WSUS and IIS?Error ConfigMgr clients fail the software update scan with 0x8024401c. WUAHandler.log shows "OnSearchComplete - Failed to end search job. Error = 0x8024401c" and "Scan failed with error = 0x8024401c". ScanAgent.log shows the same error. The failure occurs 6–8 seconds after the search starts.

image (2)

Microsoft System Center | Other
0 comments No comments

Your answer

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