Forum Discussion
Document Library tab: Cannot upload or drag&drop files (Bug)
- Oct 30, 2020
pblbsyl
I finally have a useful update from Microsoft.This should likely close the issue off:
Microsoft acknowledge the bug and that their product team are rolling out a solution which should be out in the next few weeks:Unfortunately this does not actually fix the damage done......
This bug corrupts customer data yet Microsoft have not acknowledged it in the message center or service updates.
Further: They have confirmed to me it is not possible to identify or restore the corrupt files- they will be lost.I see this as "solved" in some way although i have lost a little more faith in Microsoft today- to me this is a business practice which does not encourage our trust. these kinds of bugs should be communicated.
Alex
- alexrademeyerOct 09, 2020Brass Contributor
hi, thanks for being engaged.
I just tested again.
Today the error in the Teams client is gone.However, the files that i uploaded are still corrupt (and this is the main issue).
If you check 1 of the files you uploaded via teams client, can you see the content?
For me, they all look like this:
Also, please make sure that the "document library" tab you added is to a sharepoint site (preferrably NOT the same site created by the team automatically.) i will say this: This bug does not exist on some libraries i tested, but for most of them, it does... if you could, can you please try libraries from a few different site collections? Honestly i can't identify which libraries are/are not affected but from what i have seen, most libraries are affected.
Oh! and to answer your question:
no, i am not using a proxy.
2 colleagues (both working from home) reproduced this yesterday, and so did a microsoft support agent, so i really dont think it is related to tenant, user, computer, network. 
- TheM365GuyOct 09, 2020Brass Contributor
alexrademeyer I did it like described. No issues, I can upload the files. I can access the files. Also I checked this now with 3 different document libraries. One with a team created library, two with some complete different SharePoint libraries, I can not reproduce this issue.
Our tenant is based in EMEA, just as information.
- alexrademeyerOct 09, 2020Brass Contributor
TheM365Guy
ok, thank you for taking the time to troubleshoot 🙂
I have tested in our Live tenant, my dev tenant, and also a microsoft support agent (in Asia somewhere) tested in his tenant- all 3 were affected.
Interesting to hear that yours are not.... this might help us get closer to an answer.
Thanks again.