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: Newest
  1. Anonymous
    2024-09-16T20:29:10+00:00

    Carlos do you mean the account folder that appears in C:\users on the remote server the user is currently logged into it?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-09-16T18:24:55+00:00

    Hello, the only solución that has worked to me is giving read-only permissions to the user in the "account folder"

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-09-16T17:04:54+00:00

    Thank you Lars for posting that incredibly long summary. We've tried a variety of solutions that have been presented this long, long, long post and we get only temporary relief. Seriously considering moving users to individual TS servers and removing roaming profiles. My users are not happy.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-08-29T19:52:48+00:00

    So far, on Azure Virtual Desktop, the problem is fixed without doing any changes to the users LocalCache and Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

    #We just Restart WAM service

    Stop-Service -Name "TokenBroker"

    Start-Service -Name "TokenBroker"

    Then, everything is back as usual.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-08-12T14:49:48+00:00

    We have encountered this issue with several clients who use multiple terminal servers in a cluster and utilize FSlogix or UPD.

    After extensive research, it seems that the registration of Office is not proceeding correctly.

    Ultimately, implementing the solution below resolved the issue, and no further problems were reported.

    Solution:

    Ensure the user has a "Home Folder" (Home Share variable).

    Create a GPO on the terminal servers:

    Logon script:

    robocopy "%homeshare%\ac" "%userprofile%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\ac" /MIR

    Logoff script:

    robocopy "%userprofile%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\ac" "%homeshare%\ac" /MIR /R:0 /W:0

    Login as the user and delete the folder: Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy in %userprofile%\AppData\Local\Packages\

    Logoff an login again, register Office.

    Occasionally, we still encounter someone with a 1001 error messages; in such cases, deleting the %homeshare%\ac directory and the %userprofile%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy directory is the solution, although the user needs to reactivae Office.

    Was this answer helpful?

    0 comments No comments