Forum Discussion
Document Library tab: Cannot upload or drag&drop files (Bug)
Hi,
I have been running in circles with support and I am not getting anywhere, i need to raise my concern about a bug in MS Teams which causes your uploaded sharepoint files to be corrupt, and lose all contents.
I have reproduced this in 3 different tenants now, for multiple users and multiple computers, it absolutely is a bug.
The bug exists int he "document library" tab within a team and the repro steps are simple:
- create a new or use an existing team.
- add the "document library" app for any sharepoint library
- in the teams client (web or desktop) drag&drop a file into this library.
- teams gives an error: failed to upload file, "Please check if the site is available....."
- the site is available, of course, you can still upload files into sharepoint directly.
- the file which failed to upload be seen in sharepoint but IS CORRUPT AND CANNOT BE OPENED
I raised this with support but as usual it is not going anywhere. they want to have a 3 hour call collecting HAR files and fiddler logs etc, and want to spend the next few weeks asking me about my laptop- no thanks.
Also raised it in uservoice but I doubt it will get any attention:
https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/41580901-document-library-tab-cannot-upload-or-drag-drop-f
If we as users find a bug (A bad 1... which affects all tenants and causes our files to become corrupt..... for example) HOW can we escalate these effectively? this is hopeless
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
18 Replies
- alexrademeyerBrass Contributor
Microsoft support have confirmed that the product team are aware of this bug:
Unfortunately i still don't see the bug documented anywhere...... service health, message center, here (besides my post) and the result is that customer files are becoming corrupt and customers are losing data.
so, back to my original post:
HOW are we supposed to raise bugs and product issues in an efficient way, how do we get Microsoft to admit and fix such issues.- pblbsylCopper Contributor
We are having the same issue - some document libraries work and others do not. Do you know how we can get status on Case #22216444 since Microsoft is now aware?
- alexrademeyerBrass Contributor
pblbsyl
Thank you for confirming.
Case 22216444 is a case i have open with Microsoft support.
This case is very slow and unhelpful, that is why i raised the issue here in tech community. we need to find a way to escalate this bug to Microsoft and get them to act.
If you are curious, the status of my support ticket is:
support agent claims that Microsoft Product group are aware of this bug but for some reason need me to collect fiddler logs for them..... so i did that and sent them back. waiting for their reply.
- TheM365GuyBrass ContributorHey! I checked this in 2 tenants. I can not reproduce this behavior. Do you using a proxy? Checked with a direct internet connection without any between?
- alexrademeyerBrass 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.- TheM365GuyBrass 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.