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-11-09T18:10:36+00:00

    We had an issue in our Citrix Xenapp virtual Desktops environment, with Outlook and other O365 Office applications. Where it would prompt for login, followed by some other errors/prompts. Also, there was a yellow banner in Outlook “RESTART REQUIRED Restart Office to apply changes to your privacy settings”. This would happen every time after a fresh Citrix login, subsequently opening Outlook worked fine, but the issue reappeared after a fresh Citrix login again.
    I found that including the folder AppData\Local\Microsoft\OneAuth to sync with the roaming profile, resolved the issue.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-11-08T22:05:24+00:00

    Though it may work, the reason I didn't push this is for security and also to find a permanent fix. Appreciate the suggestion though!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-11-08T22:01:04+00:00

    We are now investigating a solution that involves blocking the 'WorkplaceJoined' option by adding the following registry keys:

    • HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin
      • DWORD: BlockAADWorkplaceJoin Value: 1
    • HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin
      • DWORD: AutoWorkplaceJoin Value: 0

    I have deployed those registry keys 2 months ago thinking it would help resolve the issue but it still persisted.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-11-08T21:22:50+00:00

    Hi,

    Exactly same actions and workarounds applied here. The registry keys seem to work as workaround instead of renaming/deleting Microsoft.AAD.BrokerPlugin folder located in profile user disk. This fix was recently applied for new users at first logon, waiting to see if this could defintively resolve this issue related to WAM authentication...

    I'll posting my results soon !

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-11-08T13:42:08+00:00

    On our end with 4 AVD session hosts we turned off RoamIdentity setting for FSlogix. This seems to have the opposite effect in our environment, with it turned off we haven't heard a peep from any user having to re authenticate their primary or secondary exchange account when switching between session hosts. Going on two weeks now with no issues as it was at minimum issues every other day.

    Was this answer helpful?

    0 comments No comments