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-11-28T00:35:32+00:00

    Thank you for the suggestion. Unfortunately, our issue is related to the publishing of Excel and Word as published apps in RDS. Our issue matches that of Sander_d-_-b.

    This seems to be a well known issue both Citrix and Parallels have attempted to provide workarounds. Citrix has offered shellbridge and Parallels has offered the -runexplorer option for use when publishing O365 apps. It's seems that these workarounds are now also broken.

    My question still remains.

    Is Microsoft working on a fix for this maddening issue?

    The workaround we have in place is to use Office build 2201 with WAM disabled. The trouble is that this is a VERY old version of Office. This does work consistently. I have shown this to Microsoft support. As soon as I upgrade Office we are no longer able to authenticate because the password window cannot appear when the application is published.

    Does anybody know if Microsoft is doing anything about this bug?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-11-27T14:40:59+00:00

    We're still seeing the issue, however it only occurs a short while after a user has changed their domain logon password. We sync on-prem AD to M365 via Azure AAD Sync.

    Furthermore, it doesn't happen for all users when they are prompted to change their logon password. For example, this week there were five users who's passwords were due to expire and the issue only occurred for one of them.

    Below are the steps that we follow when a user reports the problem with Outlook. We generally find we only have to go down as far as step 8.

    1. Sign out of RDS fully. Then sign back in. Re-open Outlook and try clicking in the bottom right where it will either disconnected or need password. Click that and follow through the authentication process, multiple times if necessary. If an error pops up, close Outlook again and reopen it. Check if it has connected now.
    2. Sign out of the Microsoft account via Excel.
    3. Delete the Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy from C:\Users\AppData\Local\Packages
    4. Delete IdentityCache and OneAuth folders from C:\Users(username)\AppData\Local\Microsoft.
    5. Sign out of RDS profile and then sign back in.
    6. Sign back in to the Microsoft account via Excel. An error message will most likely appear. Close Excel.
    7. Open Outlook. Most of the time it will show Connected in the bottom right.
    8. Open Excel and check to make sure it has signed back into the Microsoft account

    If Outlook still won't play ball: 9. Locate the following key. Add the key if it is not present:

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

    Key name - EnableADAL

    Key type: - DWORD

    Key value – 1

    1. Locate the following two keys and delete them if present:

    Key location:

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

    Key 1 – DisableAADWAM

    Key 2 – DisableADALatopWAMOverride

    1. Open Credential Manager and delete all the credentials relating to Microsoft under the Windows Credentials section.
    2. From Control Panel, open the Mail app, go to Show Profiles, highlight the Outlook profile, click Remove. Re-add the profile in the normal way.
    3. Sign out of RDS and then sign back in.
    4. Open Excel and sign in to the Microsoft account. Verify it has signed in successfully.
    5. Open Outlook. It should show Connected in the bottom right.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-11-27T13:47:48+00:00

    Thanks for the post.

    Not roaming the token is a big issue in environments with multiple session hosts in a collection.

    This Citrix shellbridge fix, is Citrix proprietary, HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Citrix Virtual Desktop Agent. Unfortunately we are not using Citrix.

    I have had a support ticket open with Microsoft for 11 months now. Unfortunately, Microsoft support is not providing me any helpful information. I wonder if Microsoft is working on a bug fix for this.

    Does anyone else have a Microsoft support ticket open for this?

    Is anybody else getting anywhere with Microsoft support?

    Does anyone know if Microsoft is working on a bug fix?

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Anonymous
    2024-10-18T09:46:42+00:00

    Hello,

    i have a Question. do you have the following notice in the redirections.xml?

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

    <FrxProfileFolderRedirection ExcludeCommonFolders="0">

    <Exclude Copy="0">AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy</Exclude>

    <Exclude Copy="0">AppData\Local\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy</Exclude>

    <Exclude Copy="0">AppData\Local\Microsoft\TokenBroker</Exclude>

    </FrxProfileFolderRedirection>

    EDIT: Ok i didnt saw the reply from Admin Chris's posts. There is the notice.

    Was this answer helpful?

    0 comments