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-26T15:11:36+00:00
Just to be sure, with the very last version of FSLogix (which has the issue)
- Did you have updated adml/admx files ?
- Did you have enabled the following parameter : Roam Identity
Regards,
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-26T17:15:53+00:00
Just to be sure, with the very last version of FSLogix (which has the issue)

Did you have updated adml/admx files ?

Did you have enabled the following parameter : Roam Identity

Regards,
- Adml and admx files were updated not exactly with the latest but the latest ones from sometime in August (don’t know exact version).
- roamidentity was enabled with value 1.
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-26T18:32:12+00:00

We are also recently getting this same issue with same error 1001.

Here are some facts about our issue :

Rebooting the whole server currently was fixing the issue for some times.

This issue was affecting sometimes many users sometimes wholes users.

For Outlook we also experienced this message :

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed.

While troubleshooting and since this is for an RDS in production and reboot every time isn't a very good definitive solution I still at least also found what it could be related in our environment and what was also working as an workaround:

In powershell we runned :

Get-AppxPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

This force to register all modern application to register using the system xml manifest file.

This said, It is probably not required to register whole list of all Application, I just didn't had chance to find those who are directly related to our issue but at least this workaround for us isn't to delete complete profil or reboot a whole server.

We'll probably open a case with Microsoft directly for this also, since this issue seems not to just be related to our environment.

FYI: here we are also using RDS 2019 server with O365 and User profil Disk.

Thanks,
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-27T08:38:41+00:00

Thanks everyone for posting!

Our experience is that WAM has never worked in a RDS 2019 1809 environment.

That is why we had to revert to ADAL authentication instead.

ADAL works fine and no authentication problems! To get this working and Outlook to understand, a few registry keys were needed. No big deal

We have a customer who does NOT suffer from the 1001 error.

Also the added ADAL registry values work fine for this customer.

Environment is:

Server 2019 1809

FSlogix 2.9.8440.42104 (Roam Identity = 1)

Office 2301 (build 16026.20238) (autoupdate = FALSE)
STABLE ENVIRONMENT

ADAL registry keys have also been implemented for another customer who suffers a lot from the 1001 errors.
We notice WAM overpowers the ADAL registry keys and causes authentication problems.
I say this because the ADAL registry key was present but WAM authentication came up. Which is weird.

Environment is:

Server 2019 1809

FSlogix 2.9.8440.42104 (Roam Identity = 1)

Office 2308 (latest build) (autoupdate = TRUE)
UNSTABLE ENVIRONMENT (1001 errors)

We downgraded this customer yesterday evening to the following Office version: Current channel Version, 2301 (Build 16026.20200)

After the downgrade we received the familiar ADAL login screens again.

It is noticeable that WAM now not ADAL predominates in this older Office version.

We did have a storm of re-authentication via ADAL this morning (which makes sense) but we expect everything to be stable now.
This is because our experience is that ADAL has always been stable and WAM not.

It should also be noted that from March 2023 we had some employees/customers who sometimes had the 1001 error, but until now it has become worse.

That is why we have downgraded from a version before March this year.

I will keep you all informed whether this downgraded version remains stable.

Regards.
Was this answer helpful?

0 comments No comments
Anonymous

2023-09-27T08:50:30+00:00

I've seen a few people mention the Roam Identity=1 but can you clarify how to set this as i can't see any option in the GPO for FSLogix and i can't seem to find a post to say what the exact registry key needed is to be able to set this ?

Just as a note also that we've NOT downgraded but we've had NO issues at all today ad there has been an Office 365 update on one of our RDS servers (we are running 2022 as well)

Thanks
Was this answer helpful?

0 comments No comments