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

2024-12-02T15:16:44+00:00

"One of the reasons, from the point of view of Server 2019 and Server 2022, is that M365 apps won't be supported on these operating systems from October next year (Server 2019) and the year after (Server 2022)."

I have not heard this yet... Is there a KB article that describes this, or where are you seeing this? I would like to look more at the official Microsoft documentation on this so I can better prepare.

Thank you!

Full details here: Windows Server end of support and Microsoft 365 Apps - Microsoft 365 Apps | Microsoft Learn

I've been surprised generally from when they first announced this a couple of years ago how few people seem to know about it.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-12-02T13:49:36+00:00

"One of the reasons, from the point of view of Server 2019 and Server 2022, is that M365 apps won't be supported on these operating systems from October next year (Server 2019) and the year after (Server 2022)."

I have not heard this yet... Is there a KB article that describes this, or where are you seeing this? I would like to look more at the official Microsoft documentation on this so I can better prepare.

Thank you!
Was this answer helpful?

0 comments No comments
Anonymous

2024-12-02T09:24:14+00:00

Hi!

We also have this "working" by adding the following:
Add the following to this:

<?xml version="1.0" encoding="UTF-8"?>

<FrxProfileFolderRedirection ExcludeCommonFolders="0">

<Exclude Copy="0">AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy</Exclude>

<Exclude Copy="0">AppData\Local\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy</Exclude>

<Exclude Copy="0">AppData\Local\Microsoft\TokenBroker</Exclude>

</FrxProfileFolderRedirection>

Problem now is that they have to login everyday since it does not remember. Do anyone have any solution for that? I have enabled "Roam Identity" in GPO.
Was this answer helpful?

0 comments No comments
Anonymous

2024-11-28T13:48:03+00:00

Is this fix still working for you?

May ask what exact build of office you were able to get this working with?
Was this answer helpful?

0 comments No comments
Anonymous

2024-11-28T12:28:56+00:00

Thank you for the suggestion. Unfortunately, our issue is related to the publishing of Excel and Word as published apps in RDS. Our issue matches that of Sander_d-_-b.

This seems to be a well known issue both Citrix and Parallels have attempted to provide workarounds. Citrix has offered shellbridge and Parallels has offered the -runexplorer option for use when publishing O365 apps. It's seems that these workarounds are now also broken.

My question still remains.

Is Microsoft working on a fix for this maddening issue?

The workaround we have in place is to use Office build 2201 with WAM disabled. The trouble is that this is a VERY old version of Office. This does work consistently. I have shown this to Microsoft support. As soon as I upgrade Office we are no longer able to authenticate because the password window cannot appear when the application is published.

Does anybody know if Microsoft is doing anything about this bug?

Personally I don't think Microsoft are that bothered about resolving the issues.

One of the reasons, from the point of view of Server 2019 and Server 2022, is that M365 apps won't be supported on these operating systems from October next year (Server 2019) and the year after (Server 2022).

I also think that the problems have been going on for some time now and if they were going to resolve them they would have done already.
Was this answer helpful?

0 comments No comments