Teams Error - "We're sorry -- We've run into an issue"

Anonymous
2020-04-07T12:43:38+00:00

When opening Teams I get this error

Reinstalling fixes the issue for a day or so, then it starts back.

Microsoft Teams | Microsoft Teams for business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2020-04-07T13:16:02+00:00

Hi GeorgeRoberson,

Since reinstall Teams can temporarily fix this issue, you can try to sign out and kill Teams from Task Manager to see how it goes.

If the problem persists, you can try to clear Teams cache to see if it can help:

1.  Fully exit the Microsoft Teams desktop client. You can right click Teams from the Icon Tray and select ‘Quit’ or run Task Manager and fully kill the process.

2.  Go to File Explorer, and type in %appdata%\Microsoft\teams.

3.  Once in the directory, you’ll see a few of the following folders:

========================================================

 a.  From within ‘Application Cache’, go to Cache and delete any of the files in the Cache location.

    *   %appdata%\Microsoft\teams\application cache\cache

 b.  From within ‘Blob_storage’, delete any files that are located in here if any.

    *   %appdata%\Microsoft\teams\blob_storage

 c.  From within ‘Cache’, delete all files.

    *   %appdata%\Microsoft\teams\Cache

 d.  From within ‘databases’, delete all files.

    *   %appdata%\Microsoft\teams\databases

 e.  From within ‘GPUCache’, delete all files.

    *   %appdata%\Microsoft\teams\GPUcache

 f.  From within ‘IndexedDB’, delete the .db file.

    *   %appdata%\Microsoft\teams\IndexedDB

 g.  From within ‘Local Storage’, delete all files.

    *   %appdata%\Microsoft\teams\Local Storage

 h.  Lastly, from within ‘tmp’, delete any file.

*   %appdata%\Microsoft\teams\tmp

====================================================

Once the cleanup is finally completed, you can now restart Teams and check the results.

Best Regards,

Sylvie

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

259 additional answers

Sort by: Newest
  1. Anonymous
    2022-01-25T19:01:39+00:00

    Thanks, I already did that. What got Teams to finally work was uninstalling and re-installing 4 times, making sure to yank out every vestige of it in the Users folder.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-01-25T18:43:34+00:00

    Try reinstall Microsoft Edge WebView2: https://developer.microsoft.com/en-us/microsoft-edge/webview2/#download-section

    It helped me.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-01-18T14:03:39+00:00

    The fact that this fails on Mac tells us that the error is in the software. These fixes are touching the symptoms not the issue.

    Based on other bugs listed on this site and judging from MS's inability / willingness to address them I'd suggest that Mac users use the URL: https://teams.microsoft.com

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-01-18T13:54:38+00:00

    About 80% of the time this bash script will work (use git for bash, hyper, cygwin etc..) I made it into a function as this fails

    ON EVERY REBOOT. MICROSOFT FIX YOUR SOFTWARE!!!!!

    function blowAwayTeams() {
            tskill teams
            pushd /c/Windows/System32/
            ./cmdkey.exe //list | grep Office16_Data: | cut -d " " -f 6 | tr "\n" "\0" | xargs -0 -n1 ./cmdkey.exe /delete:
            popd
            pushd /c/Users/<YOUR USER NAME HERE>/AppData/Local/Microsoft/Teams
            ./Update.exe --uninstall
            popd
            echo "Please manually delete the following directories C:\Users\<YOUR USER NAME HERE>\AppData\Local\Microsoft\Teams*
            echo "Please manually reinstall Teams_windows_x64.exe"
    }
    

    When the above fails run it again. 80% of the time it seems to work.

    Btw if there are any MS devs the cause of this seems to be when there is a trust between domains. Don't assume users are user@company.com that is not always the case.

    The last two lines can be automated as well (they are on my box) I didn't want to upload a delete command that I won't be able to verify.

    Was this answer helpful?

    0 comments No comments