06-06-2018 07:12 AM
06-06-2018 07:12 AM
We have a long-standing issue that is manifesting itself via Teams much more frequently. I have found a ton of info online related to the opening of Excel files from Network locations, and have tried everything I can get my hands on to no avail.
Scenario: Excel Spreadsheets in the FILE folder of Teams.
User has a file called May Metrics. They need to create June Metrics. So they open May Metrics and make all the changes necessary inputting the new metrics. Then they save it as JUNE METRICS.
Now when another user tries to open that file, it will say that it is corrupt, try to repair, and fail because it cannot find the file in %appdata%
At this point, the user can save the file locally, open it as expected, then upload it back to Teams. Not acceptable to the users as it adds a significant amount of time and steps to the workflow. This DID occasionally happen to the users when using a file share as well, and the same workaround was used. Copy locally, then move back. However, that workaround was a tad easier and quicker when using a file share. Not being able to drag and drop from Teams makes that more cumbersome.
It appears that if they FIRST make a copy of the MAY METRICS, rename it to JUNE METRICS and then edit the copy, it will work. That is rather confusing to me, but it does seem to be a workaround.
Solving the root problem is really what I would like to do. It just so happens that Teams makes the problem show up more frequently.
So it seems apparent that this only comes into play when a file is NOT local. Searching reveals a number of reasons for that. Many talk about turning OFF the DDE, and going to the Trust Center and UNCHECKING the three Protected View settings (all seemingly counterproductive).
I've seen the suggestions to go to Trust Center and turn off all the File Block Settings as well (again, counterproductive).
- The URL is added to the Trusted Zone.
- I tried adding the URL to Trusted Locations (including subfolders) in Excel.
- Checked the "Allow Trusted Locations on my network (which is not recommended)
- Turned off DDE
- Turned off the three Protected Views within Excel
NOTES: We can save the file locally, and it will open...but that isn't very efficient in our environment because they then have to upload it BACK to Teams (or OneDrive, or SharePoint, or Network Share) when they are done.
It seems as if we CAN open it from Excel as opposed to clicking on the file itself. Again...silly, but it does seem to work a lot of the time. You have to then go through some dialogue boxes about links to other files in locations it cannot reach, but ultimately, you can get the file open.
The files are clearly NOT CORRUPT. Maybe it has to do with the way users are making edits in some way that references a local location. I can't really tell for sure because I am not an Excel Guru.
What I do know is that the user expectation is that they should be able to click on a file and start working on it without having to jump through eleventy-billion hoops.
Has anyone else had trouble opening Excel files from Teams? I can't imagine we are the only ones considering how many people online seem to experience similar issues with Excel files in Network locations.
Lastly, the problem is happening to 2013 and 2016 users. The only real difference there appears to be that each version provides slightly different dialogue when the file opens.
Thoughts? Ideas? Job references?
06-08-2018 03:42 AM
I've experienced many of similar issues as you describe and a tip based on my experience with Excel is that if the files contain calculations or links to other files, you should use the Excel client instead of excel online. Therefore, when you are in the teams "Files tab", select "Open in Excel" instead of just click on the file to open it (which will open it in Excel online).
10-23-2019 02:29 AM
Do you have any backup policy in your dept? If yes then, you can check the backup folder.
Always try to use save as option instead of Save when you perform any changes in the file or create a copy of it before performing any action. In my office, we also faced an issue related to Excel file corruption. We have a file on a shared network. The access of that file distributed to 10 people. One day I got file extension error i.e. file extension is not valid Bla bla bla.
As you have mentioned, I tried different solutions to handle it, but no one worked for me. My friend suggested to try Excel repair software, and luckily, I got the software on the giveaway website. I downloaded it and repaired my file. The software name is Stellar Excel Repair, and It is a paid tool ($39)(luckily I got it on giveawayoftheday).
Did you get a resolution to your problem below. I am having an ongoing problem with file corruption and teams. The following is the situation:-
1) I have developed a system where an Excel file hosts a set of VBA routines. Triggering these routines causes files to be loaded or created, processed and saved.
2) For a considerable time I based the whole directory structure in a OneDrive account and it worked perfectly. I wanted to move to Teams so as the make the files more easily available to the various users (distributed globally). Moving the whole file structure to Teams was easy.
3) However, after loading an Excel workbook within this environment, I now occasionally experience a total Excel crash i.e. it just turns off and then reloads. Excel now tells me that the file is corrupt and cannot be repaired. If I download the file, send it to a colleague who loads and renames it and sends it back to me, the file is fine.
4) If I delete the original (i.e supposedly corrupted file) in Teams and upload the file returned by my colleague with the new name into Teams, it runs fine.
5) If, however, I rename the uploaded file to the original filename and attempt to load from Teams, it loads the original (supposedly corrupted) file and tells me it is corrupt.
6) I've had to abandon my attempt to use Teams and have returned the system to OneDrive where it works fine again.
Do you or anyone else have any thoughts on what is causing this problem. It's very frustrating as Teams looks like a great environment