Forum Discussion
Files on Demand - The Cloud sync engine failed to validate the download - Error 0x8007017F
I'm seeing the same as PhilineVon at a client site. Lots of 0x80070185 errors ("The cloud operation was unsuccessful"). It seems to be affecting certain users more than others within the same library?
The document libraries at this client's site are very large - 199k files in the main one. I'm wondering if that's just too many files for the sync agent to handle? The official documentation states that OneDrive for Business can reliably sync up to 300,000 files, but it's the only thing I can think of?
I just wanted to throw my hat in the ring here too in case anyone finds a solution.
Cheers,
Matt
Matt_Ignite take a look here for a couple of suggested solutions:
I still think the easiest solution for individual users is to set all files to "Keep offline" then push them all back to the cloud "Free up space", but Justin Kropp's solution may be a better way to clear up the issue for multiple users.
- Matt_IgniteJul 10, 2019Copper Contributor
kevinmckeown8 - many thanks again for your recommendation here.
Early last week I ran Justin's powershell scripts against all the document libraries for the customer, and reset the OneDrive cache on the worst-affected user's PCs. In the week since, the users have reported absolutely no re-occurrences of this error. Originally, we were hitting the error on EVERY Excel document that we opened from the synced library. This is a BIG change. So I'm calling that a success.
I'm planning on calling into the client site later this week to confirm with the team in person, but for now I'm pretty confident.
Thanks very much for pointing me in the right direction. I really appreciate the assist!
Cheers,
Matt
- Matt_IgniteJul 01, 2019Copper Contributor
kevinmckeown8 - thanks very much for this! Apologies for the late reply, for some reason I never received a notification that you'd tagged me here.
That thread is gold. The scenario JustinKropp outlined is the exact situation I've been struggling with now for months - a large Sharepoint library that was migrated from a network share with the Sharepoint Migration Tool. All Office docs are affected, but nothing else. My ego has taken a bit of a hit given that he solved the problem with "a few days of troubleshooting" and I've been running this case with MSFT now for ~4 months, but hey - if it works I'll be a happy man.
I'm currently running the powershell script across the entire library, since there's a lot of files and a number of PCs. Plus, the PC's don't have sufficient space on their local SSD's to sync down the entire library :D .
I'll let you know how I get on. Thanks again for the links - much appreciated.
Cheers,
Matt
- PhilineVonMay 31, 2019Iron Contributor
Hi Kevin, the keep on device - free up space trick seems to fix the issue. Thanks.
Currently trialing this with a user to see if this is actually a long term fix. Will report back if not.Update on this - the fix as described by kevinmckeown8 above seems to have done the trick.
Thanks so much for sharing