This message was deleted.
# microsoft-fslogixs
Slackbot
11/14/2019, 9:19 PMThis message was deleted.
d
Dennis
11/14/2019, 10:04 PMI also saw this event. Does it have any impact? Is it an AppMaking issue?
t
Tim Riegler
11/14/2019, 10:32 PMI'm not sure...Oh, that's a good idea! I'll check my AppMasking rules...
d
Dennis
11/18/2019, 7:16 AMHi Tim, I just found this: https://bit.ly/32VH0Hl It seems to be related to CloudCache, but it’s not a problem. In the next FSL release they will get them cleanup.
t
Tim Riegler
11/18/2019, 12:18 PMThanks Dennis. That link goes to the main FSLogix support FAQ, though. I was able to go through my rules and fix some of them that had groups without the domain in front of them (and were still working). For example, the rule would should SG_Allow_Group_A, instead of DOMAIN\SG_Allow_Group_A. Not sure it's working yet, haven't had a chance to check the logs this morning. I'll do so when I get in, and let you know.
Tim Riegler
11/18/2019, 1:11 PMHmmmm...still occurring after modifying all of the security groups in the App Masking rules. Unfortunately, the FSLogix logs don't tell me which user, or which SID / Group are problematic. Would be nice if the FSL logs were a bit more verbose.
c
Chris P
11/25/2019, 2:31 PMWe saw this too so I raised a support call. The official response:
"Cannot get Token from Sid" has been in the cloud cache service log for quite some time and is expected. This happens when the frxccd service attempts to query the user's token, but is unable to because it is too early in the process of a user logging in and does not have a session yet. I believe we just retry in this scenario.