question

JonCovalt-6115 avatar image
0 Votes"
JonCovalt-6115 asked AllenLiu-MSFT commented

SCCM: Unable to Install O365 Updates: Error 0x801901F7

When trying to deploy updates to clients with the O365 client on their machines, the Microsoft 365 Apps Updates fail, hanging at 50% downloaded with the full error (I replaced the server name, it was correct):

DTS job {5A3456EC-2EAF-44FB-97B5-39794BD24AA0} BITS job {D7227AB9-661A-416D-8D80-B529A23DE92B} failed to download source file https://<servername>:443/SMS_DP_SMSPKG$/22865c69-46ce-4ab9-9063-1ec66b04b135/sccm?/Office/Data/16.0.13901.20400/s320.cab to destination C:\WINDOWS\ccmcache\p.5A34.dlt\Office\Data\16.0.13901.20400\s320.cab with error 0x801901F7

I can't, for the life of me, find a solution to this particular error code. Anyone out there encountered this before?

mem-cm-updates
· 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.

Here's a new complication to add to this; after about 6 hours of attempting the updates and repeated fails, one of the updates actually succeeded. The DataTransferService log shows the following line right before the patch actually successfully downloaded:

DTSJob {1C1AEFC0-A0BA-4F6F-8E2A-CB89CCB29AB4} switched to location 'https://<servername>:443/NOCERT_SMS_DP_SMSPKG$/1654aef6-5ceb-4813-85b7-ba69fc5d94d2'.

I'm guessing this means there's some sort of certificate-based transfer that's just not working right, but I adopted this SCCM server, and I'm not sure where I'd find that configuration. Any assistance?

0 Votes 0 ·
JonCovalt-6115 avatar image
0 Votes"
JonCovalt-6115 answered AllenLiu-MSFT commented

I think I was finally able to figure this out, and it was IIS related.

On the SMS_DP_SMSPKG$ IIS site, the available protocols had been set to 'http https' (exactly like that, but without the quotes). This was making that sub-site appear to be offline. Once I removed the extraneous https, it appears these updates are working. We'll be doing further testing, but at first glance this seems to have fixed the issue.

· 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.

Thank you very much for the update and we're glad the problem is solved now. If you have any questions in future, we warmly welcome you to post in this forum again.

0 Votes 0 ·
AllenLiu-MSFT avatar image
0 Votes"
AllenLiu-MSFT answered JonCovalt-6115 commented

Hi, @JonCovalt-6115
Thank you for posting in Microsoft Q&A forum.
Please make sure you have selected all the languages you are using for the Office updates.

Here is a link for your reference:
http://redcoat.nl/sccm-office-c2r-update-installation-hangs-on-50/
(Third-party link,just for your reference)


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.


· 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 only have English installed, so I'm fairly confident this is not the issue. Plus, see the comment I added to my original post, as it adds another layer of confusion to the whole thing.

0 Votes 0 ·

0x801901F7 means the service is temporarily overloaded and cannot process the request. Resume the job at a later time.
We may check if the DP IIS logs are good?
And do other updates can deploy to clients successfully?

0 Votes 0 ·

In reverse order:

I can confirm other updates are working; both Windows patches and patches from a 3rd-party software updater (PatchMyPC) function as intended and install successfully from SCCM. It is only the Office 365 Client patches that are failing.

I don't see anything out of the ordinary in the IIS logs that would indicate an issue. I can confirm that the WsusPool is running and there are no memory issues as well, though I get a 503 error if attempting to connect via browser to the directories where the patches are hosted (when connecting normally). The O365 patches return a 404 error if I connect using the NOCERT version of the URL, while functional patches actually show the correct data.

I can also confirm that all patches have the correct files downloaded onto the server, so it's not just that the updates are missing.

0 Votes 0 ·