MECM DP software installations keep failing - Downloads at 0% - HTTP code 405, status 'Method Not Allowed'

Question

For some reason our clients are not able to download packages from the DP via Software Center, but we can browse to the packages via browser just fine.

Basically our jobs get stuck at 0%, our content has been copied to the DP (verified) and we are added successfully to a boundary group. It seems to be permissions related but we do not know.

We have checked Boundary (Group) assignments in the MECM console (added the Column Boundary Group(s) to The Devices overview). The logs also show this: <BoundaryGroup GroupID="16777218", this seems fine. Boundaries are also assigned by IP range.

What we tried:

1. AV disabled (client) - doesn't help
2. Firewall disabled (client) - doesn't help
3. DP Allows clients to connect annonymously
4. Clients can access the HTTP link directly via the webbrowser, packages are there and can be downloaded without any problems;
   [http://xxxxxx.com:80/SMS_DP_SMSPKG$/Content_9486f285-fedd-4db3-8585-7cf9785cdaea.1]

5. Have created new packages, have redistributed existing packages - did not solve issue
6. Reinstallation of the client does not solve anything
7. Tried disabling eHTTPS with disabling "Use Configuiration Manager-generated certificates for HTTP site systems" but this did not solve the issue
8. Reinstall the DP role

Bitlocker policies get applied without a problem by the client.

We are using default certificates that came with the installation, no custom certs have been created or uploaded.
DataTransferService.log says the following;

UpdateURLWithTransportSettings(): OLD URL - http://MECMSERVER/SMS_DP_SMSPKG$/Content_8fbce89d-a083-4823-b557-d388c638dcb3.1

UpdateURLWithTransportSettings(): NEW URL - http://MECMSERVER:80/SMS_DP_SMSPKG$/Content_8fbce89d-a083-4823-b557-d388c638dcb3.1

DTSJob({FC0E6BAD-034B-404E-8C70-81B94C6D00AC}):CDTSJob::ModifySource - switched to location 'http://MECMSERVER:80/SMS_DP_SMSPKG$/Content_8fbce89d-a083-4823-b557-d388c638dcb3.1'.

[CCMHTTP] ERROR: URL=http://MECMSERVER:80/SMS_DP_SMSPKG$/Content_8fbce89d-a083-4823-b557-d388c638dcb3.1, Port=80, Options=1472, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE

[CCMHTTP] ERROR INFO: StatusCode=405 StatusText=Method Not Allowed

instance of CCM_CcmHttp_Status
{
	ClientID = "GUID:C4EE94B9-5EB7-4C4D-AA9F-9FB4DE55A7C5";
	DateTime = "20230117124355.354000+000";
	HostName = "MECMSERVER";
	HRESULT = "0x87d0027e";
	ProcessID = 17568;
	StatusCode = 405;
	ThreadID = 33112;
};

Successfully queued event on HTTP/HTTPS failure for server 'MECMSERVER'.

GetDirectoryList_HTTP Error sending DAV request. HTTP code 405, status 'Method Not Allowed'

Download timeout has met. DTS job {FC0E6BAD-034B-404E-8C70-81B94C6D00AC} will quit.

GetDirectoryList_HTTP GetDirectoryList_HTTP('http://MECMSERVER:80/SMS_DP_SMSPKG$/Content_8fbce89d-a083-4823-b557-d388c638dcb3.1') failed with code 0x800705b4.

DTSJob({FC0E6BAD-034B-404E-8C70-81B94C6D00AC}):CDTSJob::ProcessManifestCallback - Error retrieving manifest (0x800705b4).

DTSJob({FC0E6BAD-034B-404E-8C70-81B94C6D00AC}): state changing from 'DownloadingManifest' to state 'Suspended'.

Any ideas?

Answer 1

Hi, @PieterSjon

Thanks very much for your posting and feedback in Microsoft Q&A forum. We're glad that the problem is solved now. Here's a short summary for the problem, we believe this will help other users to search for useful information more quickly.

Problem/Symptom:

Clients are not able to download packages from the DP via Software Center, the software installations keep failing - Downloads at 0% - HTTP code 405, status 'Method Not Allowed'.

Solution/Workaround:

It turned out to be WEBDAV. Removed the feature (Webdav publishing in IIS) from the server and it instantly started working.

---

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

This can be closed, in the end (after 3 days of troubleshooting) it turned out to be WEBDAV. Removed the feature (Webdav publishing) from the server and it instantly started working.