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
    2023-11-03T07:48:42+00:00

    A reminder of our infra, 4 RDS, 1 Brocker, 1 Filer and Fslogix.

    We noticed that when users connected to the same server, we had fewer 1001 problems.

    Let me explain: 1 user who authenticates correctly on server A on day 1, as long as he stays on this server he doesn't get the 1001 error, but when he switches to another server he's likely to be blocked by the 1001 error.

    As a result, when he reconnects to his initial server, in the worst case he'll have to enter a password to re-authenticate. It's a bit of a hassle, but in many cases it avoids deleting the profile.

    I hope this helps

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-10-31T19:07:26+00:00

    Azure Virtual Desktop Windows 11 Enterprise Multi-Session Hosts Build 22621.2428 AzureAD/Entra Hybrid Joined

    FSLogix 2.9.8612.60056

    Office 365 Apps for Business Version 2309 16827.20166

    RoamIdentity - See Below

    Running into periodic, never consistent 1001 errors with users who have a second Exchange account configured in Outlook. Only the secondary account has the issues.

    We realized last week 2 of our 4 session hosts had RoamIdentity configured to be on and 2 were off. We turned it on across the board and after the weekend all secondary exchange accounts ran into 1001 errors, when up until now it's only been sporadic. Turned RoamIdentity off (0) and rebooted our session hosts and it's only been 1 day but no reported issues today. 1 day of course means nothing, we could go many days before, but wanted to add my 2 cents in here while I had a minute.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-10-31T14:14:22+00:00

    Windows Server 2019, Office version 16827.20166 (there is an update waiting to go on).

    We don't use FSLogix - standard user profile disks.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-10-31T14:00:30+00:00

    Hey! What's your FSLogix, Windows Server, and Microsoft versions?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-10-31T13:48:06+00:00

    7 reports of the issue today from 7 different people, including 4 who have never had the issue before.

    Was this answer helpful?

    0 comments No comments