sorry, we ran into a problem
Where do these "Sorry" error message go after they pop up and disappear?
There does not appear to be any way to "open" the message. Clicking on it does nothing.
Is there somewhere we can go to find out what the issue was?
Peter Mantos commented
I found out that the root of my problem was a company group policy that permits only owners to move files. Still, a complete error message would be nice.
Peter Mantos commented
This problem still exists after 4 years of nothing. It's frustrating enough that I can't simply move files, but there is absolutely no excuse for not being able to read the error message in order to "correct" the issue. I have no special characters in my file name (unless a blank is a special character). No message is logged to the system event viewer.
The error is frustrating. It is more frustrating that I cannot read the error message. It is inexcusable that Microsoft can ignore these BUGS for years with not even a false promise of a solution or workaround.
Potential way to get access the (or at least an error message): I tried to rename my file to simple A.xls as some posts indicate special characters as a problem source. When I attempted to rename, I got the FULL error message "Access Denied". SO, I will pursue a permissions problem.
I'm still disgusted over the lack of Microsoft's response. The least they could do is acknowledge the error, put it on a bug tracker, and give some visibility to the issue for the customers.
It must be nice to own a Monopoly that doesn't have to respond to customers or bugs.!
Edward paul commented
Hey guys few days back only I have encountered with this We’re Sorry But Excel Has Run Into An Error in my Excel application.
When I searched for the solutions to fix this error, I found this informative article, fixes listed in this post, has helped me a lot. So have a look over the fixes to resolve this issue.
chirag sadhu commented
Still a problem. Do we not have a fix for this yet?
Most of these issues are due to File Name conflicts.
Stop using special characters within filenames, it does not scale very well.
It always show 'We ran into a problem try again in a few minutes." It doesn't tell that what's the problem. I can't join my class because of it.
please remove bug
Sandeep Lal commented
Sync the time to fix the issue
Try eliminating special characters in the filename. I renamed three stubbornly unmovable files to eliminate an instance of "#" from the filename. After doing that, I was able to move them successfully.
C Thomas commented
I have the same issue.
I'm having the same issue. Anybody from Microsoft who can address the issue?
Jim Larsen commented
For crying out loud, Microsoft. LISTEN! This is basic broken functionality. If I open a file from Teams in the desktop app, the only way I can thereafter move that file within Teams is to COMPLETELY CLOSE THE DESKTOP APPLICATION FIRST. So if I have several spreadsheets open, then I open a spreadsheet in Excel from Teams, then close that spreadsheet I will be unable to move the spreadsheet to another place in Teams until I close Excel on my computer entirely. FIX THIS!
Bryan Nord commented
This is happening to Upper level management at our business when they try to move a file from one folder to another in Teams. Not a great look, and no explanation as to why.
So how to unlock a file in Teams so that it can be moved? It says it is locked by me, but I closed down the editing app and any related browser tabs. Still locked. And no unlock mechanism in sight.
Andrew Sutton commented
Microsoft - how is it possible that after more than 2 years that you haven't made error messages readable to end users? They are truncated and it isn't possible to even read what the message says properly. BASICS. Build a UX that doesn't have users in the dark with no idea what is going on!
Carlos Deras commented
Lo solucione entrando a esta direccion de mi PC C:\Users\"usuario con problemas"\AppData\Local\Microsoft , luego busquen las carpeta con nombre "teams" y las borran, despues intenten de nuevo.
When I tried to move a file I got the "Sorry we ran into a problem" error message and could not read the entire message. In case this is helpful for anyone else, the file was checked out and therefore could not be moved. As soon as the file was no longer checked out, I was able to move the file and did not get the incomplete error message.
Still having this problem in Feb 2020
Viral Naik commented
ok its jan 2020 and i got two users who has same issue while working with documents.