We cannot access your content. Please refresh to try again.

%3CLINGO-SUB%20id%3D%22lingo-sub-43742%22%20slang%3D%22en-US%22%3EWe%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-43742%22%20slang%3D%22en-US%22%3E%3CP%3EUsing%20latest%20client%20on%20Mac%20Sierra%26nbsp%3B10.12.3%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EYou%20have%20Microsoft%20Teams%20Version%200.7.00.401.%20It%20was%20last%20updated%20on%202%2F3%2F17.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EOne%20of%20the%20conversations%20is%20giving%20me%20%22We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20I%20press%20%22refresh%22%20button%20it%20allows%20to%20type%20new%20message%20while%20loading%20the%20conversation%20but%20as%20soon%20as%20it%20can't%20load%20it%20will%20hide%20the%20input%20bar.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20I%20was%20lucky%20enough%20to%20type%20and%20send%20message%20quickly%2C%20then%20it%20comes%20to%20the%20receiver%2C%20but%20I%20can't%20see%20the%20history%20of%20messages%20in%20conversation%2C%20as%20it%20still%20writes%26nbsp%3B%22We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FSPAN%3E%3CSPAN%3E%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-43742%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EChat%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-149830%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-149830%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Marius-%20signing%20out%20and%20in%20worked%20for%20me.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-96958%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-96958%22%20slang%3D%22en-US%22%3EFor%20the%20record%20-%20I%20had%20this%20problem%20today%20in%20two%20channels%20that%20someone%20else%20had%20recently%20created.%20I%20resolved%20the%20issue%20by%20signing%20out%20and%20back%20in%20again.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20realize%20this%20is%20an%20old%20thread%20-%20but%20the%20issue%20itself%20is%20still%20occurring%20and%20someone%20who%20is%20looking%20for%20a%20solution%20may%20find%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46262%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46262%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20Mac%20owner%20-%26gt%3B%20Unix%20based%20system%20wich%20has%20root%20user%20if%20you%20like%20to%20use%20one.%20(not%20recommended%20%3A)%3C%2Fimg%3E%20)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20assume%20web%20version%20of%20Teams%20might%20also%20use%20some%20local%20storage%20etc.%20so%20deep%20cleaning%20of%20browser%20is%20required.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOtherwise%20it%20means%20that%20there%20is%20a%20bug%20internally%20on%20the%20server%20side%20which%20you%20can't%20fix%20unless%20contacting%20administrators.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46252%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46252%22%20slang%3D%22en-US%22%3E%3CP%3ERoot%20user%3F%20Are%20you%20running%20a%20linux%20client%3F%20I%20didn't%20think%20one%20of%20those%20existed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20user%20on%20Linux%20and%20using%20the%20online%20version%20of%20Teams%20but%20is%20having%20this%20issue.%20Tried%20clearing%20his%20browser%20cache%20but%20that%20didn't%20help.%20Any%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-44056%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44056%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ELes's%20reply%20is%20correct%2C%20works%20for%20me%2C%20except%20if%20you're%20not%20a%20root%20user%20you%20should%20use%20your%20username%20directory%20in%20path.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20Teams%20directory%20is%20located%20under%20your%20user%20profile%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Eso%20add%20%22~%22%20before%20%22%2FLibrary%2FApplication%20Support%2FMicrosoft%2FTeams%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Ewhich%20is%20then%20converted%20to%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%2FUsers%2F%25username%25%2FLibrary%2FApplication%20Support%2FMicrosoft%2FTeams%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%20you%20can%20run%3A%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CPRE%3Ecd%20%22%2FUsers%2F%24(id%20-un)%2FLibrary%2FApplication%20Support%2FMicrosoft%2FTeams%22%3C%2FPRE%3E%3CP%3Ewhere%26nbsp%3B%24(id%20-un)%20expands%20to%20your%26nbsp%3Buser%20name%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOr%20just%20to%20save%20time%2C%20execute%20following%20command%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3Emv%20%22%2FUsers%2F%24(id%20-un)%2FLibrary%2FApplication%20Support%2FMicrosoft%2FTeams%22%20%22%2FUsers%2F%24(id%20-un)%2FLibrary%2FApplication%20Support%2FMicrosoft%2FTeams.bak%22%3C%2FPRE%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EYou%20can%20navigate%20using%26nbsp%3BFinder%20as%20well%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EFrom%20your%20desktop%2C%20select%20'Go'%20-%26gt%3B%20%22Go%20to%20Folder%22%20and%20type%20%22~%2FLibrary%2FApplication%20Support%2FMicrosoft%2FTeams%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Eand%20rename%20the%20Teams%20directory%20e.g.%20to%20Teams.bak%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%20everyone%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERegards%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-43961%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-43961%22%20slang%3D%22en-US%22%3E%3CP%3EWhere%20exactly%20is%20that%20directory%20found%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-43842%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-43842%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20having%20the%20same%20problem%2C%20with%20only%20one%20of%20my%20contacts%20in%20Teams.%20Only%20difference%20I'm%20running%200.7.00.3101%20as%20I%20haven't%20found%20a%20new%20version%20that%20was%20released%20today.%20Was%20working%20everywhere%20except%20on%20my%20Mac%20client.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ETo%20get%20it%20working%20I%20had%20to%20remove%20all%20my%20local%20settings%2Fhistory%20and%20start%20Teams%20from%20scratch%2C%20which%20isn't%20a%20big%20deal%20since%20history%20is%20stored%20on%20MS%20servers.%20The%20directory%20I%20had%20to%20rename%2Fdelete%20is%20in%20%2FLibrary%2FApplication%20Support%2FMicrosoft%2FTeams%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGive%20that%20a%20try.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E...Les%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-43788%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-43788%22%20slang%3D%22en-US%22%3E%3CP%3EYes.%20It%20works%20using%20web%20access.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20about%20desktop%20version%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-43781%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-43781%22%20slang%3D%22en-US%22%3EHave%20you%20tried%20to%20access%20the%20info.%20using%20the%20Web%20access%20to%20teams%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1537894%22%20slang%3D%22en-US%22%3ERe%3A%20We%20cannot%20access%20your%20content.%20Please%20refresh%20to%20try%20again.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1537894%22%20slang%3D%22en-US%22%3E%3CP%3E-ERR%3AREF-NOT-FOUND-%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBehaviour%20remains%20the%20same%20even%20with%20Teams%20on%20Web.%3C%2FP%3E%3CP%3ERemains%20same%20even%20if%20logged%20out%20and%20logged%20in%20or%20even%20system%20is%20restarted%3C%2FP%3E%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Using latest client on Mac Sierra 10.12.3

 

You have Microsoft Teams Version 0.7.00.401. It was last updated on 2/3/17.

 

One of the conversations is giving me "We cannot access your content. Please refresh to try again.".

If I press "refresh" button it allows to type new message while loading the conversation but as soon as it can't load it will hide the input bar.

 

If I was lucky enough to type and send message quickly, then it comes to the receiver, but I can't see the history of messages in conversation, as it still writes "We cannot access your content. Please refresh to try again."

10 Replies
Have you tried to access the info. using the Web access to teams?

Yes. It works using web access.

 

What about desktop version?

I was having the same problem, with only one of my contacts in Teams. Only difference I'm running 0.7.00.3101 as I haven't found a new version that was released today. Was working everywhere except on my Mac client.


To get it working I had to remove all my local settings/history and start Teams from scratch, which isn't a big deal since history is stored on MS servers. The directory I had to rename/delete is in /Library/Application Support/Microsoft/Teams

 

Give that a try.

 

...Les

Where exactly is that directory found?

Les's reply is correct, works for me, except if you're not a root user you should use your username directory in path.

 

The Teams directory is located under your user profile,

so add "~" before "/Library/Application Support/Microsoft/Teams"

which is then converted to:

/Users/%username%/Library/Application Support/Microsoft/Teams

 

So you can run:

cd "/Users/$(id -un)/Library/Application Support/Microsoft/Teams"

where $(id -un) expands to your user name

 

Or just to save time, execute following command:

 

mv "/Users/$(id -un)/Library/Application Support/Microsoft/Teams" "/Users/$(id -un)/Library/Application Support/Microsoft/Teams.bak"

 

You can navigate using Finder as well

From your desktop, select 'Go' -> "Go to Folder" and type "~/Library/Application Support/Microsoft/Teams"

and rename the Teams directory e.g. to Teams.bak

 

Thanks everyone,

 

Regards

 

Root user? Are you running a linux client? I didn't think one of those existed.

 

I have a user on Linux and using the online version of Teams but is having this issue. Tried clearing his browser cache but that didn't help. Any ideas?

I'm Mac owner -> Unix based system wich has root user if you like to use one. (not recommended :) )

 

I assume web version of Teams might also use some local storage etc. so deep cleaning of browser is required.

 

Otherwise it means that there is a bug internally on the server side which you can't fix unless contacting administrators.

For the record - I had this problem today in two channels that someone else had recently created. I resolved the issue by signing out and back in again.

I realize this is an old thread - but the issue itself is still occurring and someone who is looking for a solution may find this.

Thanks Marius- signing out and in worked for me. 

@Juan Carlos González Martín 

 

Behaviour remains the same even with Teams on Web.

Remains same even if logged out and logged in or even system is restarted