Teams cannot log in at all, Error Code: 2147942402

Yasir Luo 0 Reputation points
2024-07-17T02:35:09.12+00:00

7635136506e3ac3314b4bca75fd32d2

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,607 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. LiweiTian-MSFT 16,845 Reputation points Microsoft Vendor
    2024-07-17T07:09:44.6266667+00:00

    Hi @Yasir Luo

    When users attempt to sign into Microsoft 365 desktop applications, they receive an error message: Error: Something went wrong. [1001] 

    In the first scenario the error "Something went wrong [1001]" is caused by security software impacting the WAM plug-in (AAD.BrokerPlugin). 

    Please see this article for more details about how to mitigate: 

    Can't sign in to Microsoft 365 desktop applications

    To provide temporary relief, these steps may help:

    1.Rebooting the device often helps to mitigate the issue.

    2.Run the commandlets below in user mode PowerShell to repair WAM. For more context see the article, Authentication fails in Microsoft 365 services.

    Add-AppxPackage -Register  "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown    Add-AppxPackage -Register  "$env:windir\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

    In the second scenario the error "Something went wrong [1001]" is caused by user profile management issues. Please see this article for more details about how to mitigate: Device identity and desktop virtualization

    In this category of issues, we find that on both VDI and physical devices the user profile data is being roamed and that can cause identity and authentication data components to be in a bad state. Make sure to follow the guidance in the article above to carefully review if user profile management practices could be causing the issue. This section is pulled from that article to emphasize its importance: 

    Roaming any data under the path %localappdata% is not supported. If you choose to move content under %localappdata%, make sure that the content of the following folders and registry keys never leaves the device under any condition. For example: Profile migration tools must skip the following folders and keys:

    User's image


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    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.