11-25-2016 02:49 PM
11-25-2016 02:49 PM
I have tried uploading files to Teams using Chrome, Edge and the Teams Desktop App.
Nothing seems to allow a file to be uploaded. Is anyone else seeing this?
Here is a video of the situation. It's pretty self-explanatory.
As I noted in the video ... I am working hard to keep my team interested in Teams, but it's not easy when simple funcationality like this is broken.
Anyone got any ideas on how to fix this?
11-26-2016 01:36 AM
11-26-2016 05:48 AMSolution
I had the same problem and raised it with MS. There was a bug and they have fixed it. It will roll out in production/preview in due course I've been told, not sure when. What was happening for me was the file would get uploaded to the default document library and not the one selected in the tab.
11-26-2016 08:54 AM
UH-OH --- There seems to be a bug. It happens, but it's odd that a MSFT filetype is not working.
I can upload some files, but not OneNote files. It seems there is a problem uploading ".one" files.
After a reboot I tried to upload the same file. And, got the same error. So, I randomly tried another file ... and it worked. I also uploaded one of the other files (a .PPT) that I wanted to put onto the Team site.
So, although the problem is not solved at least we know OneNote files are persona non-grata on Teams.
11-26-2016 11:49 PM
11-30-2016 03:08 PM
Got an update yesterday that is has been fixed in the Win10 desktop version of Teams. I can now upload docs to the correct place in SharePoint!
04-23-2020 09:54 PM
This reply is a bit late, but here it is 2020 and I still am encountering issues with uploading files into Team conversations. I found that if I used Team on Windows 64, I couldn't upload files and I couldn't connect Teams to One Drive. Tried uploading from a network drive, my local C drive and from One Drive - all failed with the message "the image did not upload. Please check if the site is available."
I found the solution was to try the same upload with Teams for Android using my phone. The image uploaded in about 10 seconds using this alternative method. Seems that there must just be a bug in the Windows version of the app.
07-10-2020 06:51 AM
07-10-2020 06:55 AM
07-27-2020 07:56 AM
@davedallasnc @David_Ree I'm having the same issue and I have 64-bit as well. I tried to call their support, but for some reason there is only this Indian guy who doesn't have technical knowledge and only guides you to the site where you can search support or create a ticket. What a waste of time that was. And apparently Microsoft Incident solving costs 499 $. I can't believe they don't fix it for free.
09-09-2020 02:25 PM