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-18T08:20:45+00:00

We also had three different cases open between April and now.

However, Microsoft technicians were unable to solve the problem.

We use

Windows 2019 1809.17763.4851

Office 2308 16731.20234.

FSLogix

At first I suspected there was a problem with our infrastructure. However, replacing the firewall and changing the virus protection didn't help.

We also had problems with Edge login. However, that could be solved.

I suspect there are problems with the accessibility of the Exchange servers (information stores) in Office 365. Overload
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-18T09:33:58+00:00

We see that when we clean up the profile (vhdx) for a temp fix and reconfig the Outlook profiles the WAM authentication is forced over ADAL while the ADAL registry keys are in place to use ADAL. Also, this only seems to happen if multiple mailboxes have been added in addition to the primary mailbox (not shared mailboxes but additional "user" mailboxes).
Does anyone else experience this too?
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-18T09:44:51+00:00

Hello Stephan,

For us the problem is with users with one mailbox as well as with multiple mailboxes. As with users with a personal mailbox and a shared mailbox.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-09-18T10:20:21+00:00

Ivo Schoemaker [Bolk Transport]

We also remove the AAD Broker Plugin folder as a first stage for anyone that reports the problem. Sometimes this works and sometimes it doesn't and we have to go through the rest of the steps. We've even recreated the RDS user profiles for a number of users only for them to have the problem again two days later.

Wolfgang Burkhard1

I too suspected it was a problem with our infrastructure, but once we started seeing more forum threads describing the same behaviour with the same environment, I came to the conclusion that it was a problem either at Microsoft's side, or a problem they had introuced by way of a Windows/Office update.

I am in contact with someone that works for an MSP and he has a number of customers with the same problem.

It also seems that in the last week or so the problem is getting worse/more common.

Stephan Stoke

For us the problem is with users that just have the one mailbox (no users have more than one mailbox).
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-09-18T14:58:50+00:00
Hi Stephan, I have an update with our case.

We were able to resolve our 1001 error issue by adding the shellbridge registry from the following Citrix article. https://support.citrix.com/article/CTX267071/ However, this is a fix for Citrix Virtual Apps so I don't think it will help with RDS deployments.

The required hotfix was already pushed from a previous Microsoft roll-up so we didn't need to apply it separately before applying the following registry "Shellbridge" hack:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Citrix Virtual Desktop Agent
Name: Shellbridge
Type: REG_DWORD
Value: 1

This resolved the 1001 error, but now introduces a new problem for us to troubleshoot for our users when logging off.
Processes stay open and prevent a clean logout after closing the last application.

The article has a work-around section I'm going to be testing next to see if I can resolve the 1001 error without having to apply the shellbridge registry hack.
```
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments