This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When someone else in our OneDrive has downloaded files in the past, I used to be able to click on those same files and they would open without issue. Now, I get the above error code and have to continue to hit "try again." Does anyone have any idea as to why all of the sudden I'm having this problem? Thank you.
A Microsoft file hosting and synchronization service.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I can also confirm this fix works. Strangely though - microsoft support passed this fix along to me without giving any props to Justin lol.
Haha nice! Glad to hear my fix is circling around.
I have come to the same conclusions as you have but to add to the list of fixes,
I have found that if you sync the library with OneDrive, instruct OneDrive to always keep the items on your device (obviously can trigger a large download) this also fixes the files in question. You can then safely use the "Free up Space" to remove them from your local drive. I looped through our previously migrated sites with this method and it fixed all of those libraries.
We also have confirmed it happens on files migrated from SharePoint 2013 on Premise using ShareGate that also have the issue.
I have come to the same conclusions as you have but to add to the list of fixes,
I have found that if you sync the library with OneDrive, instruct OneDrive to always keep the items on your device (obviously can trigger a large download) this also fixes the files in question. You can then safely use the "Free up Space" to remove them from your local drive. I looped through our previously migrated sites with this method and it fixed all of those libraries.
We also have confirmed it happens on files migrated from SharePoint 2013 on Premise using ShareGate that also have the issue.
Hello Jason,
The only problem is this will only fix the files on the local computer (at least it did for me). It doesn't actually upload the fixed file when you press 'Free up space'. I'm not sure why it continues to work locally but I am guessing there is a cached file somewhere. Curious if it was different for you.
-Justin
When your organization has added a half terabyte library to SharePoint, and all user computers have 128GB SSDs as their storage, this "solution" is impractical at best. I notice the issue has gone now, sometime in the last three weeks. At last I can switch off the old server!