SCCM Status Message Data transfer service returned BITS error HTTP status 404

Question

Hello

Thank you in advance for any suggestions.

I recently Updates and Servicing on my SCCM environment. I am currently at Microsoft Endpoint Configuration Manager 2103, 5.00.9049.1000 and Client Version 5.00.9049.1010.

The trouble I am having is that when I deploy updates most computers are remaining in Unknown status of the deployment as Client Check passed/Active with some moving on to either In Progress or Compliant.

Some of the devices seem to actually be installing the updates but aren't reporting as such. I am able to perform IS Deployments and Application Deployments without issues.

All components under \Monitoring\Overview\System Status\Site Status and Component Status show as Ok with SMS_ISVUpdates_SyncAgent showing as a warning but that is related to my Adobe Catalog.

Any suggestions? Is the answer here to update to 2103 Hotfix Rollup or newer?

The client failed to download policy. The data transfer service returned "BITS error: 'HTTP status 404: The requested URL does not exist on the server.
' Context: 'The error occurred while the remote file was being processed.
'" (-2147024894).

Answer 1

@Jason Moran
Thanks for your posting on Q&A.

Is there any hot fixes about MECM 2103 which shown on the Updates and Servicing? I found the following document from MS, and it seems that the phenomenon is more similar to your’s.
https://learn.microsoft.com/en-us/mem/configmgr/hotfix/2103/9210721

If a client computer performs multiple software update scans in one pass, and one of the scans fails, overall compliance is incorrectly reported as 'Unknown'.

Please try to install the related hot fix as suggested.

Hope the above will be helpful.

Best regards,
Rita

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

After submitting a case with Microsoft, it seems there is a hardware policy that has been lost from the SCCM DB. This error although annoying to see in the logs doesn't seem to hinder OSD, Patching or App Deployments. As I am currently building a replacement SCCM environment from scratch I think I will let this slide.