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
    2024-10-12T13:55:44+00:00

    Mate, you legend.

    Ok since I seen so many people having issues. Here is the fix that worked for me.

    MY ENVIRONMENT

    1x GW/Broker server 2022
    2x Session host server 2022
    -365 for business (latest build) (using business premium licensing) Install with custom XML to override the SCLCacheOverrideDirectory, you want to point this to a UNC share. https://learn.microsoft.com/en-us/microsoft-365-apps/deploy/office-deployment-tool-configuration-options

    <Property Name="FORCEAPPSHUTDOWN" Value="FALSE"/>

    <Property Name="SharedComputerLicensing" Value="1"/>

    <Property Name="SCLCacheOverride" Value="1" />

    <Property Name="SCLCacheOverrideDirectory" Value="\server\share%username%" />

    The above are the parameters I used.

    FSLOGIX REG SETTINGS:
    CleanOutNotifications - dword - 1
    DeleteLocalProfileWhenVHDShouldApply - dword - 1
    Enabled - dword - 1
    FlipFlopProfileDirectoryName - dword - 1
    IsDynamic - dword - 1
    KeepLocalDir - dword - 1
    LockedRetryCount - dword - 12
    LockedRetryInterval - dword - 5
    OutlookCachedMode - dword -1
    PreventLoginWithFailure - dword - 1
    PreventLoginWithTempProfile - dword - 1
    ProfileType - dword - 3
    ReAttachIntervalSeconds - dword - 10
    ReattachRetryCount - dword - 60
    ReDirectXMLSourceFolder - RegSZ - path to UNC
    RemovedOrphanedOSTFilesOnLogoff - dword - 1
    RoamIdentity - dword - 1
    Roamsearch - dword - 0
    SetTempToLocalPath - dword - 3
    SizeInMBs - dword - whatever size you want
    VHDLocations - RegSZ - path to UNC
    VolumeType - RegSZ - VHDX

    Add the following to this:

    <?xml version="1.0" encoding="UTF-8"?>

    <FrxProfileFolderRedirection ExcludeCommonFolders="0">

    &lt;Exclude Copy="0"&gt;AppData\Local\Packages\Microsoft.AAD.BrokerPlugin\_cw5n1h2txyewy&lt;/Exclude&gt; 
    
    &lt;Exclude Copy="0"&gt;AppData\Local\Packages\Microsoft.Windows.CloudExperienceHost\_cw5n1h2txyewy&lt;/Exclude&gt; 
    
    &lt;Exclude Copy="0"&gt;AppData\Local\Microsoft\TokenBroker&lt;/Exclude&gt; 
    

    </FrxProfileFolderRedirection>

    Note: I believe this is if you do not do the custom 365 install with XML (read above) I could be wrong. You can add it for good measure anyway it does not break anything.

    REG KEY TO ADD ON BOTH SESSION HOSTS

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin]

    "BlockAADWorkplaceJoin"=dword:00000001

    This will remove that prompt for Microsoft to manage the device. we do not want this. I beleive this is what breaks the identity token for OneDrive. Log into Entra ID > go to devices and search your session hosts. If they are in there just remove them it will not break anything.

    Note: Users will have to sign into the following
    Edge - will prompt MFA
    Teams - will prompt MFA
    Office apps - will prompt MFA
    OneDrive - will prompt MFA

    This is the only down side. Once you do this once they won't have to go again for like 30 or 90 days (i cant remember)
    They will also need to do this on the other session host just once to.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-03-20T17:02:12+00:00

    Well that certainly narrows it down.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-06-07T17:16:51+00:00

    Thank you to the community for providing all this great information. We have a customer who's experiencing a similar same issue as described.

    The environment consists of Windows Server 2019, a 2210 version of FSLogix, Office 365 in an Azure Virtual Desktop environment. Users are able to launch Office apps when logging in with a new profile without issue; however, after a logon cycle, they will be prompted to enter credentials when launching Office apps. After launching an Office app, they will receive the 1001 error after completing the sign-in process. They will not be authenticated and are unable to use the Office app. If the user, then closes Office and relaunches without a logon cycle all Office apps launch without issue. This process must be repeated after each logon cycle for all users. This issue has been confirmed in FS2210.9.8884.27471 and FS2210.9.8784.63912 of FSLogix.

    We have another Windows Server 2019, Office 365, with an older version FSLogix (2201) running in Citrix and it is not experiencing the issue. We downgraded FSLogix (FS2201.9.8111.53415) to that older version in our Windows Server 2019 Azure Virtual Desktop environment and it resolved the issue. Unfortunately, public download of the older versions of FSLogix are no longer available. It appears to be an issue that was introduced in a 2210 version of FSLogix for Windows Server 2019.

    Hope that helps someone else.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-10-02T14:33:53+00:00

    Have completed testing with a newer version that goes back to around March this year. Version 2301 - build 16.0.16026.20200 does not seem to be affected by this bug and can be considered production ready.

    Office Deployment Tool configuration file:

    <Configuration>

    <Add OfficeClientEdition="64" Channel="Current" Version="16.0.16026.20200">

    <Product ID="O365ProPlusRetail">

    <Language ID="en-us" />

    </Product>  

    </Add>

    <Updates Enabled="FALSE" />

    <Display Level="None" AcceptEULA="TRUE" />

    <Property Name="AUTOACTIVATE" Value="1" />

    <Property Name="SharedComputerLicensing" Value="1" />

    </Configuration>

    Downgrading FSLogix did not work for us, so we're considering downgrading Office to be the fix for now. Office auto-updates have been disabled and all future updates will be processed manually and tested before mass deployment.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-09-19T08:37:22+00:00

    Hi, We have the same issue here. Using multiple RDS servers with FSlogix profiles. Deleting the FSlogix profiles from the affected user(s) sometimes helps for a few days, sometimes the problem is getting back right after creating a new profile. It's not related to a specific server and not related to specific users. We think it has something to do with FSlogix and/or the MFA check that Office checks in background or something like this. Sometimes a user is working for a few hours and does not have any problems and then just out of nothing Outlook does not synchonize and shows "need password" at the bottom of the Outlook screen. When user wants to login, which normally isn't necessary, the error 1001 is showing. When getting the error 1001 it's not possible to login and profile needs to be deleted. When lucky you can work for period of time and last a few days or not, its hopeless.

    All the other workarounds mentioned on othet MS forums or Reddit such as deleting AADbroker, Identycache and OneAuth folders etc. does not work. Deleting FSlogix profile is the only thing that works for us sometimes.

    @Microsoft: When are you guys going to do something about it...?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments