Teams access problem, loading chunck 5 failed

%3CLINGO-SUB%20id%3D%22lingo-sub-1423605%22%20slang%3D%22en-US%22%3ETeams%20access%20problem%2C%20loading%20chunck%205%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1423605%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3EI%20will%20try%20to%20explain%20the%20issue%20in%20short%20summary%3A%3C%2FP%3E%3CP%3EI%20have%20a%20user%20who%20was%20granted%20access%20to%20a%20private%20channel%20(she%20was%20able%20to%20access%20the%20documents%20on%20Monday)%2C%20today%20she%20received%20the%20following%20error%3A%3C%2FP%3E%3CP%3E%22%3CEM%3E%3CSTRONG%3ELoading%20chunck%205%20failed%3C%2FSTRONG%3E%3C%2FEM%3E%22.%3C%2FP%3E%3CP%3EShe%20says%20that%20everytime%20she%20goes%20to%20private%20channel%20-%26gt%3B%20Files%20tab%2C%20she%20receives%2C%20she%20gets%20the%20following%20error%3A%20%22ChunkLoaderror%3A%20Loading%20Chunck%205%20failed%22.%3C%2FP%3E%3CP%3EShe%20restared%2C%20updated%20everything%20she%20can%2C%20log%20out%2Fin%20from%20MS%20Teams.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3C%2FP%3E%3CP%3EDino%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1423605%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUser%20Interface%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1426942%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20access%20problem%2C%20loading%20chunck%205%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1426942%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390770%22%20target%3D%22_blank%22%3E%40DiVojich%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHad%20the%20same%20thing%20happen%20to%20a%20user%20yesterday.%20It%20wasn't%20a%20private%20channel%20though%20(I%20don't%20think).%20Temporarily%20resolved%20the%20issue%20by%20doing%20the%20following%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EOpen%20Teams%26nbsp%3B%3C%2FLI%3E%3CLI%3EClick%20on%20your%20profile%20picture%3C%2FLI%3E%3CLI%3EClick%20Sign%20Out%3C%2FLI%3E%3CLI%3EGo%20to%20%25appdata%25%5CMicrosoft%5Cteams%5CCache%20and%20delete%20all%20the%20files.%3C%2FLI%3E%3CLI%3EGo%20to%20%25appdata%25%5CMicrosoft%5Cteams%5CApplication%20Cache%5CCache%20and%20delete%20all%20the%20files.%3C%2FLI%3E%3CLI%3ERestart%20Teams%20desktop%20client%20and%20sign%20in%20again.%3C%2FLI%3E%3C%2FOL%3E%3CP%3EHe%20said%20it%20worked%2C%20but%20then%20this%20morning%20the%20issue%20came%20back%20and%20doing%20this%20trick%20didn't%20work%20so%20I'm%20out%20here%20searching%20for%20answers%20as%20well.%20It%20doesn't%20happen%20in%20the%20web%20client%20so%20maybe%20a%20Teams%20reinstall%20will%20fix%20it%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi all,

I will try to explain the issue in short summary:

I have a user who was granted access to a private channel (she was able to access the documents on Monday), today she received the following error:

"Loading chunck 5 failed".

She says that everytime she goes to private channel -> Files tab, she receives, she gets the following error: "ChunkLoaderror: Loading Chunck 5 failed".

She restared, updated everything she can, log out/in from MS Teams.

 

Kind regards,

Dino

 

1 Reply
Highlighted

@DiVojich 

 

Had the same thing happen to a user yesterday. It wasn't a private channel though (I don't think). Temporarily resolved the issue by doing the following: 

 

  1. Open Teams 
  2. Click on your profile picture
  3. Click Sign Out
  4. Go to %appdata%\Microsoft\teams\Cache and delete all the files.
  5. Go to %appdata%\Microsoft\teams\Application Cache\Cache and delete all the files.
  6. Restart Teams desktop client and sign in again.

He said it worked, but then this morning the issue came back and doing this trick didn't work so I'm out here searching for answers as well. It doesn't happen in the web client so maybe a Teams reinstall will fix it?