ERROR code: 0x80070185

Hello All.  I had the same issue.  After a few days of troubleshooting I developed a fix.  You essentially need to open each file in the cloud and get people to restart their OneDrive client.  Opening the file triggers the repair. Below is my findings.  I included a fix at the bottom.

**Effected Files:**Only Office files that were migrated from network drives using the SharePoint migration tool (likely ''SharePoint Migration Tool Public Preview).  Confirmed it affects old legacy office files (.doc, .xls, etc...) and new (docx., xlsx, etc...).  Does not happen with PDFs.  I can consistently reproduce the problem on multiple sites and with multiple computers/users but only on files migrated using the tool.

Troubleshooting:

-Most of the time pressing retry 1-3 times works.  The file then open successfully even if it's loaded back to the cloud and re-downloaded.  Noticed the file sometimes gets ~2kb's bigger as soon as you open it for the first time (right after file is downloaded before it opens in Office).  Opening it a second time only fixes it for the local computer.  The file is fixed on all computers as soon as it is modified and uploaded back to the cloud.

• Confirmed it was not anti-virus.  Uninstalled Vipre and issue still happened.  I have noticed that Vipre crashes sometimes after the OneDrive error message.  Replicated issue on two computers.  Uninstalling Vipre does not fix OneDrive error.  Confirm Vipre crashing is a separate known issue (VPBAGENT-3652 - Microsoft OneDrive users could encounter a VIPRE service crash when attempting to access OneDrive documents. link)
• Confirm issue still occurs on other wifi networks.  Confirmed it happens on wired and wireless connection.
• Confirmed it happens with small and large files (22 KB - 25+ MB).
• Confirmed issue is happening on latest OneDrive version 19.070.0410.0005. 
• Confirmed issue happens on sites where all the default library settings are kept (no special columns or metadata).

- Started re-index of document library.  Checked 24+ hours later and confirmed issue is still occurring.  

- Confirmed previewing the file in SharePoint Online does not trigger the file size increase/fix it.  

The following steps appear to fix the problem on an individual file/folder:

• Opening the file AND modifying it (desktop or Online).  Problem is it updates the last modified date/author as well so solution is not feasible.
• Modifying any file properties/column on SharePoint Online.  Problem is it updates the last modified date/author as well.
• Moving the folder to a different library and moving it back appears to resolve the issue.  Moving also triggers the file size increase.  Only problem is it is very time intensive.

Here is what I did to fix the problem on our sites without having to move any files:

1. Open the document library in Internet Explorer.  Use the ‘View in File Explorer’ feature.  Map the site library as a network drive.
2. Use PowerShell to loop through all documents in the library and read the first line (see below).  This triggers the file repair in the cloud.
3. Have people reboot their computers or restart OneDrive sync client.

Get-ChildItem -Path 'INSERT MAPPED DRIVE HERE' -Include "*.xls*","*.doc*","*.ppt*" -Recurse | ForEach-Object {

    $_.FullName

    Get-Content -Path $_.FullName -first 1 | Out-Null

}

End result is people no longer get the error message and I didn’t need to move the files.  It also maintains all file properties since I am just reading the file.  Also has no impact on users who have documents open so it can be run during office hours.

If you have files that are over 50 mb you may need to modify your registry so the WebClient service can open them.  Otherwise you will get an 'The file size exceeds the limit allowed and cannot be saved.' message in powershell. https://www.thewindowsclub.com/file-size-exceeds-limit-allowed-cannot-saved

You might be on to something though, gonna test out some theories about migrations.  I have a library that has the issue and if I create a new file in that library using the New Dropdown from the browser, that new file will open fine from the sync'd OneDrive library.  I can copy a file via drag drop from a shared network drive to the library via browser and that file also opens fine when opened from the sync'd OneDrive folder.

I am curious if anyone sees this error in libraries that were not migrated and do not contain any migrated files.

Right now, it seems as though most people are only seeing this in libraries that were migrated.

By PC I meant in general terms the computer, we have no Macs so can't speak to that.  Some of the libraries that have the problem have been migrated using a tool called File Facets.  However other libraries that have also been migrated using this tool are fine.  It doesnt seem to be related to a specific library however, I have the issue with Library A and other users have no problems with Library A.  They have an issue with Library B and I have no issues with Library B.  Unless it is even intermittent between libraries I havent been able to determine that.

It is also happening to Mac users, so it isn't just relegated to PCs.

The intermittent nature of this error makes it difficult to pinpoint the actual cause.

In our case, all of the affected libraries contain files that were migrated to SharePoint from a file share.

Do your affected libraries contain folders/files that were migrated to SharePoint from somewhere else?