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-27T15:59:35+00:00

Thomas Praill

Downgrading our Office software on the session hosts wouldn't be something I'd be keen to do. The potential security issues is one thing, removing features/stuff that staff are used to etc. But we're currently only seeing 2 or 3 users a day reporting the problem (out of about 70 users) so we can manage that.
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-27T16:03:20+00:00

For now :) you will see in newt few days that you will have more and more users complaining about that.
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-27T16:14:48+00:00
Hey everyone,

I've been dealing with this issue for over 3 weeks now on an entirely new RDS deployment but think we may have "fixed" it. Here's my setup details, troubleshooting steps, and solution.

Setup

4x RDSHs running Windows Server 2019 Datacenter, 1x RDCB

Latest version of FSLogix (was 2.9.8612.60056 at the time)

Office 365 version of Office, x86, deployed via Office Deployment Tool (sharedcomputerlicensing=1)

Symptoms and Troubleshooting

Office would not remember people's credentials at random intervals. Some people were fine for a few days before asking again, others would need to enter their credentials every login.

Sometimes, when the user authenticates, they'd be greeted with "Something went wrong, Error 1001" message with no more helpful details. Closing the error and Office, then reopening, they were fine to continue working.

Easiest way to tell it wasn't working was to open Word or Excel > Account and see account had "Fix me" button to sign in again. Outlook would open most of the time even if Word/Excel said "Fix me" but would eventually stop opening until credentials were entered at some point.

Creating new FSLogix profiles for users would temporarily alleviate the issue for a few days but it would always come back.

Tried newer RoamingIdentity reg key for FSLogix but made no difference.

Tried Office 2019 VLSC instead of Office 365 Office but made no difference.

Users that did not use FSLogix were not affected by this issue.

Solution (Workaround until they fix it) SEE EDIT BELOW

We eventually found another client we support with the same exact setup that did not have the issue, noted their FSLogix version, and downgraded it on all our RDSHs, and the last 2 days, no one has reported being asked for credentials again. There's still time for it to mess up but so far, it's looking positive.

We downgraded to FSLogix version 2.9.8228.50276. This was our fix/workaround until Microsoft figures their stuff out.

Hope this helps!

EDIT: As of this morning, users started getting prompted for credentials again and worse, got stuck in Error 1001 loops when opening Outlook. I guess this didn't fix things...
Just wanted to update everyone that it seems downgrading FSLogix, though fixing the issue for 3 days, seemed to have no fixed it permanently. Users are getting stuck in Error 1001 loops now to the point they can't even open Outlook now. This is ridiculous...
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-28T08:41:55+00:00

Richard Castillon

Other than on Friday 15th September when we had a lot of reports about the problem we've averaged about 2-3 reports per day since the issues started for us in June.

There was something about Friday 15th September as it wasn't just us that experienced a lot of the issue reports - I spoke to a friend at an MSP and he mentioned it nearly wiped out his first line support team with calls from customers reporting the problem.
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-28T08:43:54+00:00

Steven Gerrish

Sure is getting ridiculous. I've been kind of hoping that with the increase in the number of people posting on here that they are having the problem that Microsoft might at some point take notice and do something about it.

We've been having the issue since June, but I believe for a lot of companies it started in March time.
Was this answer helpful?

0 comments No comments