Outlook 365 app error 1001 on RDS environment ( FSLogix)

Anonymous
2023-07-07T08:25:49+00:00

Hello,

We encounter an issue with M365 apps (Outlook, Work, Excel) on a specific environment ( Remote Desktop Service)

Sometime, when an user open his application (Outlook for instance) on a RDS, an authentification pop and ask for credentials. If the user enter his credentials, he encounter a 1001 error.

« We encountered an issue [1001] »

https://learn-attachment.microsoft.com/api/attachments/5a947921-955a-4688-ad93-acc305bf77c6?platform=QnA

We already try some step to resolve the issue that help in some case but not all the case, and not defintely for a same user ( Issue occur again) :

  • Clear folder C:\Users*yourusername*\AppData\Local\Microsoft\OneAuth and  C:\Users*yourusername*\AppData\Local\Microsoft\IdentityCache
  • Move the user from 1 TSE server to an other TSE)e
  • Clear FSlogix User profil ( The specific one link to FSLogix Office 365 Container technology )

The main issue is that the error can occur again few day laterfor the same user.

We also generate some log from M365 apps client during the signin process with this link to help : https://learn.microsoft.com/en-us/office/troubleshoot/diagnostic-logs/how-to-enable-office-365-proplus-uls-logging

In the log I find the reference to the 1001 error but the log is a bit complex to understand or analyse.

0xa3e4	Microsoft Outlook	Identity Authentication Client	48cmb	Monitorable	OneAuth log {"Message": "[MSAL:0004]\tERROR  \tErrorInternalImpl:134\tCreated an error: 58tm1, StatusInternal::Unexpected, InternalEvent::None, Error Code 2147942403, Context '(pii)'", "IsError": true}	

07/07/2023 09:04:21.440	OUTLOOK (0x8b30)	0xa3e4	Microsoft Outlook	Identity Authentication Client	48cmb	Monitorable	OneAuth log {"Message": "[OneAuth:Error:58tm1:db6d7d6e-a557-4465-a968-a874c5e456e5] (Code:1001) An unexpected error occurred.", "IsError": true}	

07/07/2023 09:04:21.440	OUTLOOK (0x8b30)	0xa3e4	Microsoft Outlook	Identity Authentication Client	48cmb	Monitorable	OneAuth log {"Message": "[OneAuth:Error:9vdpp:db6d7d6e-a557-4465-a968-a874c5e456e5] Unexpected error code: 1001", "IsError": true}	

Environment :

  • Microsoft FSLogix version : 2.9.7654.46150
  • Office version : version 2305 build 16501.20228
  • OS version : Windows Server 2019 Standard 1809 build 17763.4499
Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

278 answers

Sort by: Most helpful
  1. Anonymous
    2023-10-30T13:41:16+00:00

    Work-around for me

    Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity. You can type this path in the search bar also.

    Here 16.0, is for Outlook version 2016 if you are using the previous version of Outlook you may change it's value.

    **Note:**for Outlook 2013, 15.0 will be used in place of 16.0

    Here you have to create 1 new Key. 

    • Create a new DWORD named "DisableAADWAM" and give it a value 1

    We did start to apply this reg key in June when the problems started for us. Unfortunately the same problem re-occurred after a few days so we stopped applying it. In fact now we actually remove the reg key if it exists whilst we're fixing the problem for a user.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-10-30T12:47:15+00:00

    Work-around for me

    Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity. You can type this path in the search bar also.

    Here 16.0, is for Outlook version 2016 if you are using the previous version of Outlook you may change it's value.

    **Note:**for Outlook 2013, 15.0 will be used in place of 16.0

    Here you have to create 1 new Key. 

    • Create a new DWORD named "DisableAADWAM" and give it a value 1

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-10-25T14:11:09+00:00

    Hello,

    We i logged in with my test user on the Remote Desktop Session Host. I started PowerShell as admin and executed: Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown.

    After that i have still the 1001 errors when logging in to Word/Excel

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-10-25T07:39:46+00:00

    Hi all,

    Microsoft officially acknowledges this issue since yesterday.

    "Some of the scenarios that receive the error Something went wrong [1001] are related to security software causing impact on the WAM plug-in (AAD.BrokerPlugin). "

    https://support.microsoft.com/en-gb/office/error-something-went-wrong-1001-signing-in-to-microsoft-365-desktop-applications-6f63238d-d83c-437c-a929-de72fe819793

    Finally! Took them long enough.

    Interestingly they don't mention RDS environments/user profile disks/FSLogix.

    They also encourage those experiencing the problem to open a support ticket within the portal.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-10-12T20:54:21+00:00

    Hi,

    Experiencing same issue here with a new RDS farm...

    12x RDSH 2022

    FSLOGIX 2.9.8440.42104 with RoamIdentity=1

    OFFICE 16.0.14332.20461

    No ODFC container and No outlook cache.

    Issue affects many users with 1001 error and outlook crashing past 24hours. Temporary workaround is to rename/remove this file : C:\users<yourusername>\appdata\local\packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy and then login back again.

    I'm afraid to see so many reports with no fix solution yet provided by Microsoft Teams ! Don't know what to do here.

    Thanks for precious help

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments