I recently started getting an error message when I try save a file to the local Dropbox folder. I can save my files to other local locations without a problem. I am using Windows 10 and Office 365. The message that comes up is "An error occured while PowerPoint was saving the file."
When I click "OK", I get a second error message: "We're sorry. Something went wrong that might make PowerPoint unstable. Please save your presentation and restart PowerPoint."
It will look as though it is not allowing me to save, but actually it is saving locally and syncing to Dropbox. When I try to open the file, I get this error: "PowerPoint foound a problem with the content in [file]. PowerPoint can attempt to repair the presentation. I fyou trust the source of this presentation, click Repair."
If I click Repair, I get this: "PowerPoint couldn't read some content in [file]. Repaired and removed it. Please check your presentation to see if the rest of it looks ok."
And it does seem ok. This happens with every PowerPoint file I'm working with, not just this one, but not with other Office applications.
My IT person did a 'quick repair' on my PowerPoint installation, but that didn't fix the problem. I don't seem to be having this problem on my desktop at work which is using an older version of Office, so I suspect it might be related to the connection between Office 365 and Dropbox. Is there any way to fix this? I really don't want to move everything to OneDrive.
We have multiple users who are experiencing the same issue. It only seems to affect pptx documents saved to dropbox. The file is in a shared folder, but no other user has the same document open at the time it is creating the problem.
I have tried:
1) Removing and reinstalling Dropbox
2) Resyncing the Dropbox Cache
Oddly, the same file can be opened on a different PC and it works normally. So this does seem to be a local issue.
Windows 10 (64 bit with latest 2004 patch) running Office 365. All machines are running the same software. One update, after deleting the cache manually and resyncing, it seems to have fixed the issue. I will post again if it keeps happening.