sccm error 0x80244007 wsus scan failed soap fault

TL;DR

SCCM scan error 0x80244007 is a SOAP fault returned by WSUS when the client scan request hits a server-side problem, commonly an overloaded or unhealthy WSUS application pool, a database issue, or too many expired update revisions. Check WSUS health and run WSUS maintenance - decline superseded updates, clean obsolete revisions, and reindex - then test one client scan. The client is usually fine; rebuilding clients cannot fix a fault the server is generating.

sccm error 0x80244007 wsus scan failed soap fault

Use this when

• WUAHandler.log on multiple clients shows scan failed with 0x80244007 at similar times.
• WSUS synchronization works, but client scans time out or fault, especially in large environments.
• The SUSDB has not had maintenance in a long time and holds many superseded or expired revisions.

Not for this skill when

• Only one client faults while others scan fine against the same WSUS. Repair that client update agent.
• WSUS itself will not synchronize and shows its own sync error. Fix synchronization first.

Steps

1. Confirm scope and timing: sample WUAHandler.log from several clients in different collections and note whether the SOAP faults cluster at scan peaks. Server-side faults cluster; client-side faults scatter. Record the WSUS server and software update point involved. Verify: you can show the fault is shared across clients and time-clustered, pointing at the software update point
2. Check WSUS service health on the server: IIS WsusPool running, WSUS Administration site up, and the server not starved of memory or disk. Recycle the pool once in a quiet moment and immediately test a single client scan to see whether the fault clears temporarily. Verify: a single client scan succeeds after the recycle, or still faults and proves the cause is deeper than a stopped pool
3. Run WSUS maintenance in the right order: decline superseded updates that are no longer deployed, run the Server Cleanup Wizard for unused updates and revisions and obsolete computers, and remove expired revisions that inflate every scan response. This maintenance is the step most environments skip and the one that shrinks scan payloads back to a size the server can answer reliably. Verify: cleanup completes, superseded and expired counts drop visibly, and the SUSDB size or revision count is measurably smaller
4. Reindex and check the SUSDB using the Microsoft provided maintenance script or your DBA standard, then run a full synchronization so clients and server agree on the cleaned catalog. Watch the synchronization result rather than assuming success. Verify: the database maintenance completes without errors and the next synchronization reports success
5. Force a software update scan on the test client and monitor WUAHandler.log through completion, then let the normal scan schedule run for a full cycle and compare failure rates in the console before and after the maintenance. Verify: the test client scan completes, and fleet scan failures for 0x80244007 fall to near zero over the next cycle

Why it happens

A Configuration Manager client scan is a conversation with WSUS using SOAP requests, and WSUS answers from its catalog database. Over years, that catalog accumulates superseded revisions and expired updates that are still returned in scan responses, making each answer huge and slow until the request faults or times out at the server, which clients log as 0x80244007. Application pool pressure makes it worse at peak scan times. Microsoft designs WSUS to need regular declining, cleanup, and database reindexing; environments that skip maintenance eventually hit this fault at scale, and no amount of client repair changes the size of what the server is trying to answer.

Variants and edge cases

0x80244007 only during the morning scan peak

Demand shaping helps alongside maintenance: stagger scan schedules by collection so the software update point is not hit by the whole fleet within the same hour.

0x80244007 after enabling many new classifications or products

Newly enabled catalog volume can tip a marginal WSUS over the edge. Enable classifications in stages and run maintenance after large catalog additions.

0x80244007 with WID database instead of SQL Server

The internal database has the same maintenance needs and fewer tools. Use the cleanup wizard and consider migrating busy software update points to SQL Server for maintainability.

Compatibility: Applies to WSUS integrated with Microsoft Configuration Manager current branch as a software update point, using SQL Server or Windows Internal Database.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst__cEqDMWzxmgtwhrrM3RdnA