Teams - Cannot access files in VDI environment

%3CLINGO-SUB%20id%3D%22lingo-sub-2841129%22%20slang%3D%22en-US%22%3ETeams%20-%20Cannot%20access%20files%20in%20VDI%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2841129%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20involved%20in%20two%20distinct%20organisations%20and%20we%20are%20both%20experiencing%20issues%20where%20we%20get%20an%20error%20message%20when%20trying%20to%20access%20files%20in%20the%20Teams%20Desktop%20App%20within%20the%20two%20different%20VDI%20environments%20(Citrix%20and%20Horizon).%3C%2FP%3E%3CP%3EWe%20receive%20the%20message%20'f.a%20is%20not%20a%20constructor'.%3C%2FP%3E%3CP%3EAnyone%20have%20a%20resolution%20or%20know%20why%20both%20organisations%20are%20experiencing%20this%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22lornaschmidt_0-1634116526811.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317001i7EB0A9C0F073729D%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22lornaschmidt_0-1634116526811.png%22%20alt%3D%22lornaschmidt_0-1634116526811.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2841129%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Regular Visitor

I'm involved in two distinct organisations and we are both experiencing issues where we get an error message when trying to access files in the Teams Desktop App within the two different VDI environments (Citrix and Horizon).

We receive the message 'f.a is not a constructor'.

Anyone have a resolution or know why both organisations are experiencing this? 

lornaschmidt_0-1634116526811.png

 

1 Reply

@lornaschmid 

 

I don't have a solution for your problem but I just had the same error an a laptop in our company. Here is where I got rid of it:

 

First, I renamed the folder %appdata%\roaming\microsoft\teams - same error, the files were not visible and  "f. a. is not a constructor".

 

The next thing was to rename all Teams-related folders in %appdata%\local and %appdata%\roaming\microsoft and run the Teams-Installer again (with user priviledges, no admin-rights).

 

This did the trick, the files were visible agin and the error is gone.

 

Maybe this helps...

mhacker