'BITS error: 'HTTP status 500: An unexpected condition prevented the server from fulfilling the request. ' Context: 'The error occurred while the remote file was being processed.

Question

I have one distribution point where the majority of the clients that attempt to download from get the following error in the DataTransferService.log:

'BITS error: 'HTTP status 500: An unexpected condition prevented the server from fulfilling the request.

' Context: 'The error occurred while the remote file was being processed.

The MP and a different DP do not have the same issue.

The result is that the clients that this server serves are not getting the latest Software updates.

Answer 1

The failure is isolated to the affected distribution point, so check its required WMI firewall rules when the client records 0x801901F4, then validate and redistribute the affected update content before investigating IIS.

1. Check the exact BITS error code

In DataTransferService.log, inspect the lines around the HTTP 500 message.

If the entry includes 0x801901F4, enable these inbound Windows Defender Firewall rules on the affected DP:

• Windows Management Instrumentation (DCOM-In)
• Windows Management Instrumentation (WMI-In)

Configuration Manager documents these as required DP firewall rules and specifically associates their absence with 0x801901F4 in DataTransferService.log.^1^

Use Windows Defender Firewall with Advanced Security → Inbound Rules, enable both rules, and retry a client download. Do not apply this as the primary fix if the log does not contain that code.

2. Validate and redistribute the failing update content

Because another DP works, first determine whether the failure affects particular update packages or every package on this DP.

1. In the Configuration Manager console, open Monitoring → Distribution Status → Content Status.
2. Select an affected software update package and choose View Status.
3. Check this DP’s state:
   • If it is under Error, open that tab, right-click the DP entry, and select Redistribute.
   • If it remains under In Progress, cancel the stalled distribution before starting redistribution.^2^
4. Run content validation for the package on the affected DP.
5. Wait for the package to report Success, then retry the deployment from one affected client.

Content Library Explorer can provide a more precise check:

1. Start ContentLibraryExplorer.exe.
2. Connect using the affected DP’s FQDN.
3. Select the package node—not an individual folder or content item.
4. Choose Package → Validate.
5. If content is missing or corrupt, choose Package → Redistribute.^3^

Do not manually modify or delete anything under SCCMContentLib; Microsoft recommends validation followed by redistribution because direct changes can corrupt the content library.^4^

3. Correlate the client request with the DP failure

If redistribution succeeds but clients still receive HTTP 500:

1. On an affected client, correlate the same content ID through:
   • CAS.log — selected content and DP location
   • ContentTransferManager.log — DP URL plus CTM/DTS job IDs
   • DataTransferService.log — BITS request and HTTP failure

These logs respectively track cache/content access, BITS scheduling, and BITS communication.^5^

2. Copy the exact failing DP URL and timestamp from ContentTransferManager.log or DataTransferService.log. Configuration Manager’s documented download flow shows how the content ID leads to the DP URL, DTS job, and BITS job.^6^
3. On the DP, open IIS Manager → server → Sites, select the site serving the DP request, and open Logging to identify its configured log directory.
4. Find the matching request by timestamp and URL. Record:
   • HTTP status and substatus
   • Win32 status
   • Requested path
   • IIS site and application pool

If all packages fail, compare the affected DP with the working DP and capture differences in the DP site’s bindings, authentication settings, virtual directories, application-pool state, and the IIS/Windows event logs. Do not copy settings blindly; the IIS substatus and event details should identify which component requires correction.

4. Trace content installation on the DP

For the affected package/content ID:

1. Review DistMgr.log on the site server and confirm that a PkgXferMgr job was created.
2. Review PkgXferMgr.log to determine whether transfer to this DP completed.
3. Review SMSDPProv.log on the DP to confirm that the content was added to its content library.
4. For a pull DP, also inspect PullDP.log and its local DataTransferService.log.^7^

If content validation and distribution both succeed but IIS continues returning 500 for all content, repair the identified IIS/DP configuration problem. Consider removing and reinstalling the DP role only after preserving the relevant logs and confirming that the failure is role-wide rather than limited to particular packages.

---

References

1. Manage distribution points - Configuration Manager | Microsoft Learn
2. Monitor content you distribute with Configuration Manager
3. Content Library Explorer
4. The content library in Configuration Manager
5. Log file reference - Configuration Manager | Microsoft Learn
6. Application download in Configuration Manager
7. Troubleshoot Content Distribution issues - Configuration Manager ...