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-02-15T09:02:43+00:00

Hi All,

We have been experiencing the 1001 issue and other Office activation issues with multiple customers over the last six-twelve months. similar infrastructure Windows 2019 RDS, Office 365 Apps for Enterprise and UPD.

since December\January with one customer in particularly that have 4 RDS Farms on different domains, total about 16 RDSH approximately 150 users was being impacted very heavily. This was impacting users randomly and some users more than others. Then suddenly Friday lunchtime GMT the Issues just stopped.

Has anyone else that have been experiencing these issue found that they just resolved on Friday? As of today the customer is having no reports of the 1001 issue.

We have tried various fixes on these forums on users and non that resolved permanently. Server wide fixes such as disabling workplacejoin have only been tested on test servers. No changes had been made when the problem suddenly resolved.

Hi Lee GTS,

We are exactly in the same situation as you, multiple customers, RDS 2019 with UPD, Office 365 and 1001 error + multiple passwords prompts over the last six months.

May I ask you which Windows Server build/CU and which Office version are currently installed on your infrastructure ?

We still encounter the issue today and we hope that like you, the 1001 will miraculously disappear with the same versions as you.

Thank you in advance for your help !
Was this answer helpful?

0 comments No comments
Anonymous

2024-02-12T14:22:30+00:00

Hi All,

We have been experiencing the 1001 issue and other Office activation issues with multiple customers over the last six-twelve months. similar infrastructure Windows 2019 RDS, Office 365 Apps for Enterprise and UPD.

since December\January with one customer in particularly that have 4 RDS Farms on different domains, total about 16 RDSH approximately 150 users was being impacted very heavily. This was impacting users randomly and some users more than others. Then suddenly Friday lunchtime GMT the Issues just stopped.

Has anyone else that have been experiencing these issue found that they just resolved on Friday? As of today the customer is having no reports of the 1001 issue.

We have tried various fixes on these forums on users and non that resolved permanently. Server wide fixes such as disabling workplacejoin have only been tested on test servers. No changes had been made when the problem suddenly resolved.
Was this answer helpful?

0 comments No comments
Anonymous

2024-02-07T15:17:16+00:00

Hi there,

These were based on all the Microsoft recommendations our team found when looking into this issue. These are the configs/registry keys we've deployed that appear to have worked together with Microsoft's latest version of O365 apps.

This might not work to every scenario but so far, even if users are prompted with passwords on O365, they're no longer getting error 1001.
Was this answer helpful?

0 comments No comments
Anonymous

2024-02-07T10:46:21+00:00
Hi everyone!

I've been following this thread for a while and so far, our client's environment has been stable since end of November. Here are the things to note so far:

Deploy these registry keys:
[HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin]

"BlockAADWorkplaceJoin"=dword:00000001

[HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin]

"autoWorkplaceJoin"=dword:00000000"

**Delete these registry keys, if possible, Microsoft doesn't recommend using these anymore:**Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity

EnableADAL

DisableAADWAM

DisableADALatopWAMOverride

**If you're using FSLogix, make sure to enable this policy through main GPO:**RoamIdentity

Lastly, if users did register the RDS to Azure AD, might have to follow these steps:- Download (WPJCleanup.zip) https://download.microsoft.com/download/8/e/f/8ef13ae0-6aa8-48a2-8697-5b1711134730/WPJCleanUp.zip

Extract and run the .cmd file

Confirm if the WorkPlaceJoined indicates "NO"

Reenter credentials to outlook (might have to log out and log back in to the RDS)

Let me know if that helps or not. We're looking to deploy this to other clients since it appears to be working fine but I hope it helps with your case.
How have this developed for you ?

We are in the same situation but not using FsLogix

We are using RDS 2019 with Profiledisks and getting 1001 error on several users -But not all.
Was this answer helpful?

0 comments No comments
Anonymous

2024-02-01T09:51:56+00:00

So the Roam Identity is in the Profile and not in the ODFC and this seems to have fixed it for us (again I'm only going on the fact it stopped the problems straight away and we've had no more) and we haven't needed to delete ANY profile off at all so has anyone else fixed this but still had the Roam Identity enabled ?

It does seem to be a slightly different fix for different scenarios.

Also have we seen this happen to ANY rds environment that doesn't use profiles disks (either FSLOGIX or UPD) or a broker ?

I'd be interested to find that out as again we've had no problems at all with the same users logging onto our other 2 RDS servers locally (i.e normal local profiles stored on the RDS servers)

Thanks
Was this answer helpful?

0 comments No comments