ConfigMgr Downloads from CDN failing for MS 365 Apps for Enterprise

Stewart Pollock 11

We've run into a problem this month deploying updates for Microsoft 365 Office Apps using ConfigMgr 2002. These have been working fine as recently as a couple of weeks ago as we deployed Semi-annual build 13127.21624 to a pilot group successfully. The same update now fails on all devices when downloading direct from CDN. The same download works perfectly if we make the content available from a ConfigMgr distribution point.

DataTransferService.log contains the error:

DTS job {A748857A-BA09-4591-B399-E0B09B580F45} BITS job {5375518E-6E52-420D-9571-47F655D01C29} failed to download source file http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114/office/data/16.0.13127.21624/stream.x86.x-none.dat to destination C:\ProgramData\Microsoft\ClickToRun\ProductReleases\2623A9B5-35EF-40AF-B907-841C96135B74\467D1B81-6125-426E-BB95-FDC7EF920714.stream.x86.x-none.1396372.dat with error 0x8020002B

I googled the BITS error which is: BG_E_INVALID_RANGE (0x8020002B) The specified byte range is invalid. The byte range must exist within the specified remote file.

I've tried reverting the Office build to an older version and updating to the penultimate build which also fails now so CDN downloads just appear to be broken outright rather than for any specific Office build. If I put the download URL into a web browser it works fine, the download only fails when instigated by ConfigMgr.

At a complete loss as to what may have changed to be causing this issue. Any help greatly appreciated.

Target devices are Win 10 1909 18363.1556

Thanks

JWT 1 Reputation point

2021-06-10T13:59:58.197+00:00

Same exact issue here trying to install 13127.21668. Installs fine from on premise configuration manager distribution point, but fails when downloading from CDN. Hangs at 50% and gets a 0x800775f1 error.
Phil Hartree 11 Reputation points

2021-06-11T11:15:01.12+00:00

We have been expeiencing the exact same issue for the last 5-6 days.

Devices obtaining content from DPs are working fine (even when the DPs are located in Azure) but devices obtaining their content from the Microsoft CDN fail.

Devices fail with the same file DataTransferService log entries: same file: stream.x86.x-none.dat and the same error code 0x8020002B

Other files as part of the same update pacakge are present on the client device - so it's not a routing / network config issue.

It appears only to be that single file (although I have reports of possibly one other file missing)

We are deploying SEAC 2008.May and we have the same issue with few test devices with 2008.June. Some May and June updates are slowly getting through, but unable to understand why. Maybe some round robin / network balancing stuff at the MS end?
JWT 1 Reputation point

2021-06-15T01:06:48.6+00:00

I just tried the download/install at around 7:30pm CDT. It seemed to take an abnormal amount of time, but eventually downloaded and installed over CDN. Seems to be resolved. Can anyone else confirm?
MelQ 11 Reputation points

2021-06-15T02:08:22.103+00:00

I'm still having the issue.
messindj 1 Reputation point

2021-06-15T17:36:57.923+00:00

Seeing the same issue with the Preview update - DTS job {E26B0FE3-5079-4C22-B078-BF6E7BD06A35} BITS job {C0A46536-139D-4A9E-900A-5239B6C3D355} failed to download source file http://officecdn.microsoft.com/pr/b8f9b850-328d-4355-9145-c59439a0c4cf/office/data/16.0.13801.20738/stream.x64.x-none.dat to destination C:\WINDOWS\ccmcache\19.E26B.dlt\Office\Data\16.0.13801.20738\stream.x64.x-none.dat with error 0x8020002B Has anyone seen this as well?
Samuel Valaparla 6 Reputation points

2021-06-16T05:44:26.27+00:00

Does anyone have some detail on the bug itself, apart from the fact that this is a known issue and being worked upon? There are some sporadic instances where the failing download eventually goes ahead and succeeds, but this isn't the case with a majority of users. Trying to seek some detail around this from MS, but have only been told that this is a Priority 1 BUG, and the workaround is to deploy the update from a Distribution Point, which doesn't help at all considering 90% of the devices are working remotely.
David Moon 541 Reputation points

2021-06-17T02:34:53.43+00:00

I am in the same boat. Same error.. same file. However i am having the same problem whether the download is happening from the local sccm DP or CDN.
These are semi annual updates from June. But having same problems with the latest Monthly enterprise update as well. If you keep trying over and over... eventually it succeeds.
TBA 1 Reputation point

2021-06-17T04:52:13.11+00:00

We are seeing the same issue with Config Mgr, we had this last month with around 20-30% failures. Eventually, they all seemed to get it, dont know whether it was down to machines rebooting from the Windows 10 update, some of our support guys seemed to think the update wasnt downloading if Office was open, but cant confirm that. As our company are working remotely we are relying on getting the updates direct from MS so it doesn't incur costs from our Cloud Management Gateway, or create traffic over our VPN. Im now seeing the June update have the same failures with our Pilot group. Any updates from MS?
SethB 1 Reputation point

2022-03-03T05:50:28.373+00:00

Had to delete the contents of my %temp% folder located on the site server, then remove all products and classifications from the SUP configuration, do an update sync, then reenable pertinent classifications and products and then sync again for this to finally start working again.

19 answers

Alistair Carr 6 Reputation points

2021-06-22T07:40:18.367+00:00

Some further information, 'new' updates are downloading are downloading correctly. So, all i did (sorry if this is teaching to suck eggs)

Searched for and added required new 365 updates to SUG
Removed 'old' superseded expired updates from SUG
Deployed
Worked !!!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Phil Hartree 1 Reputation point

2021-06-22T08:25:07.167+00:00

Similar here: 09:00BST 22/6/21

MS engineer has updated earlier this morning to say the issue is resolved - but no detail around what the issue was nor how it was resolved.

Our compliance has gone up from ~25% to 40-45% overnight, so updates appear to be succeeding.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Kevin Winegardner 1 Reputation point

2021-06-23T18:25:17.507+00:00

Updates starting downloading as of this morning.
Please sign in to rate this answer.
Krthk 1 Reputation point

2021-06-24T14:48:28.337+00:00

Initially we get BITS Job error 0x8020002B and now we get BITS Job error 0x80190194. This happens for both type of updates looking for CDN or DP. Luckily, the error count is getting reduced slowly for both types of updates.
Sign in to comment
Simon Dettling 1 Reputation point

2021-07-20T08:41:52.807+00:00
Same BITS error 0x80190194 while deploying "Microsoft 365 Apps Update - Semi-Annual Enterprise Channel Feature Update for x86 based Edition Version 2102 (Build 13801.20808)" for Remote Clients that pull the Content from CDN. Internal Clients that get their Content from a DP are working without any issues.

DTS job {...} BITS job {...} failed to download source file http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114/office/data/16.0.13801.20808/stream.x86.x-none.dat to destination C:\WINDOWS\ccmcache\2cc.0CFC.dlt\Office\Data\16.0.13801.20808\stream.x86.x-none.dat with error 0x80190194

Looks like this still isn't solved...

If someone likes to share Case Numbers, you can find me me on Twitter (@Simon Dettling ).
Please sign in to rate this answer.
MelQ 11 Reputation points

2021-07-21T00:02:06.887+00:00

We are also seeing BITS error 0x80190194 in DataTransferService.log for the July "Microsoft 365 Apps Update - Semi-Annual Enterprise Channel Feature Update for x86 based Edition Version 2102 (Build 13801.20808)" update on remote clients that pull from CDN. Some remote clients are getting through though eventually after a restart, but a restart does not always resolve.

We were seeing a different BITS error (0x8020002B) with the June updates, created a case with Microsoft, and June O365 update downloads started working for us after Microsoft indicated the issue was resolved.

We've created a new case with Microsoft for our July issues. Our support engineer indicated he is not finding other cases submitted other than Simon's. The issue is being investigated for our environment, but if anyone else is having this error and can create a case with Microsoft, I would encourage you to do so they know the scope of the issue. Otherwise, maybe the problem is only just a few of us with certain configurations or if we are hitting certain servers?

Alan DoeGrise 1 Reputation point

2021-12-06T08:29:10.087+00:00

Do you have any update from your opened ticket on Microsoft support ?
Same issue here

MelQ 11 Reputation points

2021-12-06T16:43:23.597+00:00

Microsoft resolved the issue for us about a week after the post. There was something affecting certain tenants. I believe things resolved for Simon at the same time. I don't know the ultimate cause. Similar issues with O365 updates do seem to crop up every once in a while and hit just certain tenants at a time. We had similar issues in June. I haven't seen issues in our environment since this July issue though. Both our issues were definitely something that had to be resolved on Microsoft's end.
Sign in to comment