10-08-2020 11:57 PM
10-08-2020 11:57 PM
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:
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:
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
10-09-2020 12:23 AM
10-09-2020 12:39 AM - edited 10-09-2020 12:49 AM
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.
10-09-2020 12:51 AM
@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.
10-09-2020 12:55 AM
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.
10-11-2020 11:53 PM
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.
10-12-2020 05:15 AM
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?
10-12-2020 05:28 AM - edited 10-12-2020 05:42 AM
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.
10-12-2020 05:53 AM
@alexrademeyer I just opened a ticket with Microsoft this morning also. Will keep you posted if I get any resolution. Thanks for the update.
10-12-2020 11:37 PM
@pblbsyl any update on your support ticket?
I had an update on mine but it is not helpful (surprise!) :)
on my side, I asked for some kind of post where customers can check the status of the bug (like we get in Service Health for example) and the support agent confirmed that Microsoft keeps bugs "confidential" and do not share updates with customers. So he closed the ticket.
Truly awful work by MS Support, as expected:
I hope you make better progress on your side.
10-13-2020 07:44 AM
@alexrademeyer : Just finished with my first support call. No resolution so far, but he is escalating to the SharePoint team next.
For our configuration, the Teams upload is failing if the document library tab connects to a SharePoint document library that contains document sets with a default content type. From within Teams:
If I add a document library tab in Teams to just a simple document library in SharePoint with no document sets, etc., then the upload is fine.
If your configuration and issue similar?
10-13-2020 10:13 AM
hi, thanks for keeping this issue updated, and for your information.
I also got my issue escalated today- it is escalated to the "product group"- unclear which product though. I await their reply.
Interesting note about document sets... thanks for confirming.
On this side however i have reproduced the issue on a site where the "document set" content type is not even enabled.
To answer clearly: I have this issue on document libraries which do not use document sets.
as a quick test i just did the following, which might be interesting for you to hear:
i created a brand new document library (no customisations, no document sets, and no documents. brand new).
This was created on the same site where other affected libraries are hosted.
I added this new library to a team using the "document library" app.
Tried to upload a file here and got the same error.
Not sure what this tells me, but i think it is interesting to see the error on a brand new, empty library.
hope we get the answer soon.
10-13-2020 10:45 AM
@alexrademeyer I just ran across documentation of a method that does seem to work for me.
Let me know if that works for you also? In my setup it is fine to ask the users to add this way as opposed to the Document Library tab. So this may be a solution for us. Would like to know if you also get good results. Thanks!
10-13-2020 11:51 PM
Thanks! I tested this and it is a good workaround.
Very nice, thank you for the suggestion.
I can announce this to my users but can't be sure they will all see it and/or stop using the "document library" app (which is still broken).
But i think this is a good workaround or temporary solution- nice thinking and thank you!
10-14-2020 04:05 AM
@alexrademeyer You are very welcome! I am still waiting to hear back from my users, so thank you for letting me know this worked for you.
Since my ticket has not been closed with Microsoft I will continue to pursue to see if they can figure out the issue. Will let you know if they do.
10-29-2020 05:29 AM
I continued to work with Microsoft, and yesterday I was able to upload to the Document Library tab with no errors.
Curious if this also works for you now? I know it doesn't fix the corrupted files that are in place, but would be interested to see if new file uploads work now.
10-29-2020 09:55 AM
Hi, thanks for reaching out.
Interestingly, Microsoft reached out to me today and asked me to reproduce the issue again.
I tried but I can't - seems solved for me too!
I will test some more tomorrow but I suspect this is solved- thanks for sticking with this over the weeks!
10-30-2020 03:45 AM - edited 10-30-2020 03:47 AMSolution
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.