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
    2024-09-19T08:11:47+00:00

    Hi everyone

    After loosing a lot of time investigating this b***-breaking issue, I found it worthy to spend some time sharing our solution here as well. Hopefully it might help some of you admins preventing more headaches on this MS issue.

    One of our customers ran into this issue only since recently too! After many troubleshooting steps - thanks to everyone that contributed to this post btw - and going through all the presented workarounds (which sometimes seemed to work temporarily) we've found a permanent solution. Perhaps this will not be applicable to all of you, but at least our issue got solved using this method.

    We are running RDS in a Citrix CVAD 2203 CU5 environment, so this might not be applicable to all of you, but the root cause might be related (as it is not Citrix... ;-)

    *Servers are only domain (not hybrid or AAD) joined since Office is licensed using a different tenant.

    Server 2019 OS standard 1809 build 17763.6293

    Office 2402 build 17328.20588 (Semi-annual enterprise)

    FSLogix 2210 hotfix 4 (2.9.8884.27471)

    A login script runs the register WAM (Add-AppxPackage) commands for each user, and re-registers it if it is not present.

    Resetting a user's profile did not solve the issue. Neither resetting appdata folders or what so ever. Even tried excluding FSLogix, rolling back PVS images, etc etc..

    The cause lays in the password prompt not being able to be shown to the user, which generated this error [1001]. Once the user logs in by using a desktop instead of a published app, the issue did not occur! So this (CTX267071 - Shellbridge feature) is what we finally discovered and applied to all of our RDS (Citrix workers) servers which addressed the issue for us. This recommendation WAS described in the summary Lars posted here as well, via this link.

    Solution:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Citrix Virtual Desktop Agent
Name: Shellbridge
Type: REG_DWORD
Value: 1

    Previous workaround:

    Please note that the workaround described in this article was already applied for a couple of years, until now, since it suddenly does not work anymore!:

    1. Disable Web Account Manager via registry.***

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

    “DisableADALatopWAMOverride”= dword:00000001

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity

    “DisableAADWAM”= dword:00000001

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity

    "DisableMSAWAM"= dword:00000001

    Also mentioned there: ***    Disabling WAM as a workaround does not always work and may not be supported by Microsoft.

    The above registry keys which served as a workaround for years have now been removed, as they no longer have a purpose for us.

    Hope this helps! cheers to all

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-03-22T14:29:42+00:00

    Essentially, this problem is caused by hundreds of firewall rules registry keys that are produced during the login process but are not deleted. I had read about the issue with the firewall rules registry entries elsewhere, but I had no idea it would affect the server in this way. I just executed the three suggested registry changes on my server that was having this issue, and the problem went gone (Reboot the server to take effect).

    reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules /va /f

    reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\Configurable\System /va /f

    reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\AppIso\FirewallRules /va /f

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-12-28T23:25:11+00:00

    This is exactly what I did a couple of weeks ago and not one report of issues since. Deleted all Stale entries in Entra (we don't have any Hybrid devices or Joined devices in Entra, only the registered ones from Office Sign-ins.

    Blocked the Workplace Registration and now users just have to login to Office every day since the RDS Session Hosts aren't registering with Entra. Small price to pay to eliminate the daily tickets for this issue.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-11-08T21:59:10+00:00

    There's a registry key to prevent those firewall rules from accumulating:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy DeleteUserAppContainersOnLogoff (DWORD)Value: 1

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2023-07-13T23:29:33+00:00

    Hi ARGUAIROLLES Florian

    May I know whether there are any updates to your question? If you have any questions, please feel free to contact us.

    Best regards,

    Tin

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments