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-25T11:22:32+00:00

Our users get the same 1001 error massage when they are login on the RDS environment, We are using Windows Server 2019 with Office 2019 2308 on the dedicated Session Hosts, it was just a couple users at first when we where stil on 2307 an where abel to fix the problem by logging off and in again but it seems to be 10 times worse sinds the system did updates. If someone has a solution to fix the issue please let me know.

We have 8 Session Host servers with Windows Server 2019 1809 And using Office 2019 version 2308.
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-25T09:37:13+00:00

Just as a note that ours WAS only on our RDS environment but this morning I've had the 1001 error on 2 laptops as well so it's getting worse for us.
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-25T09:30:57+00:00

We've had at least two logged so far this morning. That's an increase for us. It does see to be getting more frequent even in the last few weeks. I am attempting to raise a MS support call but I don't have high hopes. Maybe I will be assigned a dedicated/expert tech
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-25T09:23:30+00:00

Today we had an explosion of 1001 error's and password entries.

What nonsense! Anyone else had this too?

It's driving us nuts!
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-21T09:21:10+00:00

Just to add ours to this but we have the same issue....always random people however we find simply bouncing them onto another server fixes the issue (albeit temporarily) so I would agree that it's some sort of authentication issue however I tested the same environment using a Volume Licence install of office (instead of the click to run) and have had no issues in testing however we don't have a paid for Volume Licence to continue using this version but having worked at MSP's for 20 years I've found a lot of these types of issues (including one's we've had recently whereby it shows random users as not licenced when they are) is down to the Office click to run program and Microsoft have never fixed it so we've always put the Volume Licence copy of office on customers servers and never get these types of issues but I work for internal I.T now so we don't have a licence to use full time.

Unfortunately (like I suspect a lot of you) we can't keep a user "not working for a day or two" while we do some background digging on it as our staff need to be able to work so although bouncing them fixes the issue when then in fact remove all evidence of the issue for troubleshooting.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments