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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-10-11T11:05:32+00:00

    Hi,

    MS support got back to me and they analyzed my provided information and logs. They noticed that the user state is "WorkplaceJoined" (cmd: dsregcmd /status) and this is not the the desired state.

    Image

    I was recommended:

    1. To block WorkplaceJoined by adding registry keys:

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin

    DWORD: BlockAADWorkplaceJoin

    Value:1

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin

    DWORD: AutoWorkplaceJoin

    Value:0

    1. To additionally configure registry keys:

    HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles 

    DWORD: RoamIdentity

    Value: 1 

    HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity 

    DWORD: NoDomainUser

    Value: 1

    1. To use all three methods to clean up tokens from https://learn.microsoft.com/en-us/office/troubleshoot/activation/reset-office-365-proplus-activation-state?source=recommendations#method-clear-prior-activation-information-manually
    2. To make sure to exclude locations from roaming:

    %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy 

    %localappdata%\Microsoft\TokenBroker 

    1. If the issue still exists: to run the command to repair broker as logon script for users. 

    Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown 

    Please also note that the second workaround I advise and use, most of the time fixes the issue: https://techcommunity.microsoft.com/t5/outlook/outlook-desktop-app-quot-something-went-wrong-1001-solution/m-p/3885670

    Was this answer helpful?

    1 person found 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-04T15:28:25+00:00

    Microsoft support acknowledges there are a lot of reports regarding the 1001 error message. This is being investigated by several teams without luck so far in finding a common root cause that applies to all customers.

    I am still waiting for my access to a MS tech after logging it with our provider over two week ago.

    Was this a phone discussion where you were told this or in the body of an email. If it was an email it would be great to see that.

    We've decided against rolling back office due to the security issues especially CVE-2023-23397 around March-23. I wonder if that has been the culprit and MS are in a catch-22 situation. Pure conjecture by me of course.

    Saying that this may be our nuclear option if it becomes too disruptive

    On a side note. I would like to commend all those engaging in this forum on their efforts, collaboration and clear information provided in the absence of any Microsoft techs. It's one of the best I have ever read

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2023-10-04T14:51:30+00:00

    MathieuVandenHautte

    The commonality is RDS environments, running Windows Server 2019/2022, with multiple session hosts, M365 apps and roaming user profiles (User Profile Disks, FSLogix etc.).

    My personal opinion on the cause of the issue is a bug/fault with the way that M365 apps authenticate when a user moves between session hosts. A security token or something similar not liking the fact that the app is being opened and authenticated on a different host.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2023-10-04T09:16:29+00:00

    Same here, send logfiles etc. and mentioned this thread on the forum

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments