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

278 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-10-05T12:54:24+00:00

    Hello Steven

    On our Windows Farm:

    Windows Server 2019

    FSLOGIX 2.9.8612.60056

    MS 365 Apps for Enterprise 16.0.160.26

    And with this setting:

    Image

    Image

    For the moment works as expected, I will inform you i we have again a 1001 Error.

    This is great info Giuseppe, thank you for sharing. I think the biggest difference is that you have ADAL enabled and WAM disabled, which I haven’t touched yet. This may be the secret sauce we’re looking for.

    Out of curiosity, how many days have you been 1001-free, and how many daily users? Our environment has 4 RDSHs with about 33 people in it daily with the goal of rolling out to 125 within the next couple of weeks. With our user count, we see a handful of 1001s a day, some turning into MFA loops until the user fully logs off the RDSH, then back in again.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-10-05T06:26:42+00:00

    Hello Steven

    On our Windows Farm:

    Windows Server 2019

    FSLOGIX 2.9.8612.60056

    MS 365 Apps for Enterprise 16.0.160.26

    And with this setting:

    For the moment works as expected, I will inform you i we have again a 1001 Error.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2023-10-04T20:19:31+00:00

    I have an active ticket with Microsoft support. When we had our initial call, we showed them the problem and replicated it after they've turned on logging. I also sent them a link to this forum.

    I have requested to get the ticket escalated to a senior tech but have yet to speak with any escalation engineers.

    Based on my testings so far, though it still happens, updating FSLogix to the latest version and enabling Roam Identity helped minimize the impact. We used to get a call at least once a day regarding this issue and has been down to once a week. The ones we've dealt with recently were caused by the same folders being outdated (Modified date were before FSLogix update).

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-10-04T19:35:08+00:00

    We are only 10 pages deep with 95 replies and 120 people saying they have the same question. I don't visit this forum a lot to know but to me that seems like a large amount of people/companies that Microsoft might want to look at this.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-10-04T17:09:16+00:00

    I'm glad you've found some positive results with your changes; however, I may have some contradicting findings unfortunately...

    I'm on Day 2 of using 16.0.16026.20200 Office (x86) with FSLogix 2.9.8228.50276 and error 1001 came back. Yesterday, the downgrade fixed a lot of things for us; users that were stuck in authentication loops were able to sign in, error 1001 and WAM errors all disappeared, etc. Now, we have a user where their FSLogix profile was created fresh yesterday, no issues at all, now all of the sudden this morning, they're getting auth loops and error 1001 when signing into Word. More specifically, they received error 1001. To fix it, they signed out of Word, but upon trying to sign back in, they got error 1001 again but stayed signed out. Trying to sign in a second time, their MFA just kept prompting over and over, never getting fully logged in.

    The server did not reboot since yesterday, no windows updates, no Office updates... everything is unchanged since yesterday.

    In another neck of the woods, one of my co-workers mounted another user's FSLogix profile when they were not logged in and deleted the following folders.

    C:\users$user\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

    C:\users$user\AppData\Local\Microsoft\IdentityCache

    C:\users$user\AppData\Local\OneAuth

    After deleting these folders, the user was able to log back in and open Office without error 1001 once again.

    I tried excluding users from FSLogix ODFC but this didn't change anything, worth a try.

    Next troubleshooting steps I'm going to try...

    1. Upgrade FSLogix to latest version, keep Office on 16.0.16026.20200, and add RoamIdentity reg key = 1.
    2. Use custom profile redirections.xml within FSLogix to EXCLUDE the folders my co-worker deleted from being stored within the FSLogix profile. If I can make it so Office authentication is localized to each RDSH server, that may be the fix.

    I'll update as soon as I have some new findings.

    Was this answer helpful?

    0 comments