Outlook 365 app error 1001 on RDS environment ( FSLogix)

Anonymous

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

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

278 answers

Anonymous

2023-09-15T06:32:10+00:00

We have this issue with 2022 as well.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-09-14T14:19:19+00:00

We have a case open with both Citrix and Microsoft. Citrix let us know it's an issue with Windows Server 2019.

Citrix shared the following technical article Password Field Not Displayed for published Apps in Windows Server 2019 (citrix.com)

with us to try. We're going to test the listed recommendations.

We're running Citrix LTSR 2203 CU3 with Citrix Profile Manager configured with Full Containers on Windows Server 2019. I know many of you are using RDP, but thought I'd share the information if it may help.

Is anyone seeing this on Windows Server 2022?

If we're not able to resolve the issue, we may move to Server 2022.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-09-14T11:04:16+00:00

@Stephan Stoke

There isn't a permanent fix. Like you we try various things and we can get Outlook working again, but for some users the problem returns.

Microsoft have not acknowledged the problem as yet. It will be great if/when they do acknowledge the issue as it would hopefully lead to a resolution.

For us, the problem seemed to start around June time this year, but based on the various forum posts I've read it seems to have been around March this year when it started.

The environmental consistencies between those that are having the problem are Windows Server 2019 Remote Desktop Services, multiple session hosts, user profile disks/FSLogix, Microsoft 365 apps.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-09-14T08:01:03+00:00

@Stephan Stoke

Do you have multiple RDS session hosts as well?

It occurs pretty randomly for us. Out of 70 users, 21 have had the problem, and out of those 21, only 10 have had it more than once. We do have 4 users that seem to have the problem more often.

We use User Profile Disks as opposed to FSLogix.

The steps on this site usually get Outlook working again, although it's not a permanent fix. What we have had some luck with this week though for users that have the problem is closing all Microsoft apps, sign out of Edge, set Internet Explorer as the default web browser, then open Outlook and go through the authentication process. Check if Outlook has reconnected and then if it has, set Edge back as the default browser.

We're thinking that perhaps Edge has something to do with the problem.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-09-06T15:27:48+00:00

We've been having the same problems since around June time, although from what I've seen on other forum posts the issues seemed to begin in March.

Our infrastructure is Windows Server 2019 Remote Desktop Services, multiple session hosts, user profile disks.

Out of 70 users 17 have had the problem, with three of those users having it multiple times.

We need Microsoft to acknowledge this issue and sort out a fix for it.

When a user has the problem we follow the steps on this page to get Outlook working again: O365 - Outlook Logon Error: Something Went Wrong 1001 | Matrix 7. I should add that this doesn't fix it for good - sometimes it fixes it for a few days, sometimes it fixes it for weeks, and other times it only fixes it for a few hours.

It's also being discussed on this Reddit post as well: https://www.reddit.com/r/Outlook/comments/14pdh3r/anyone_else_having_these_1001_issues_with_outlook/

Completely baffling!
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments