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: Most helpful
  1. Anonymous
    2023-10-12T13:20:34+00:00

    Hi AFABIA,

    For now, I have not changed anything (the advised MS workarounds) because we had less customer complaints in the past few days. I suppose Microsoft fixed the issue in the backbone or in the Microsoft 365 Apps (security) update of October 10?

    Only one customer seems to keep experiencing this issue.

    I'll keep you posted.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-10-12T13:19:32+00:00

    Hi Steven,

    I created the MS support ticket regarding one of our (multiple) customers who are experiencing this issue.

    The customer's environment:
    RDS: 2 x Windows Server 2019 Version 1809 (OS Build 17763.4851)
    Microsoft FSLogix Apps: 2.9.7979.62170
    Microsoft 365 Apps for enterprise - 16.0.16731.20234

    For now, I have not changed anything (the advised MS workarounds) because we had less customer complaints in the past few days. I suppose Microsoft fixed the issue in the backbone or in the Microsoft 365 Apps (security) update of October 10?

    Only one customer seems to keep experiencing this issue.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-10-12T07:13:13+00:00

    Hello,

    no new cases since 02 October.

    We just pass the M365 updates

    fingers crossed

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-10-11T15:43:23+00:00

    Just a quick update from my side - we've not had any reports of the issue occuring for almost two weeks now. We've not made any changes whatsoever.

    So if anything, I presume Microsoft have changed something their side.

    Has anyone else noticed a drop in reports of the problem, or not had any reports at all for a week or so?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-10-11T14:49:05+00:00

    Thank you Mathieu! All the registry keys you've posted have been set in our client's server with the exception of "NoDomainUser". I will add that to the GPO I used to deploy the first two registry keys. I will also go through your other steps. Please do let us know as well how it goes as per your testing.

    Was this answer helpful?

    0 comments No comments