FSLogix Teams Something Went Wrong

Question

FSLogix Teams Something Went Wrong

Andy S 26

Citrix Virtual Apps and Desktops 2203 LTSR CU2 environment, customer currently has this VDA installed on Server 2016 and no SSO issues or errors in Teams or Office.

New environment consists of the VDA on Server 2019 with latest Teams Per-Machine Installer 1.6.00.6754 and FSLogix 2210 hotfix 1 (2.9.8440.42104) & RoamIdentity set to 1.

Randomly, users will get errors shown below, if they sign out of Teams and back in it works for an unknown amount of time. We can try to clear out any Teams folders in their AppData but it's only temporary.

If I disable the FSLogix GPO (the same one used in the Server 2016 VDA environment, with the addition of the RoamIdentity setting), therefore the users get a new local profile, the users never get this issue in Teams. Teams is not redirected to the Office container, it lives in the Profile container, per the GPO setting. The only exclusions I have for Teams are the Cache folders in their AppData, I've also tried to not set any exclusions/redirections for Teams and left everything in the profile, same issue. Why does FSLogix cause this issue when their Profile and Office disks are mounted?

User's image

SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-08T01:57:44.3166667+00:00
Hi @Andy S

Does the Teams web client have the same problem?

Does anyone else in the organization have the same problem?

Based on your description, this could be caused by Teams caching or updating issues. Try the following steps to troubleshoot this issue:

With a stable network, try checking the issue in the Teams web client.

Try signing out of Teams and signing back in.

Check that your hardware meets the requirements in the documentation.

Check if you have the latest version of Environment or Teams installed.
Andy S 26 Reputation points

2023-05-08T14:19:27.94+00:00

@SokiGuo-MSFT Customer doesn't use Teams via Web, have always been Teams Machine-Wide Installer, no issues in Server 2016, issue first observed in Server 2019.

Network is stable.

As mentioned, if you sign out of Teams it may work temporarily until the next time it occurs.

Hardware requirements met, following the Non-Persistent requirements per MS: https://learn.microsoft.com/en-us/microsoftteams/teams-for-vdi#non-persistent-setup

I also mentioned they have "latest Teams Per-Machine Installer".
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-10T02:39:45.4766667+00:00
Hi

To narrow down the problem, we need to check that the Teams web client can sign in properly to determine if it's just the desktop client's issue.

From the above description, it seems that the cache data is caused by a large number of profile container controls, to clean up the Teams cache on FSLogix, you can try the following steps:

Quit Teams and delete the following cache folder in the user profile:

%appdata%\Microsoft\Teams\Application Cache\Cache

%appdata%\Microsoft\Teams\blob_storage

%appdata%\Microsoft\Teams\Cache

%appdata%\Microsoft\Teams\databases

%appdata%\Microsoft\Teams\GPUcache

%appdata%\Microsoft\Teams\IndexedDB

%appdata%\Microsoft\Teams\Local Storage

%appdata%\Microsoft\Teams\tmp
Andy S 26 Reputation points

2023-05-10T13:42:07.6033333+00:00

@SokiGuo-MSFT Teams web is a different way to SSO into the app, they don't have issues there, just with the installed Teams Machine-Wide Installer.

I also mentioned that "We can try to clear out any Teams folders in their AppData but it's only temporary.", all Teams appdata folders have been cleared.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-12T06:15:11.17+00:00
Hi @Andy S

Based on your description, this seems to be just an issue with the Teams desktop client. Try a few things to check if it works:

Close any applications or browser tabs that you don't use.

Check that your client version is up to date.

Try to clean up other meaningless things in your computer to make sure that the computer is freeing up enough cache.

Disable GPU hardware acceleration in Teams. To disable this feature, select the Settings and more menu selection next to your profile picture in the upper-right corner of Teams.

If you're out of luck, please uninstall and reinstall the Teams client.
Andy S 26 Reputation points

2023-05-12T13:31:36.01+00:00

@SokiGuo-MSFT all those steps are already done, just tried disabling GPU acceleration and same result, plenty of room for cache on the computer and no other "meaningless things" are on the system
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-16T05:51:06.7766667+00:00

Hi

How long has this problem been going on?

Sign into this Teams account with another device to troubleshoot if it's an issue with your environment.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-22T02:47:13.6333333+00:00

Hi

Haven't received your message for a long time.

Do you have any further issue on this topic?
Andy S 26 Reputation points

2023-05-22T13:11:22.7966667+00:00

@SokiGuo-MSFT ever since they started testing Server 2019, Server 2016 works just fine with the same GPO's. Installed software versions are also the same between environments.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-24T05:15:39.2833333+00:00

Hi

Is there any error code in the login interface?

Based on our research, this seems to be a known issue described in this document:

https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues
Andy S 26 Reputation points

2023-05-24T13:18:42.62+00:00

@SokiGuo-MSFT no, just the error shown in my screenshots above, no specific error codes in the event logs either.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-26T05:05:26.7466667+00:00

Hi

Does the workaround for the known issue mentioned in the above article also not work?

Unexpected VHD disk compaction results：

Affected version(s): 2210 (2.9.8361.52326), 2210 hotfix 1 (2.9.8440.42104)

Using ProfileType = 3 or VHDAccessMode = 1,2, or 3, differencing disks are used. This affects the VHD disk compaction process because the size of the differencing disk is used to evaluate the thresholds. Most often these differencing disks are small and never meet the thresholds.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-30T01:24:34.2133333+00:00

Hi

Haven't received your message for a long time.

Do you have any further issue on this topic?
Andy S 26 Reputation points

2023-05-31T13:55:24.0933333+00:00

@SokiGuo-MSFT we don't use the disk compaction feature, we disable it
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-06-01T06:56:54.0733333+00:00

Hi

We are looking into this. If there are any updates, we will post them here.
Van den Broeck, Lucas 5 Reputation points

2023-06-02T10:33:26.0766667+00:00

Just wanted to add that we've been getting the exact same problem on a CVAD 1912 CU3 environment, Server 2019 with UPM as profile mgmt solution. FSlogix agent is present but the users in scope of the issue are not touched by FSlogix and have a UPM profile (pre vdisk)

We have a handful of users with this issue (as far as we are aware of). We've been running on server 2019 for years, so the issue is 'newly introduced' and most likely related to one of the windows updates CU's from Q1 2023, since that is the only thing that has changed in our environment when it started surfacing.
We've updated Teams machine installer from 1.5.0.4689 where we already had this issue up to 1.6.0.4472 but the issue remains.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-06-06T02:47:11.8433333+00:00

Hi

According to our research, there are some issues experiencing when using Microsoft Teams in a CVAD 1912 CU3 environment due to a known issue that affects some users using this VDA version. This issue may be related to the virtual channel allow list feature, which may not be available in Microsoft Teams. At this time, Citrix does not provide a fix or workaround for this issue. You can check the Citrix documentation for any updates on this issue.
Andy S 26 Reputation points

2023-06-06T13:14:27.6933333+00:00

@SokiGuo-MSFT our customer is using 2203 LTSR CU2 VDA, not 1912 CU3.
Anonymous

2023-06-08T13:42:24.6+00:00

This link lists issues fixed after Citrix Virtual Apps and Desktops 7 2203 LTSR, some of which may be related to Teams sign-in：https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/2203-ltsr/whats-new/cumulative-update-2/fixed-issues.html
Andy S 26 Reputation points

2023-06-08T13:46:57.1566667+00:00

Thanks for the link @Anonymous but the customer is using 2203 LTSR CU2 VDA, those fixes are mentioned in CU1
Anonymous

2023-06-08T14:05:45.72+00:00

This is very unreasonable ah. …Is there a problem with only Teams in the environment? Can other software run well?
Andy S 26 Reputation points

2023-06-08T14:22:15.0666667+00:00

@Anonymous only Teams, other apps including Office C2R work just fine
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-06-09T08:22:35.8033333+00:00
Hi

You try the following method to check if it works:

On the VDA, open Registry Editor (regedit.exe).

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Graphics.

Under the Graphics key, create a DWORD value called EnableTimerPeriod and modify it if it already exists.

Set the value of EnableTimerPeriod to 1.

Restart the VDA.
Andy S 26 Reputation points

2023-06-09T15:14:37.5966667+00:00

@SokiGuo-MSFT thanks for the suggestion, but that appears to be for pre-CU2, as mentioned in the Citrix docs article as well as their blog:
Jan G 0 Reputation points

2023-06-19T16:07:04.56+00:00

we have exactly the same problem. S2019 2203CU3 FSLOGIX. is there a solution in the meantime? it's also annoying that employees can't get out of the "restart teams" screen.

Your answer

SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-08T01:57:44.3166667+00:00

Hi @Andy S

Does the Teams web client have the same problem?

Does anyone else in the organization have the same problem?

Based on your description, this could be caused by Teams caching or updating issues. Try the following steps to troubleshoot this issue:

With a stable network, try checking the issue in the Teams web client.

Try signing out of Teams and signing back in.

Check that your hardware meets the requirements in the documentation.

Check if you have the latest version of Environment or Teams installed.
Andy S 26 Reputation points

2023-05-08T14:19:27.94+00:00

@SokiGuo-MSFT Customer doesn't use Teams via Web, have always been Teams Machine-Wide Installer, no issues in Server 2016, issue first observed in Server 2019.

Network is stable.

As mentioned, if you sign out of Teams it may work temporarily until the next time it occurs.

Hardware requirements met, following the Non-Persistent requirements per MS: https://learn.microsoft.com/en-us/microsoftteams/teams-for-vdi#non-persistent-setup

I also mentioned they have "latest Teams Per-Machine Installer".
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-10T02:39:45.4766667+00:00

Hi

To narrow down the problem, we need to check that the Teams web client can sign in properly to determine if it's just the desktop client's issue.

From the above description, it seems that the cache data is caused by a large number of profile container controls, to clean up the Teams cache on FSLogix, you can try the following steps:

Quit Teams and delete the following cache folder in the user profile:

%appdata%\Microsoft\Teams\Application Cache\Cache

%appdata%\Microsoft\Teams\blob_storage

%appdata%\Microsoft\Teams\Cache

%appdata%\Microsoft\Teams\databases

%appdata%\Microsoft\Teams\GPUcache

%appdata%\Microsoft\Teams\IndexedDB

%appdata%\Microsoft\Teams\Local Storage

%appdata%\Microsoft\Teams\tmp
Andy S 26 Reputation points

2023-05-10T13:42:07.6033333+00:00

@SokiGuo-MSFT Teams web is a different way to SSO into the app, they don't have issues there, just with the installed Teams Machine-Wide Installer.

I also mentioned that "We can try to clear out any Teams folders in their AppData but it's only temporary.", all Teams appdata folders have been cleared.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-12T06:15:11.17+00:00

Hi @Andy S

Based on your description, this seems to be just an issue with the Teams desktop client. Try a few things to check if it works:

Close any applications or browser tabs that you don't use.

Check that your client version is up to date.

Try to clean up other meaningless things in your computer to make sure that the computer is freeing up enough cache.

Disable GPU hardware acceleration in Teams. To disable this feature, select the Settings and more menu selection next to your profile picture in the upper-right corner of Teams.

If you're out of luck, please uninstall and reinstall the Teams client.
Andy S 26 Reputation points

2023-05-12T13:31:36.01+00:00

@SokiGuo-MSFT all those steps are already done, just tried disabling GPU acceleration and same result, plenty of room for cache on the computer and no other "meaningless things" are on the system
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-16T05:51:06.7766667+00:00

Hi

How long has this problem been going on?

Sign into this Teams account with another device to troubleshoot if it's an issue with your environment.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-22T02:47:13.6333333+00:00

Hi

Haven't received your message for a long time.

Do you have any further issue on this topic?
Andy S 26 Reputation points

2023-05-22T13:11:22.7966667+00:00

@SokiGuo-MSFT ever since they started testing Server 2019, Server 2016 works just fine with the same GPO's. Installed software versions are also the same between environments.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-24T05:15:39.2833333+00:00

Hi

Is there any error code in the login interface?

Based on our research, this seems to be a known issue described in this document:

https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues
Andy S 26 Reputation points

2023-05-24T13:18:42.62+00:00

@SokiGuo-MSFT no, just the error shown in my screenshots above, no specific error codes in the event logs either.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-26T05:05:26.7466667+00:00

Hi

Does the workaround for the known issue mentioned in the above article also not work?

Unexpected VHD disk compaction results：

Affected version(s): 2210 (2.9.8361.52326), 2210 hotfix 1 (2.9.8440.42104)

Using ProfileType = 3 or VHDAccessMode = 1,2, or 3, differencing disks are used. This affects the VHD disk compaction process because the size of the differencing disk is used to evaluate the thresholds. Most often these differencing disks are small and never meet the thresholds.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-05-30T01:24:34.2133333+00:00

Hi

Haven't received your message for a long time.

Do you have any further issue on this topic?
Andy S 26 Reputation points

2023-05-31T13:55:24.0933333+00:00

@SokiGuo-MSFT we don't use the disk compaction feature, we disable it
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-06-01T06:56:54.0733333+00:00

Hi

We are looking into this. If there are any updates, we will post them here.
Van den Broeck, Lucas 5 Reputation points

2023-06-02T10:33:26.0766667+00:00

Just wanted to add that we've been getting the exact same problem on a CVAD 1912 CU3 environment, Server 2019 with UPM as profile mgmt solution. FSlogix agent is present but the users in scope of the issue are not touched by FSlogix and have a UPM profile (pre vdisk)

We have a handful of users with this issue (as far as we are aware of). We've been running on server 2019 for years, so the issue is 'newly introduced' and most likely related to one of the windows updates CU's from Q1 2023, since that is the only thing that has changed in our environment when it started surfacing.
We've updated Teams machine installer from 1.5.0.4689 where we already had this issue up to 1.6.0.4472 but the issue remains.
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-06-06T02:47:11.8433333+00:00

Hi

According to our research, there are some issues experiencing when using Microsoft Teams in a CVAD 1912 CU3 environment due to a known issue that affects some users using this VDA version. This issue may be related to the virtual channel allow list feature, which may not be available in Microsoft Teams. At this time, Citrix does not provide a fix or workaround for this issue. You can check the Citrix documentation for any updates on this issue.
Andy S 26 Reputation points

2023-06-06T13:14:27.6933333+00:00

@SokiGuo-MSFT our customer is using 2203 LTSR CU2 VDA, not 1912 CU3.
Anonymous

2023-06-08T13:42:24.6+00:00

This link lists issues fixed after Citrix Virtual Apps and Desktops 7 2203 LTSR, some of which may be related to Teams sign-in：https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/2203-ltsr/whats-new/cumulative-update-2/fixed-issues.html
Andy S 26 Reputation points

2023-06-08T13:46:57.1566667+00:00

Thanks for the link @Anonymous but the customer is using 2203 LTSR CU2 VDA, those fixes are mentioned in CU1
Anonymous

2023-06-08T14:05:45.72+00:00

This is very unreasonable ah. …Is there a problem with only Teams in the environment? Can other software run well?
Andy S 26 Reputation points

2023-06-08T14:22:15.0666667+00:00

@Anonymous only Teams, other apps including Office C2R work just fine
SokiGuo-MSFT 31,541 Reputation points Microsoft External Staff

2023-06-09T08:22:35.8033333+00:00

Hi

You try the following method to check if it works:

On the VDA, open Registry Editor (regedit.exe).

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Graphics.

Under the Graphics key, create a DWORD value called EnableTimerPeriod and modify it if it already exists.

Set the value of EnableTimerPeriod to 1.

Restart the VDA.
Andy S 26 Reputation points

2023-06-09T15:14:37.5966667+00:00

@SokiGuo-MSFT thanks for the suggestion, but that appears to be for pre-CU2, as mentioned in the Citrix docs article as well as their blog:
Jan G 0 Reputation points

2023-06-19T16:07:04.56+00:00

we have exactly the same problem. S2019 2203CU3 FSLOGIX. is there a solution in the meantime? it's also annoying that employees can't get out of the "restart teams" screen.

Share via

FSLogix Teams Something Went Wrong

Your answer