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
    2023-09-19T10:02:30+00:00

    Zaltbommel5301

    The issue isn't specific to FSLogix unfortunately. We use regular User Profile Disks and are having the exact same issues you are describing.

    In my opinion this is 100% a problem that Microsoft need to resolve. I am hoping that at some point they will at least acknowledge the issue. Then maybe a fix will follow.

    I've not found any patterns with users or RDS session hosts either. It seems completely random. We are keeping a list of users who have had the problem and some do have it more than others. Some users haven't had the problem at all.

    I'm in contact with a guy that works at an MSP and he has multiple customers with the exact same problem.

    As with you we can have a user working fine all day with Outlook and then out of nothing it stops working. And we have users that we fix the problem for, then the next morning they have the problem again.

    To briefly summarise the steps we take when a user has the problem:

    Note: These steps don't fix the problem for good for the user. It nearly always comes back at some point.

    1. Close all M365 apps.
    2. Delete the Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy from C:\Users<username>\AppData\Local\Packages
    3. Sign out of Edge.
    4. Temporarily set Internet Explorer as the default web browser.
    5. Re-open Outlook and check if it's working again. If it is, set Edge back as the default web browser and hand back to user.
    6. If Outlook still isn't playing ball, go through all of the steps on this site: https://www.matrix7.com.au/microsoft-365/o365-outlook-logon-error-something-went-wrong-1001/
    7. If Outlook still won't work, try all of the above steps again, and then if still no good, nuke the users' RDS profile and set it up from scratch. Note - this doesn't usually make the problem go away for good.

    Shane Vandewalle

    As above I'm hoping that with more people posting/replying to forum threads about the issue Microsoft will eventually acknowledge the problem and hopefully come up with a fix.

    It's definitely a Microsoft problem though.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-09-19T08:49:43+00:00

    I feel like nobody from Microsoft nor fslogix cares about this, yet many users are having these issue's. Why is this taking so long?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. 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
  4. Anonymous
    2023-09-18T14:58:50+00:00

    Hi Stephan, I have an update with our case.

    We were able to resolve our 1001 error issue by adding the shellbridge registry from the following Citrix article. https://support.citrix.com/article/CTX267071/  However, this is a fix for Citrix Virtual Apps so I don't think it will help with RDS deployments.

    The required hotfix was already pushed from a previous Microsoft roll-up so we didn't need to apply it separately before applying the following registry "Shellbridge" hack:

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

This resolved the 1001 error, but now introduces a new problem for us to troubleshoot for our users when logging off.
Processes stay open and prevent a clean logout after closing the last application.

The article has a work-around section I'm going to be testing next to see if I can resolve the 1001 error without having to apply the shellbridge registry hack.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2023-09-18T10:20:21+00:00

    Ivo Schoemaker [Bolk Transport]

    We also remove the AAD Broker Plugin folder as a first stage for anyone that reports the problem. Sometimes this works and sometimes it doesn't and we have to go through the rest of the steps. We've even recreated the RDS user profiles for a number of users only for them to have the problem again two days later.

    Wolfgang Burkhard1

    I too suspected it was a problem with our infrastructure, but once we started seeing more forum threads describing the same behaviour with the same environment, I came to the conclusion that it was a problem either at Microsoft's side, or a problem they had introuced by way of a Windows/Office update.

    I am in contact with someone that works for an MSP and he has a number of customers with the same problem.

    It also seems that in the last week or so the problem is getting worse/more common.

    Stephan Stoke

    For us the problem is with users that just have the one mailbox (no users have more than one mailbox).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments