Jump to content


Fenney

error 0x80244007 sccm soap fault

Recommended Posts

Hello everyone, thank you for taking the time out to read the post.

 

For our infrastructure we use SCCM to monitor our servers and clients machines while also using it for deploying software and Windows updates. We ran some reports last week and discovered that some machines have not been receiving updates and being classed as "Unknown" to SCCM When checking the logs on the client machines we discovered the error 0x80244007. 

We believe the cause of this error to be server side and not client side. I applied multiple solutions such as a disk clean-up, Windows update trouble shooter, editing registry keys and deleting items in the software distribution folder (which was recommended to try from other forums) 

 We have also rebuilt one of the client machines and changed the build from 1903 to 1909 and 2004 which still did not allow us to pull any updates from SCCM which indicates that this is most likely server side. 

I am still currently a helpdesk technician but trying to understand SCCM as much as possible so I greatly appreciate any advice.

I have attached logs from SCCM  and the client machine which should be able to shed some light on the matter, if you need additional logs I will provide them

 Thanks

 

UpdatesStore.log WUAHandler.log UpdatesDeployment.log UpdatesHandler.log WUAHandler.log

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.