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-10-11T13:04:20+00:00

Do you mind posting what your OS and Office version you were using? Did the above changes resolve things for you?

Also, can you post an example of your exclusions for FSLogix xml? I'm struggling to get mine going and it would be helpful if there was a working example available. Much appreciated!
Was this answer helpful?

0 comments No comments
Anonymous

2023-10-10T17:51:29+00:00

https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/administration/disabling-adal-wam-not-recommended There is this MS article from March 3/16/2023 stating that starting with build 16.0.7967 office client apps, MS changed the default Office auth type to Web Account Manager (WAM). So for any of you that found that forcing to ADAL, or reverting to an older version than March.. That seems to align.

I note in many of the posts, resetting profiles, deleting certain office or auth related folders would clear the error at least temporarily.

I'll note that we are using Citrix UPM(User profile management) which is a streamed/roaming user profile service... The behavior is identical, and arrived on day one of our Sept patched image (both office and windows Sept patches). Not really any reports prior to that.

I provided our team this blog and the registry entries that some of you kindly posted as workarounds (forcing ADAL), we'll see how that goes.

For MS's part, a rewrite/fix/re-think/self-healing of files written to profile (with minimal needed user action) is required. Even if "something went wrong (1001)" then add 'would you like to log out and try again" which would/could clear the profile files and re-create them, instead of everyone here supporting customers having to do it, would be a good start. :-)
Was this answer helpful?

0 comments No comments
Anonymous

2023-10-10T16:22:58+00:00
Thank you both for your contributions our troubleshooting!

Update from my end...
- Windows Server 2019 Standard
- 4x RDSHs
- FSLogix 2.9.8612.60056
- Microsoft 365 Apps for Business (x86) 16.0.16026.20200
I added the BlockAADWorkplaceJoin=1 reg key and it completely broke Office logins for me. I would click "Sign In" at the top of Word and it would just do nothing. When I tried in Outlook, I'd load my cached profile, and at the bottom, it would say "Needs password". I clicked it and it never prompts with a login screen. I removed to reg key and it's back to normal.

I'm curious, what version of Office are you guys using? I wonder if me not being on the latest (or simply a newer) version of Office is the reason mind broke completely. There's people using my servers right now but after a reboot tonight and blocking new connections, tomorrow I'll see if Office updates fix things.
Was this answer helpful?

0 comments No comments
Anonymous

2023-10-09T11:26:42+00:00

Great Post above

I did add the registry key to block WPJ back in April. However on checking Entra there are still the stale devices for the non-persistant RDS Servers - 47 of them. We'll take the above into consideration when planning next actions
Was this answer helpful?

0 comments No comments
Anonymous

2023-10-06T14:26:36+00:00

We've gone from about 5 a day to none in the last week as well and we've not done anything to change Office 365
Was this answer helpful?

0 comments No comments