SOLVED

"Unknown Error" when clicking on file in Teams

%3CLINGO-SUB%20id%3D%22lingo-sub-308638%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308638%22%20slang%3D%22en-US%22%3E%3CP%3EBob%2C%20sorry%20for%20a%20few%20questions%3A%3C%2FP%3E%3CP%3E-%20Are%20you%20using%20the%20web%20version%20of%20Teams%20or%20the%20installed%20version%3F%20If%20the%20web%20version%2C%20perhaps%20re-start%20the%20browser%20or%20try%20a%20different%20one%3F%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Are%20you%20clicking%20on%20an%20Office%20document%20(Word%2C%20Excel)%2C%20and%20if%20yes%2C%20did%20that%20document%20open%20before%2C%20and%20if%20not%20is%20it%20an%20older%20version%20of%20Office%20(e.g.%2C%20doc)%20or%20a%20non-Office%20document%3F%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Network%20or%20computer%20issues%3F%20Perhaps%20try%20the%20'turn%20it%20off%20and%20on%20again'%20option%3F%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Anything%20else%20to%20help%20us%20identify%20what%20the%20problem%20might%20be%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308635%22%20slang%3D%22en-US%22%3E%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308635%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20getting%20the%20following%20error%20when%20clicking%20on%20a%20file%20in%20Microsoft%20Teams.%20Any%20idea%20what%20I%20can%20try%20to%20resolve%20this%3F%3C%2FP%3E%3CP%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-308635%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308637%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308637%22%20slang%3D%22en-US%22%3EWill%20the%20file%20open%20in%20SharePoint%3F%20On%20the%20Files%20tab%20select%20%22Open%20in%20SharePoint%22%2C%20then%20try%20accessing%20the%20file%20from%20there%20.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308639%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308639%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20the%20file%20will%20open%20if%20I%20open%20in%20SharePoint%20or%20if%20I%20hit%20%22open%20in%20excel%20online%22.%20It%20only%20get%20the%20error%20inside%20of%20Teams.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308643%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308643%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20occurs%20in%20both%20the%20web%20version%20and%20desktop%20application.%20Yes%20I%20am%20clicking%20on%20the%20document%20form%20the%20files%20tab...%20I%20also%20have%20files%20set%20as%20%22tabs%22%20in%20the%20channel%20and%20they%20do%20the%20same%20thing%20from%20there.%20If%20I%20click%20on%20a%20file%20in%20a%20conversation...%20same%20result.%20And%20yes%20sir%2C%20I%20did%20try%20completely%20signing%20out%20of%20everything%20Microsoft%20and%20restarting%20the%20computer.%20Same%20result.%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308645%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308645%22%20slang%3D%22en-US%22%3ESounds%20like%20an%20update%20gone%20wrong%20possibly.%20Is%20it%20all%20files%20or%20just%20the%20one%3F%20Or%20just%20xlsx%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308649%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308649%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20all%20files.%20Excel%2C%20Word%2C%20PDFs%2C%20png%2C%20etc...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308650%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308650%22%20slang%3D%22en-US%22%3EIf%20it's%20happening%20for%20other%20users%20as%20well%20and%20it's%20on%20web%20too%20as%20you%20said%2C%20then%20I%20would%20get%20a%20support%20ticket%20in%20asap.%20Not%20sure%20the%20service%20the%20Teams%20App%20connects%20to%2C%20to%20render%2C%20but%20it's%20working%20for%20me%2C%20might%20be%20something%20in%20your%20tenant%20%2F%20datacenter%20or%20something%20gone%20wrong.%20But%20if%20it's%20easy%20to%20reproduce%20via%20web%2C%20with%20more%20than%20one%20user%20you%20might%20have%20something%20going%20on%20there%20that%20needs%20reported.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308655%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308655%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20not%20for%20every%20user.%20It%20has%20actually%20only%20happened%20to%20two%20users.%20It%20happened%20last%20week%20and%20lasted%20for%20about%20a%20day%20for%20one%20user....%20then%20it%20started%20working%20again.%20It%20happened%20to%20me%20also%20for%20about%20a%20day%20then%20started%20working%20again.%20But%20now%20it%20is%20happening%20again%20to%20me.%20It's%20crazy.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308656%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308656%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%20with%20Chris%2C%20check%20with%20other%20users%20and%20if%20it's%20widespread%2C%20log%20a%20ticket.%20We%20are%20having%20no%20issues%20(in%20Sydney%2C%20Australia)%20with%20this.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308663%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308663%22%20slang%3D%22en-US%22%3EOdd%20it's%20only%20a%20couple.%20Are%20both%20users%20located%20behind%20a%20corporate%20firewall%20%2F%20machine%20firewall%3F%20Wondering%20if%20the%20actual%20service%20itself%20is%20triggering%20anything%20there.%20Only%20other%20thing%20I%20could%20really%20think%20of%20that%20could%20cause%20it%2C%20seeing%20as%20I%20bet%20the%20opening%20of%20documents%20in%20Teams%20probably%20connects%20too%20and%20is%20rendered%20by%20the%20same%20service%20%2F%20engine%20the%20web%20page%20uses.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308669%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308669%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20both%20machines%20are%20behind%20a%20corporate%20firewall%2C%20but%20ALL%20of%20the%20machines%20are%20behind%20the%20same%20firewall%20with%20the%20same%20settings.%20Its%20just%20really%20weird%20to%20me%20that%20it%20works%20for%20awhile%20(like%20a%20week%20or%20so)%20then%20it%26nbsp%3Bthe%20error%20shows%20up%20again%20for%20a%20day%20or%20so.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308671%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308671%22%20slang%3D%22en-US%22%3EYeah%2C%20odd.%20Hopefully%20support%20can%20help%20solve%2C%20but%20if%20you%20can't%20reproduce%20it%20now%2C%20might%20be%20hard%20to%20pin%20down%2C%20just%20reach%20out%20while%20it's%20happening%20to%20get%20some%20logs%20etc.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-774207%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-774207%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F260172%22%20target%3D%22_blank%22%3E%40Bob_Heinze%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExperienced%20this%20today%20with%20myself%20and%20another%20user.%20Adding%20here%20to%20help%20others.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EI%20happened%20to%20close%20Teams%20at%20lunch%20and%20didn't%20reopen%20until%205pm.%20Works%20now.%26nbsp%3B%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3ESeems%20like%20some%20sort%20of%20login%20cache%20issue.%26nbsp%3B%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EI%20didn't%20sign%20out%20on%20my%20phone%2C%20but%20wasn't%20using%20teams.%26nbsp%3B%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EI%20was%20also%20signed%20into%20Office%20all%20day.%26nbsp%3B%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EHope%20this%20helps%20someone%20else.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1262843%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262843%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F331527%22%20target%3D%22_blank%22%3E%40Bionicjoe%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20the%20same%20issue.%26nbsp%3B%20For%20several%20days%20I%20just%20used%20the%20web%20version%20as%20a%20workaround.%26nbsp%3B%20Restarted%20several%20times%20but%20that%20didn't%20fix%20the%20issue.%26nbsp%3B%20Finally%2C%20I%20went%20into%20Task%20Manager%20and%20removed%20all%20tasks%20related%20to%20MS%20Teams.%26nbsp%3B%20That%20finally%20resolved%20it%20for%20me.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps%20someone.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1509914%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1509914%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4163%22%20target%3D%22_blank%22%3E%40Andrew%20Warland%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20having%20this%20same%20issue.%26nbsp%3B%20We're%20using%20the%20free%20version%20of%20Teams.%26nbsp%3B%20The%20issue%20has%20affected%20everyone.%26nbsp%3B%20The%20files%20aren't%20on%20the%20sharepoint%20or%20on%20OneDrive.%26nbsp%3B%20I%20get%20the%20same%20result%20on%20the%20web%20app%20and%20the%20desktop%20app.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20get%20the%20%22unknown%20error%22%20when%20trying%20to%20access%20an%20xlsx%20file%20that%20we%20turned%20into%20a%20channel%20tab.%20We%20also%20get%20the%20message%20%22the%20specified%20list%20in%20invalid%22%20when%20accessing%20the%20%22Files%22%20tab%20in%20every%20channel.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20will%20be%20greatly%20appreciated.%26nbsp%3B%3C%2FP%3E%3CP%3E(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F708892%22%20target%3D%22_blank%22%3E%40Matt_Anderton%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%20adding%20you%20here%20as%20I%20noticed%20you%20had%2Fhave%20the%20same%20problem)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1532235%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1532235%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F722714%22%20target%3D%22_blank%22%3E%40rpkin%3C%2FA%3E%26nbsp%3BHi%20Ryan%2C%20I%20have%20a%20few%20questions%20about%20this.%20First%2C%20when%20you%20say%20you%20are%20using%20the%20'free'%20version%20of%20MS%20Teams%2C%20what%20actually%20does%20that%20mean%3F%20Do%20you%20have%20a%20corporate%20licence%20for%20Microsoft%20365%20and%20if%20so%2C%20what%20licence%20type%20(e.g.%2C%20E3%2C%20E1%20etc)%3F%20If%20you%20don't%20have%20a%20corporate%20licence%2C%20then%20you%20won't%20be%20able%20to%20access%20SharePoint%20which%20also%20means%20OneDrive.%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20I'm%20wondering%20what%20you%20are%20actually%20doing.%20I'm%20happy%20to%20help%20out%20but%20need%20a%20bit%20more%20basic%20info%20first%2C%20starting%20with%20your%20licence%20type.%20It%20is%20possible%20your%20users%20are%20'front%20line%20workers'%3F%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1532245%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1532245%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F722714%22%20target%3D%22_blank%22%3E%40rpkin%3C%2FA%3E%26nbsp%3BI%20assume%20you%20are%20trying%20to%20do%20something%20like%20this%20...%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22%23%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22MSTeamsWordTab.JPG%22%20style%3D%22width%3A%20509px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F206299i692A590B91A4DB49%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22MSTeamsWordTab.JPG%22%20alt%3D%22MSTeamsWordTab.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%3CDIV%20class%3D%22lia-spoiler-container%22%3E%3CA%20class%3D%22lia-spoiler-link%22%20href%3D%22%23%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESpoiler%3C%2FA%3E%3CNOSCRIPT%3E(Highlight%20to%20read)%3C%2FNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-border%22%3E%3CDIV%20class%3D%22lia-spoiler-content%22%3E%26nbsp%3B%3C%2FDIV%3E%3CNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-noscript-container%22%3E%3CDIV%20class%3D%22lia-spoiler-noscript-content%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FNOSCRIPT%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F722714%22%20target%3D%22_blank%22%3E%40rpkin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1533183%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1533183%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4163%22%20target%3D%22_blank%22%3E%40Andrew%20Warland%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20actually%20already%20done%20that%20and%20now%20when%20I%20access%20that%20tab%20I%20get%20this%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22rpkin_0-1595254409142.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F206370iCAE40E3AF9612180%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22rpkin_0-1595254409142.png%22%20alt%3D%22rpkin_0-1595254409142.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1533187%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1533187%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4163%22%20target%3D%22_blank%22%3E%40Andrew%20Warland%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20using%20the%20free%20version%20of%20Teams.%26nbsp%3B%20This%20is%20a%20screen%20shot%20from%20the%20Microsoft%20website%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22rpkin_0-1595254593772.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F206371iFDF6E0BD551D1A78%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22rpkin_0-1595254593772.png%22%20alt%3D%22rpkin_0-1595254593772.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ESo%20you%20can%20see%20in%20the%20image%20that%20it%20lists%20file%20storage.%26nbsp%3B%20We%20were%20using%20this%20file%20storage%20and%20it%20appears%20to%20be%20gone%20now.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1551817%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1551817%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F722714%22%20target%3D%22_blank%22%3E%40rpkin%3C%2FA%3E%26nbsp%3Bhi%20thanks%20and%20sorry%20for%20the%20delay%20replying.%20It%20certainly%20seems%20unusual%20to%20have%20lost%20this%20ability%20and%20I'm%20wondering%20what%20else%20may%20be%20happening%20here%20to%20cause%20it.%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20indicate%20you%20get%20up%20to%2010GB%20of%20file%20storage%20plus%202%20GB%20per%20person.%20Is%20there%20any%20chance%20that%20limit%20has%20been%20reached%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-au%2Fmicrosoft-365%2Fmicrosoft-teams%2Ffree%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-au%2Fmicrosoft-365%2Fmicrosoft-teams%2Ffree%3C%2FA%3E%3C%2FP%3E%3CP%3EIf%20not%2C%20is%20everyone%20having%20the%20same%20issue%3F%20There%20must%20be%20a%20conflict%20here%20somewhere.%20Can%20you%20open%20that%20file%20when%20you%20are%20not%20in%20Teams%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1551842%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1551842%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4163%22%20target%3D%22_blank%22%3E%40Andrew%20Warland%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20definitely%20didn't%20run%20out%20of%20space.%26nbsp%3B%20Everyone%20on%20in%20our%20organization%20is%20experiencing%20this.%20I've%20tried%20everything%20I%20know%20possible.%26nbsp%3B%20I've%20determine%20that%20the%20problem%20lies%20on%20Microsoft's%20end%20and%20it%20revolves%20around%20the%20sharepoint%20site%20that%20supports%20our%20Teams%20accounts.%20Since%20the%20problem%20is%20on%20Microsoft's%20end%20and%20being%20that%20this%20is%20the%20free%20version%20of%20Teams%2C%20it%20appears%20that%20they%20aren't%20going%20to%20provide%20any%20assistance%20to%20return%20the%20functionality.%26nbsp%3B%20I've%20contacted%20support%20multiple%20times%20with%20zero%20luck.%26nbsp%3B%20I%20keep%20getting%20bounced%20around%20from%20one%20support%20division%20to%20another%20with%20none%20of%20them%20offering%20any%20help.%26nbsp%3B%20I'm%20at%20a%20total%20loss.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1554617%22%20slang%3D%22en-US%22%3ERe%3A%20%22Unknown%20Error%22%20when%20clicking%20on%20file%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1554617%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F722714%22%20target%3D%22_blank%22%3E%40rpkin%3C%2FA%3E%26nbsp%3Bsorry%20to%20hear%20this.%20FWIW%2C%20I%20tried%20to%20set%20up%20a%20free%20version%20yesterday%20to%20try%20to%20replicate%20this%2C%20but%20ended%20up%20with%20so%20many%20issues%20I%20abandoned%20the%20idea.%20Better%20to%20get%20licences%20I%20think%20as%20'free'%20usually%20comes%20at%20the%20expense%20of%20support.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I am getting the following error when clicking on a file in Microsoft Teams. Any idea what I can try to resolve this?

error.PNG

22 Replies
Highlighted
Will the file open in SharePoint? On the Files tab select "Open in SharePoint", then try accessing the file from there .
Highlighted

Bob, sorry for a few questions:

- Are you using the web version of Teams or the installed version? If the web version, perhaps re-start the browser or try a different one? 

- Are you clicking on an Office document (Word, Excel), and if yes, did that document open before, and if not is it an older version of Office (e.g., doc) or a non-Office document? 

- Network or computer issues? Perhaps try the 'turn it off and on again' option? 

- Anything else to help us identify what the problem might be? 

Highlighted

Yes, the file will open if I open in SharePoint or if I hit "open in excel online". It only get the error inside of Teams. 

Highlighted

It occurs in both the web version and desktop application. Yes I am clicking on the document form the files tab... I also have files set as "tabs" in the channel and they do the same thing from there. If I click on a file in a conversation... same result. And yes sir, I did try completely signing out of everything Microsoft and restarting the computer. Same result. :(

Highlighted
Sounds like an update gone wrong possibly. Is it all files or just the one? Or just xlsx?
Highlighted

It's all files. Excel, Word, PDFs, png, etc...

Highlighted
Best Response confirmed by Bob_Heinze (Occasional Contributor)
Solution
If it's happening for other users as well and it's on web too as you said, then I would get a support ticket in asap. Not sure the service the Teams App connects to, to render, but it's working for me, might be something in your tenant / datacenter or something gone wrong. But if it's easy to reproduce via web, with more than one user you might have something going on there that needs reported.
Highlighted

It's not for every user. It has actually only happened to two users. It happened last week and lasted for about a day for one user.... then it started working again. It happened to me also for about a day then started working again. But now it is happening again to me. It's crazy. 

Highlighted

I agree with Chris, check with other users and if it's widespread, log a ticket. We are having no issues (in Sydney, Australia) with this. 

Highlighted
Odd it's only a couple. Are both users located behind a corporate firewall / machine firewall? Wondering if the actual service itself is triggering anything there. Only other thing I could really think of that could cause it, seeing as I bet the opening of documents in Teams probably connects too and is rendered by the same service / engine the web page uses.
Highlighted

Yes, both machines are behind a corporate firewall, but ALL of the machines are behind the same firewall with the same settings. Its just really weird to me that it works for awhile (like a week or so) then it the error shows up again for a day or so. 

Highlighted
Yeah, odd. Hopefully support can help solve, but if you can't reproduce it now, might be hard to pin down, just reach out while it's happening to get some logs etc.
Highlighted

@Bob_Heinze 

Experienced this today with myself and another user. Adding here to help others. 

I happened to close Teams at lunch and didn't reopen until 5pm. Works now. 
Seems like some sort of login cache issue. 

I didn't sign out on my phone, but wasn't using teams. 
I was also signed into Office all day. 

Hope this helps someone else. 

Highlighted

@Bionicjoe 

I have the same issue.  For several days I just used the web version as a workaround.  Restarted several times but that didn't fix the issue.  Finally, I went into Task Manager and removed all tasks related to MS Teams.  That finally resolved it for me.

 

Hope this helps someone.

Highlighted

@Chris Webb @Andrew Warland 

I am having this same issue.  We're using the free version of Teams.  The issue has affected everyone.  The files aren't on the sharepoint or on OneDrive.  I get the same result on the web app and the desktop app.  

 

I get the "unknown error" when trying to access an xlsx file that we turned into a channel tab. We also get the message "the specified list in invalid" when accessing the "Files" tab in every channel. 

 

Any help will be greatly appreciated. 

(@Matt_Anderton  adding you here as I noticed you had/have the same problem)

Highlighted

@rpkin Hi Ryan, I have a few questions about this. First, when you say you are using the 'free' version of MS Teams, what actually does that mean? Do you have a corporate licence for Microsoft 365 and if so, what licence type (e.g., E3, E1 etc)? If you don't have a corporate licence, then you won't be able to access SharePoint which also means OneDrive. 

But I'm wondering what you are actually doing. I'm happy to help out but need a bit more basic info first, starting with your licence type. It is possible your users are 'front line workers'? Thanks

Highlighted

@rpkin I assume you are trying to do something like this ... 

 

MSTeamsWordTab.JPG

Spoiler
 

@rpkin 

Highlighted

@Andrew Warland 

I had actually already done that and now when I access that tab I get this: 

rpkin_0-1595254409142.png

 

Highlighted

@Andrew Warland 

I'm using the free version of Teams.  This is a screen shot from the Microsoft website:

rpkin_0-1595254593772.png

So you can see in the image that it lists file storage.  We were using this file storage and it appears to be gone now.