This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This is going to be a difficult one for people to replicate I'm sure but I thought it worth asking to see if the behaviour I am seeing is common / typical in SP19....
In our environment we are consistently having calls raised to us because of excel files becoming corrupt which users are working on from SP19 (using client app, not web app). Below screenshot demonstrates that the file becomes corrupt and shows as 0KB:
When users try to open the file they get an error message stating that the file format or file extension not valid. When they try to restore a previous working version even though version history looks like it has restored it, the file still won't load. It looks like the corruption extends to preventing the restore from happening.
At first I thought this was only happening on files where multiple users are trying to edit simultaneously, but today it has happened for a user who is the only person updating this excel file.
And final note, using the "open and repair" option from within excel also does nothing to fix it.
Anyone have any ideas? As I said, this is happening with excel files only. I've not had any reports of similar issues with word or powerpoint and we are dealing with a 2TB+ environment here.
Hi @alchemicdreams
Are there too many files in the library? Will the library with fewer files be better?
Hi,
This is happening in libraries with very few files in them.
Thanks...
![](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(51.2, 42%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
Hello @alchemicdreams ,
Our company recently migrated from SP13 to SP19, and we experience the very same issue.
Did you find a solution for your problem?
Kind Regards, Franz
![](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(265.6, 96%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hi @alchemicdreams . Did you ever find a solution for this? We are experiencing exactly the same situation. Thanks.
Hi,
No we never have found a solution for this and it still happens often enough that it is irritating. We have quite a robust backup and restore process in our organisation so currently I am just resorting to that when the crap hits the fan so to speak.
Cheers,
M
Hi,
No we never have found a solution for this and it still happens often enough that it is irritating. We have quite a robust backup and restore process in our organisation so currently I am just resorting to that when the crap hits the fan so to speak.
Cheers,
M
@alchemicdreams , @BK
Same here :(
It happens only once in a while, so we are going to live with that.
We found out, that you can restore the corrupted file via version history, when do it twice.
So, from your screen shot, restore version 0.327 and immediately after v 0.329 has been created, restore 0.327 again (without opening, reloading or any other action in between)
In our org, this happens only within Citrix Desktops and mainly for users who work with excel excessively (large lists, reports, vba, ...)
Do you have similar experience?
KR, Franz
![](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(304, 70%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJL%3C/text%3E%3C/svg%3E)
Just adding a comment to show that there are still some of us out here affected by this issue.
Thanks for the heads up on restore twice, we have the same problem and it was never resolved. That department of our business has shut down now, so we will not face this issue until it arises elsewhere.
@microsoft Shame there is no fix for this :(
Thanks for the tip about restoring twice. That worked on a document that I wasn't able to restore any other way. Note that this library has checkout required, so I checked out, restored the good version, checked in, checked out, restored the good version, checked in.
Hi @alchemicdreams
As per my research, I couldn't find any effective method on this issue. I would suggest open a ticket with Microsoft to help you to troubleshoot.
If an Answer 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.