Share via

Teams error code 8009000b on HyperV RDS

Nico Khan-Hayes 1 Reputation point
2021-01-26T11:09:58.217+00:00

We have a client on a Hyper-V Windows 2019 RDS. The Host is a Dell PowerEdge T430.

We've deployed Teams using an executable installer (I've heard trying .MSI might be the way to go?) however this setup had seemed to have worked just fine before retiring an old Windows RDS 2012 server and replacing using the Sysprep tool to generalise the install using the old RDS .VHDx.

End-users connected to this particular RDS are now experiencing an error which does not happen on immediate logon but after a few hours of use at most and is singular to the specified RDS and does not happen on the secondary RDS. Noticeably this breaks the presence function of Teams and asks them to restart the client which ends in a continuous loop.

60612-2021-01-22-13-54-33-window.png

A temporary fix for this seems to be by deleting the roaming APPDATA for Teams from the following location:

C:\Users\XXXXX\AppData\Roaming\Microsoft\Teams

According to the error log extracted from one of the affected VDs at the time of the issue, there's no web account present, the APP starts a token for async, fails to open registry items then fails due to UPN missing.

Your assistance in the matter is greatly appreciated.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,491 questions
Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,201 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,561 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,283 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. JimmyYang-MSFT 49,286 Reputation points Microsoft Vendor
    2021-01-27T03:04:55.653+00:00

    Hi @Nico Khan-Hayes ,

    Does this issue persist all the time?

    To exclude the account itself, you could try to sign in Teams web client(https://teams.microsoft.com) in InPrivate mode and check the result.

    Then, perform a clean boot to exclude whether a background program is interfering with Teams.

    Moreover, make sure Teams client is the latest version. If there is any update requirement on the machine, please install the package in time.

    Some customers solved this issue by closing Teams and renaming or deleting this file:

    %appdata%\Microsoft\Teams\desktop-config.json

    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Nico Khan-Hayes 1 Reputation point
    2021-03-01T15:39:14.973+00:00

    @JimmyYang-MSFT

    Thank you for your response.

    Yes, we've redeployed teams on both Terminal Servers using the .MSI deployment method.

    Since then the issue had unfortunately returned, however, the apparent remedy was by accessing the 'update.exe' properties in the local Teams %APPDATA%, compatibility tab and enabling compatibility mode under Windows 8 (See below image), applying and then executing the executable updater.

    Location: C:\Users\XYZ\AppData\Local\Microsoft\Teams

    73057-compatibilityw8teams.png

    This has seemingly since resolved the issues for our client, however, should you have any further suggestions please do let me know.

    0 comments