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-11-08T13:36:27+00:00

    Same as Anthony Manniello above we also have to run the same commands to clear out the build up of firewall rules. Been doing it every 3/4 months since we got our RDS servers. I think it's a known issue/bug with RDS.

    From our perspective it doesn't have any relation to the 1001 Outlook errors.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-11-08T10:31:27+00:00

    Same errors with Version 2210 Build 16.0.15726.20188. :(

    Not 1001 but "Password required" and no login popup.

    I think profiles with issues are broken before the office downgrade to 2210.

    I user recreated the corrupted profiles the day after the downgrade.

    No issues anymore, no problems since 2 weeks.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-11-08T10:21:45+00:00

    Hi Every one,

    We are currently using only one RDS and have stopped the other RDS's for new log ins and the problem is solved. we have expand the memory module and other needed stuff for this server. this is by the way until Microsoft finds a thorough solution for this problem.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-11-08T10:18:59+00:00

    We haven't downgraded the Office version, we're now on version 2310 and we're getting an average of 8 calls a day from 40 users for 1001 errors.

    We are following our procedure, which is to reconnect the person to the last server where it worked. And in 9 cases out of 10 it works, but it's time-consuming.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-11-08T09:59:03+00:00

    We "downgraded" to 2307 build 16626.20208. This fixed the issue it seems. At least so far, we have not heard of any 1001 issues. We have been running 2307 for approximately 2 weeks now. Haven't had any password changes in this periode

    Was this answer helpful?

    0 comments No comments