question

StewartPollock-0389 avatar image
0 Votes"
StewartPollock-0389 asked SethB-5909 commented

ConfigMgr Downloads from CDN failing for MS 365 Apps for Enterprise

Hi

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

mem-cm-updates
· 9
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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.

1 Vote 1 ·

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.

0 Votes 0 ·

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?


0 Votes 0 ·

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?

0 Votes 0 ·

I'm still having the issue.

0 Votes 0 ·

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?

0 Votes 0 ·
Show more comments
DavidMoon-1992 avatar image
0 Votes"
DavidMoon-1992 answered

Is there an official microsoft KB link with their response for this issue? Or are you all getting the information about Microsoft working on this, via Premier support?
Thanks.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PhilHartree avatar image
0 Votes"
PhilHartree answered AlistairCarr-4229 commented

Update 10:30 BST 18/6/21

Just has this from the incident manager (as a screenshot)

106950-capture.jpg



capture.jpg (48.9 KiB)
capture.jpg (48.9 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@PhilHartree Thanks for the update. Hopefully sorted soon..

0 Votes 0 ·
AlistairCarr-4229 avatar image
0 Votes"
AlistairCarr-4229 answered PhilHartree-7824 commented

@PhilHartree Good morning, I don't suppose you've had any further updates?

Thank you in advance !

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi
Nothing at all from MS I'm afraid.

Compliance has increased to ~25% over the weekend and failures are sitting at ~30% (where they were more like 60%)

We are still seeing failures as of 11:00BST, although the error code seems to have changed on a couple that I've just looked at:

DTS job {A8161561-FDAE-4367-BA81-FEBC44E26548} BITS job {95B21519-0AFA-4484-9CEB-20F7A2E163E4} failed to download source file http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114/office/data/16.0.13127.21668/stream.x86.x-none.dat to destination C:\WINDOWS\ccmcache\9d.A816.dlt\Office\Data\16.0.13127.21668\stream.x86.x-none.dat with error 0x80190194

0 Votes 0 ·
DavidMoon-1992 avatar image
0 Votes"
DavidMoon-1992 answered MelQ-1407 commented

MS Case engineer is telling me that this issue has been resolved in the last few hours.
My machine seems to have gone through.... but then again could have been a fluke. Need to see more results...
Anyone having better luck with CDN downloads now?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Our case manager indicated to us this morning that the issue has been resolved. I had noticed one of my stuck testers had installed the June O365 updates over the weekend. I turned 5 others that have been stuck on this afternoon and 4 out of 5 downloaded and installed the update just after being turned on for awhile. For the one still failing, it originally had failed with a 0x8000000E error and would not complete the download today until I initiated the update from Word and then it finished off. I added another laptop to get the June O365 updates this evening and it fairly quickly downloaded and installed the update. My test sample is small, but I had nothing working over CDN before and all my testers have completed now (with just one of them needing a push from an O365 app instead of just waiting to complete).

1 Vote 1 ·
AlistairCarr-4229 avatar image
0 Votes"
AlistairCarr-4229 answered

Unfortunately in the UK I'm still seeing errors this morning

DTS job {6C422185-2D29-4AB6-94FD-D1CAA3FE81AD} BITS job {6C149D1C-8C4C-4328-A527-81E637B276D7} failed to download source file http://officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60/office/data/16.0.14026.20270/stream.x64.x-none.dat to destination C:\WINDOWS\ccmcache\57.6C42.dlt\Office\Data\16.0.14026.20270\stream.x64.x-none.dat with error 0x80190194

However, As MS released new O365 updates on the 18th I'll attempt to deploy those via CDN and will hopefully have more success

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AlistairCarr-4229 avatar image
0 Votes"
AlistairCarr-4229 answered

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 !!!

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PhilHartree-7824 avatar image
0 Votes"
PhilHartree-7824 answered

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KevinWinegardner-5640 avatar image
0 Votes"
KevinWinegardner-5640 answered Krthk-1004 edited

Updates starting downloading as of this morning.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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.

0 Votes 0 ·
SimonDettling avatar image
0 Votes"
SimonDettling answered MelQ-1407 commented

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 (@SimonDettling).

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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?

1 Vote 1 ·

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

0 Votes 0 ·

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.

0 Votes 0 ·