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

Phil Hartree 11 Reputation points

2021-06-11T16:25:31.693+00:00

MS have confirmed to me via their incident manager that it's a bug and PG are working on it.
Please sign in to rate this answer.

2 people found this answer helpful.
Phil Hartree 11 Reputation points

2021-06-14T15:01:11.927+00:00

As of 16:00 BST 14/06/21 - No updates from MS other than "We are working on it"

Phil Hartree 11 Reputation points

2021-06-16T11:22:09.133+00:00

As of 12:00 BST 16/6/21 - Nothing more from Microsoft other than "We are working on a hotfix and we don't have an ETA"

Matt 16 Reputation points

2021-06-16T11:24:01.197+00:00

lol. This a failure on a massive level.

Phil Hartree 11 Reputation points

2021-06-17T09:22:05.653+00:00

Update 10:20 BST 17/6/21

As of 18:45 BST 16/6/21 (yesterday) a few devices were successfully downloading the stream.x86.x-none.dat file from the CDN. And when I say a few, I'm talking less than 60 out of a deployment to 1300. And we have ten of these types of deployments. Some are also getting their updates from DPs.

That said, the majority are still failing to get this file from the CDN, even as recently as 10:16 BST
Sign in to comment
Alistair Carr 6 Reputation points

2021-06-15T07:18:43.01+00:00

For anyone checking, still ongoing issue as of 08:00 BST 15th June
Please sign in to rate this answer.

1 person found this answer helpful.
Stefan Maas 1 Reputation point

2021-06-15T08:14:52.5+00:00

Thank you for the update :)
Sign in to comment
Amandayou-MSFT 11,046 Reputation points

2021-06-07T06:48:05.953+00:00

Hi @Stewart Pollock ，

Please use Windows PowerShell cmdlets to create and manage file download and upload transfer jobs to check if it could download successfully.

Start-BitsTransfer -Source http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114/office/data/16.0.13127.21624/stream.x86.x-none.dat -Destination C:\ProgramData\Microsoft\ClickToRun\ProductReleases\2623A9B5-35EF-40AF-B907-841C96135B74\467D1B81-6125-426E-BB95-FDC7EF920714.stream.x86.x-none.1396372.dat

Here is the reference article about Managed Reference for BITS PowerShell Commands:
https://learn.microsoft.com/en-us/windows/win32/bits/bits-powershell-commands

Besides, please check if there is proxy or firewall between client and CDN.

If the response is helpful, please click "Accept Answer" and upvote it.
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.
Please sign in to rate this answer.
Stewart Pollock 11 Reputation points

2021-06-08T14:10:58.39+00:00

Hi Amanda

Thanks for your reply. I'd already tested doing the BITS download via PowerShell to a temp folder which worked fine. I've just tried it again writing to the ClickToRun folder ConfigMgr is trying to write to as per the log and this also works fine.

There's no proxy involved, I'm using a direct internet connection and I've disabled the local firewall to rule that out. I've just tested with build 16.0.13127.21668 that was released today and still the same issue.

Thanks

Amandayou-MSFT 11,046 Reputation points

2021-06-09T09:26:45.173+00:00

Hi,

I totally understand your concern. And we're very sorry for any inconvenience that may caused.
And I find some people have similar problems, here is the related link:
https://learn.microsoft.com/en-us/answers/questions/427030/sccm-mecm-office-365-updates-not-downloaded-bits-j.html

We will also report this issue and hopefully receive an answer as soon as possible.
If your case is quite urgent, we recommend you open a case in Microsoft CSS support.
https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

Best regards,
Amanda

Robert Ebbrecht 6 Reputation points

2021-06-09T15:45:40.04+00:00

Hi Amandayou,

we have the exact same issue.

Start-BitsTransfer -Source http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114/office/data/16.0.13127.21668/stream.x86.x-none.dat -Destination C:\WINDOWS\ccmcache\3d.CA43.dlt\Office\Data\16.0.13127.21668\stream.x86.x-none.dat

Works perfect, but when the BITS job is launched from Configuration Manager client it fails with ERROR CODE: 0x8020002b - The specified byte range is invalid. The byte range must exist within the specified remote file. No proxies involved:

PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE: http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114/office/data/16.0.13127.21668/stream.x86.x-none.dat -> C:\WINDOWS\ccmcache\3d.CA43.dlt\Office\Data\16.0.13127.21668\stream.x86.x-none.dat
ERROR CODE: 0x8020002b - The specified byte range is invalid. The byte range must exist within the specified remote file.

Amandayou-MSFT 11,046 Reputation points

2021-06-10T09:12:51.417+00:00

Hi,

We could try to install the older version of MS 365 Apps for Enterprise, if it is successful, It maybe a problem with the backup of this file on the CDN/ Internet. In this case, it is suggested to contact Microsoft CSS support to see if they have some comments about this, as they may have more resources.

To obtain the phone numbers for specific technology request please take a look at the web site listed below:
https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

Thanks for your understanding!

Best regards,
Amanda

Marcel Moerings 6 Reputation points

2021-06-10T09:16:31.837+00:00

We are also having lots of issues with the latest Office for Microsoft 365 updates from the cloud. All updates downloaded from a CDN fail but when we offer them from our local DP the clients can install the updates without any issue. I was hoping the latest updates from this month would solve it, but that's only partially. In SCCM the clients have two updates that are required. One install, One fails.

The one that fails is the update for channel 2104.

It's also puzzling as to why the clients have two updates marked as required when we use only one channel (Monthly Enterprise Channel). I would think only the latest update for this version would be required but instead we get two required versions.

So, any update on this issue which seems quite widespread in the meantime?
Sign in to comment
MelQ 11 Reputation points

2021-06-11T05:19:00.84+00:00

We are also having this issue with 16.0.13127.21668 with 5 out of 5 test computers. DataTransferService.log shows:

DTS job {2CD47322-418E-4348-B8DC-F5BE04DF82C9} BITS job {E9943C7B-7C77-4347-AEA1-4E798794B4AF} failed to download source file http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114/office/data/16.0.13127.21668/stream.x64.x-none.dat to destination C:\ProgramData\Microsoft\ClickToRun\ProductReleases\8D6672D6-8C01-4BF7-A564-23002EF9C8B0\9CA65069-20A0-40CB-8A6E-7C16E16F7DC4.stream.x64.x-none.1541017.dat with error 0x8020002B

When I plug http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114/office/data/16.0.13127.21668/stream.x64.x-none.dat into a browser, the file downloads.

We have CMG setup and this happens when the computers are on Internet. For 1 of them of the 5, I connected to it to VPN. I restarted the SMS Agent Host service after connecting to VPN because it still seemed stuck, but it downloaded and installed shortly after that while on VPN. Other test computers have been able to install fine when onsite or VPN.

I didn't notice issues on my test computers last month (May). We did have some users stuck later at 50% though that eventually resolved after restarting onsite.

I will create a case with Microsoft tomorrow if the issue still shows in the morning and report back here on what I find out.
Please sign in to rate this answer.
Alistair Carr 6 Reputation points

2021-06-11T15:40:39.197+00:00

I would be very grateful (as would many others i suspect) to hear your feedback.

Thank you in advance.

MelQ 11 Reputation points

2021-06-11T15:59:53.82+00:00

Hopefully, Microsoft is already aware. There is also a thread on Reddit with others reporting the same issue. I just put in a report request in case it is not known yet and I put a link to this page so they can see what others are experiencing also. I'll let you know what I find out.

MelQ 11 Reputation points

2021-06-11T16:06:56.157+00:00

Here's people on Reddit having what sounds like the same issue:
https://www.reddit.com/r/SCCM/comments/nxcizu/office_monthly_enterprise_from_officecdn_failing/

MelQ 11 Reputation points

2021-06-11T16:41:49.277+00:00

Meant to say a Help Support Request. The details I sent in match what they have from others (maybe @HartreePhil-0634) and they are looking into.
Sign in to comment
Alistair Carr 6 Reputation points

2021-06-14T07:12:35.337+00:00

As of 08:00 14th June (BST) the issue appears to be still ongoing, has anyone heard anything further from MS ?
Please sign in to rate this answer.
MelQ 11 Reputation points

2021-06-14T14:58:59.043+00:00

Still looking into is the update I was just sent from my case.

Alistair Carr 6 Reputation points

2021-06-14T15:09:14.397+00:00

Thank you very much for the update
Sign in to comment