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
    2024-03-19T08:29:01+00:00

    FINALLY A STRAIGHT ANSWER FROM MICROSOFT!

    Hello Lars,

    Please check this and follow the below steps and let me know of the outcome. and if you needed any help, please let me know.

    What Causes Error 1001?

    There are several possible causes of error 1001, such as:

    • Corrupted office registry key under user configuration.
      • Customer disabled WAM. (Disabling ADAL or WAM isn't recommended for fixing Office sign-in or activation issues)​

    https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/administration/disabling-adal-wam-not-recommended​

    How to Fix Error 1001?

    Depending on the cause of error 1001, you can try one or more of the following solutions:

    • Reset for office activation.
    • Fix WAM component.
    • Exclude required authentication component from your Antivirus.
    • Correct device identity by configuring your device as hybrid join if it is a domain join device.
    • Add additional mailboxes using delegated credential.
    • Roaming of WAM token when using roaming profile management tools like UPD, FSLOGIX or other tools
    • Rest cash for Firewall rules.
    • Ask customer to apply CITRIX recommendations:
      Fixed issues | Citrix Virtual Apps and Desktops 7 2203 LTSR

    How to apply the Fix?

    Depending on the cause of error 1001, you can try one or more of the following solutions:

    -Reset for office activation.

    • Make sure to close all running office desktop applications, OneDrive, and teams.
    • To reset office activation, the affected user should be member of the local administrators on the device.
    • To promote the user as an admin on device you can use these steps. Make sure to remove the user after troubleshooting is done.
    • In Windows press Windows button + R to open the Run and type “lusrmgr.msc” for opening the windows Local user and group manager.
    • you can just start CMD as admin and type same command “lusrmgr.msc”.
    • Make sure you run it as an admin.
    • Select Groups → then double-click on "Administrators" -> Add -> Locations -> [select domain] -> Enter Username in Box -> Check Names -> then “OK.”
    • If not then running the scripts should be done twice, one time as a user and another one as an administrator.
      • Scripts required to be run are:
    1. OLicenseCleanup.vbs
      Download the OLicenseCleanup.zip file, extract the OLicenseCleanup.vbs script, and run it using the following command in CMD:
      cscript OLicenseCleanup.vbs
    2. signoutofwamaccounts.ps1
      Download the signoutofwamaccounts.zip file, extract, and run the signoutofwamaccounts.ps1 script with elevated permissions. 
      .\ signoutofwamaccounts.ps1
      make sure running scripts is allowed on the device. If not use this PowerShell command to allow it:
      Set-ExecutionPolicy -ExecutionPolicy Unrestricted
    3. WPJCleanUp.cmd
      Download WPJCleanUp.zip, extract the WPJCleanUp folder, and run WPJCleanUp.cmd as user and not as admin.

    -Fix WAM component.

    to make sure that WAM components are present, run the two PowerShell commands in the following article:

    https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/authentication/automatic-authentication-fails

    If you use office desktop application on RDS, AVD or VDI, then make sure to have these commands as part of a logon script for the users.

    -Roaming of WAM token when using roaming profile management tools like UPD, FSLOGIX or other tools

    Roaming of WAM token is not supported, since these tokens are encrypted with a session key, which will be stored on the device during token acquisition, therefore roaming the token causes authentication loop for users.

    Make sure to exclude the token following folders from roaming with the user profile:

    %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\TokenBroker

    %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\LocalState

    %localappdata%\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy

    %localappdata%\Microsoft\TokenBroker

    %localappdata%\Microsoft\OneAuth

    %localappdata%\Microsoft\IdentityCache

    -Exclude required authentication component from your Antivirus.

    Make sure you exclude the component listed in the following article in your Antivirus configuration.
    https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/authentication/cannot-sign-in-microsoft-365-desktop-apps

    %windir%\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

    %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

    %windir%\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy

    %localappdata%\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy

    %localappdata%\Microsoft\TokenBroker

    %localappdata%\Microsoft\OneAuth

    %localappdata%\Microsoft\IdentityCache

    -Correct device identity by configuring your device as hybrid join if it is a domain join device.

    • The preferred device identity for a domain join device is hybrid join.
    • Workplace Join is not supported on RDS, AVD or VDI.
    • You need to instruct customers to block it using registry.
    • You can run this command as admin in PowerShell on affected RDS server:
      Set-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin -Name BlockAADWorkplaceJoin -Type DWord -Value 1
    • You can make it available to all organizational devices.

    https://learn.microsoft.com/en-us/entra/identity/devices/how-to-hybrid-join

    • or apply it to a specified set of devices.

    https://learn.microsoft.com/en-us/entra/identity/devices/hybrid-join-control

    -Add additional mailboxes using delegated credential.

    Add a shared mailbox as an additional account in Outlook Desktop - Outlook | Microsoft Learn

    -Cached firewall rules in windows registry.

    Use the following commands to reset Firewall rules:
    Remove-Item "HKLM:\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\AppIso\FirewallRules"

    New-Item "HKLM:\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\AppIso\FirewallRules

    -Missing configuration in CITRIX

    Confirm that issue is not reproducible outside CITRIX or in full desktop versions and only to published applications.

    Use the following commands to create required registry entry as per CITRIX recommendations:
    Set-ItemProperty "HKLM:\SOFTWARE\Citrix\Citrix Virtual Desktop Agent" -Name Shellbridge -Type DWord -Value 1

    **Note:**If the issue can’t be reproduced when logging directly to the server, and the configuration for CITRIX did not help, the customer needs to involve CITRIX support in this situation

    Scop and logs required for escalation:

    • Affected application (only Outlook, all Office Apps);
    • Number of affected users.
    • Number of affected devices.
    • How does it happen? Is it when they sign in for the first time? When they open a new session? When they open specific files?
    • Is it reproducible or sporadic?
    • Windows(server/client) version and build.
    • Office version and build.
    • Physical or virtualized environment.
    • Details on their networking including Antivirus/Proxy/Firewall
    • How are they managing users' profiles: UPD, FSLogix, Citrix,…?
    • Details on their network include Proxy/Firewall.
    • MSOAID logs 
      https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/diagnostic-logs/use-msoaid-for-authentication-issues
    • Output for the command “dsregcmd /status” in CMD as user

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  2. Anonymous
    2024-03-08T19:12:58+00:00

    I'm late to the party. Just read the entire thread. We've been having the issue on and off for a while now.

    RDS environment, 3 session hosts. Server 2019, and UPD.

    I don't see any mention of error 1001 in any of the release notes of the updates but will try updating from 16.0.17126.20190 this weekend.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-02-16T07:56:56+00:00

    Hi RandomMS User,

    Please see the build versions

    Windows Server 2019 Standard

    Version 1809

    OS Build 17763.2803

    Office 365 Apps for enterprise 16.0.17231.20194

    Hi @Lee GTS,

    Thank you for your quick answer. I'll patch some infrastructures next week probably with OS Build 17763.5329 + Office version 16.0.17231.20236 and I'll provide feedback here.

    I hope the problem hasn't reappeared on your end !

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-02-15T14:53:07+00:00

    Hi RandomMS User,

    Please see the build versions

    Windows Server 2019 Standard

    Version 1809

    OS Build 17763.2803

    Office 365 Apps for enterprise 16.0.17231.20194

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-02-15T09:02:43+00:00

    Hi All,

    We have been experiencing the 1001 issue and other Office activation issues with multiple customers over the last six-twelve months. similar infrastructure Windows 2019 RDS, Office 365 Apps for Enterprise and UPD.

    since December\January with one customer in particularly that have 4 RDS Farms on different domains, total about 16 RDSH approximately 150 users was being impacted very heavily. This was impacting users randomly and some users more than others. Then suddenly Friday lunchtime GMT the Issues just stopped.

    Has anyone else that have been experiencing these issue found that they just resolved on Friday? As of today the customer is having no reports of the 1001 issue.

    We have tried various fixes on these forums on users and non that resolved permanently. Server wide fixes such as disabling workplacejoin have only been tested on test servers. No changes had been made when the problem suddenly resolved.

    Hi Lee GTS,

    We are exactly in the same situation as you, multiple customers, RDS 2019 with UPD, Office 365 and 1001 error + multiple passwords prompts over the last six months.

    May I ask you which Windows Server build/CU and which Office version are currently installed on your infrastructure ?

    We still encounter the issue today and we hope that like you, the 1001 will miraculously disappear with the same versions as you.

    Thank you in advance for your help !

    Was this answer helpful?

    0 comments