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-09-08T13:11:23+00:00

    thanks for your quick reply by the way!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-09-08T13:06:43+00:00

    Yes RDS with

    • Microsoft FSLogix version : 2.9.7654.46150
    • Office version : version 2305 build 16501.20228
    • OS version : Windows Server 2019 Standard 1809 build 17763.4499

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-09-08T12:58:39+00:00

    RDS en server 2019 indeed

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-09-08T12:36:33+00:00

    Hello,

    No we still have the issue for some user occasionally.

    Our best solution is to delete this folder :

    • C:\users<yourusername>\appdata\local\packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

    But some time we need to do the others steps describe in this link O365 - Outlook Logon Error: Something Went Wrong 1001 | Matrix 7

    @ARGUAIROLLES Florian Mustafa Nazir

    What environments do you have? Server 2019 and RDS?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-09-08T11:31:23+00:00

    I face the same issue with different users. could you solve the problem ? if yes then can you please let me know what you did? i delet in app data identity cashe and oneauth as well and do the same things you described at the moment but for some users it is 21 time in 2 weeks that we have to do this and it is getting now impossible for our users to work smoothly.

    in advance thanks

    Was this answer helpful?

    0 comments No comments