Outlook 365 app error 1001 on RDS environment ( FSLogix)

Anonymous
2023-07-07T08:25:49+00:00

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
Outlook | Windows | Classic Outlook for Windows | For home

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 No comments

278 answers

Sort by: Oldest
  1. Anonymous
    2023-10-06T13:43:00+00:00

    Hi folks,

    Nice thread !

    We are actually facing the same problem (3 RDS, ~80 users) since months, look like it's even worse since a few weeks.

    After trying a lot of things which are all detailed in this thread, I gave a try in downgrading the Office version to 16.0.15601.20538 (february 2023).

    I keep the fingers crossed but since more than one week we don't get any call about this authentication problem.

    I'll keep you in touch.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-10-06T13:55:05+00:00

    Definitely seems from reading this thread, something happened in the March update that is causing this issue. I may also downgrade this weekend on one of my servers and see if the error occurs from that particular server. Anyone hear from Microsoft recently or has relayed this information?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-10-06T14:04:55+00:00

    Oddly we've not had any reports of the problem at all for the last 7 days. We've not made any changes in that time period.

    Up to 7 days ago we were getting at least 2 reports a day of the problem occurring.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-10-06T14:19:05+00:00

    I have a suspicion that at least a portion of this bug is server-side. Obviously, it has something to do with authentication messing up. Maybe Microsoft is tweaking things in the back end.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-10-06T14:21:12+00:00

    I've done two this morning

    Both were users that had previously reported it but other support team staff had just got them re-connected on a different server or it had gone away temporarily and they'd closed the tickets.

    I mounted their VHDX FSLogix disks and deleted the problematic folders listed in this thread. Even when re-connected to the same RD Server it connected first time after accepting privacy and logging in to 365. Don't know how long this will last for though

    My MS ticket when to the Azure team and the agent knocked it back saying it would need paid for support. Not convinced this will lead to a positive outcome and we'll be down £££'s but at least two customers are frequently bothered by this.

    We also haven't yet downgraded office due to vulnerability concerns and have the RoamIdentity = 1 for Fslogix 2.9.8440.42104

    Was this answer helpful?

    0 comments No comments