Sep 04 2020 07:17 AM
Sep 04 2020 07:17 AM
I used Teams at my last job and we had no issues sharing documents that were uploaded into a team as long as the user did their editing after clicking "Open in Desktop App". At my new place, we are having all kinds of issues with saving documents and getting errors about saving. We use SharePoint here where at my old place everything was stored on OneDrive. Some of the errors are related to saving a new copy, which should never have to be done. I've attached an error about the document "...not been uploaded to the server. Do you want to close this file?" It's on AutoSave. Is this just a time lag issue? Help!!
Sep 04 2020 10:31 AM
Hi @RacheleRP ,
OneDrive is technically a SharePoint library and a Teams Team is backed by a SharePoint site but that is a story for another day.
Back to the task at hand. Could you walk me through from start to finish please as I can see the good old upload centre at play here, not seen that in a while. That will be the Orange icon in the system tray. Might be worth seeing that it doesn't have anything holding it up as that can cause issues. (Right click the icon to check) Also what version of Office is being used?
However like you say this doesn't sound like normal practice. So are we talking about editing a file, already stored in a Team/SharePoint and just expecting it to save a new version. Or is this a file that is new and being saved back?
Sorry to ask so many question but if you could walk me through how the file is first opened etc.
Sep 09 2020 04:31 AM
Thank you for touching base so quickly. I hope you had a nice holiday weekend. It seems we had multiple issues. One was that some of our team was linking graphs from a private document to the shared Excel document. It seems Teams doesn't like Excel links to external data. You'd think Microsoft would fix that. Anyway, another issue has to do with the error I attached to my original request for help. We also had team members who would always get an error that told them they had to save a copy. What I don't know is if our team is still having issues. I should have more information late this afternoon as our team has a meeting to go over the shared document every Wednesday.
Sep 09 2020 02:44 PM
Well....about half of the team had no problems. I was able to duplicate one of the issues so I'll describe. The team member opened the shared document and the clicked "Open in Desktop App" as directed. She did her editing (which is really just coping a worksheet into the Master) and then tried to close the document. She got the error below that told her to Discard Changes or Save a Copy. I DONT want the team to save copies, that defeats the whole purpose of using Teams. She emailed a copy of her changes and I tried to copy the sheet and experienced the same error. Rather than save a copy or discard I just hit the "X" and closed the doc. Changes were, of course, not saved. I did the entire exercise a second time, just for kicks and giggles, and low and behold, no error. It doesn't make any darn sense. The team member said she tried a few times with no luck. I'm supposed to talk to another team member that had issues tomorrow morning.
We also had an issue with the "driver" of the meeting, my boss, being able to see all the changes. He opened the document and shared his screen in our Zoom meeting. The changes on one of the sheets weren't there, but when I opened it (at the same time) they were. He closed and reopened and they still weren't there. WHY is Teams being so flaky?
Sep 10 2020 01:41 AM
Hi @RacheleRP ,
It is hard to say and I wouldn't say this is a common place issue as what you are trying to do is basic.
We also have to remember that Teams is the facilitator but really in terms of problem areas we are looking at Office and SharePoint Online.
Out of interest is this issue only seen with this one Excel doc or many others? Also just to ensure it is saved as xlsx and not say xls?
What version of Office do you have? As I am still conscious that I am sure you mentioned something about the upload centre? As you will want to ensure this is in a happy state.
As looking at your screenshot the issue is that the upload that would have saved a new version failed and therefore it presented the option to save a copy as a backup.
For the office version if you click on File with Excel or Word etc. open and click on Account towards the bottom left for me you should see something like:
Also on the same page do you see user information, is the office app signed in as the user that has permissions to the Team/SharePoint? As I have seen instances where Office that is not licensed by the signed in user by way of an M365 account and that can cause access issues.
Sep 10 2020 04:54 AM
Thanks for the input. As far as these issues being with one doc or many, we've only just started sharing on Teams and this is the first document. So I can't really say it's one or many. Originally the document was saved as .xls but I fixed that early. The master is .xlsx for sure but I don't know if the documents the team members are copying their data from are .xls or .xlsx. Do you think that matters? Reminder, they copy their updated tab from their document into the master.
I believe that we are all on Office 365. The office version on the master document is the same as yours with the exception that yours says "(Preview)".
I can't imagine that someone other than the person with permission to the Team is updating the document. I don't know if anyone has M365 but I can check with IT.
I have a conversation with another team member this morning who had issues yesterday but I don't imagine they will be different issues than what we are already running into. Fingers crossed.
Thanks! Have a great day.
Feb 11 2021 09:15 AM
Hello Rachele, Henry,
our team is currently facing similar issues to the ones you described. We are all working through MS teams on an excel.xlsm file and some peers are getting the below error. We all use 365, tried deleting cache, opening from the same app (teams) but the issue persists.
Do you have any hint on how to resolve it?
Thank you in advance,