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-10-11T13:04:20+00:00

    Do you mind posting what your OS and Office version you were using? Did the above changes resolve things for you?

    Also, can you post an example of your exclusions for FSLogix xml? I'm struggling to get mine going and it would be helpful if there was a working example available. Much appreciated!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-10-11T11:05:32+00:00

    Hi,

    MS support got back to me and they analyzed my provided information and logs. They noticed that the user state is "WorkplaceJoined" (cmd: dsregcmd /status) and this is not the the desired state.

    Image

    I was recommended:

    1. To block WorkplaceJoined by adding registry keys:

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin

    DWORD: BlockAADWorkplaceJoin

    Value:1

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin

    DWORD: AutoWorkplaceJoin

    Value:0

    1. To additionally configure registry keys:

    HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles 

    DWORD: RoamIdentity

    Value: 1 

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

    DWORD: NoDomainUser

    Value: 1

    1. To use all three methods to clean up tokens from https://learn.microsoft.com/en-us/office/troubleshoot/activation/reset-office-365-proplus-activation-state?source=recommendations#method-clear-prior-activation-information-manually
    2. To make sure to exclude locations from roaming:

    %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy 

    %localappdata%\Microsoft\TokenBroker 

    1. If the issue still exists: to run the command to repair broker as logon script for users. 

    Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown 

    Please also note that the second workaround I advise and use, most of the time fixes the issue: https://techcommunity.microsoft.com/t5/outlook/outlook-desktop-app-quot-something-went-wrong-1001-solution/m-p/3885670

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2023-10-10T17:51:29+00:00

    https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/administration/disabling-adal-wam-not-recommended There is this MS article from March 3/16/2023 stating that starting with build 16.0.7967 office client apps, MS changed the default Office auth type to Web Account Manager (WAM). So for any of you that found that forcing to ADAL, or reverting to an older version than March.. That seems to align.

    I note in many of the posts, resetting profiles, deleting certain office or auth related folders would clear the error at least temporarily.

    I'll note that we are using Citrix UPM(User profile management) which is a streamed/roaming user profile service... The behavior is identical, and arrived on day one of our Sept patched image (both office and windows Sept patches). Not really any reports prior to that.

    I provided our team this blog and the registry entries that some of you kindly posted as workarounds (forcing ADAL), we'll see how that goes.

    For MS's part, a rewrite/fix/re-think/self-healing of files written to profile (with minimal needed user action) is required. Even if "something went wrong (1001)" then add 'would you like to log out and try again" which would/could clear the profile files and re-create them, instead of everyone here supporting customers having to do it, would be a good start. :-)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-10-10T16:22:58+00:00

    Thank you both for your contributions our troubleshooting!

    Update from my end...

    • Windows Server 2019 Standard
    • 4x RDSHs
    • FSLogix 2.9.8612.60056
    • Microsoft 365 Apps for Business (x86) 16.0.16026.20200

    I added the BlockAADWorkplaceJoin=1 reg key and it completely broke Office logins for me. I would click "Sign In" at the top of Word and it would just do nothing. When I tried in Outlook, I'd load my cached profile, and at the bottom, it would say "Needs password". I clicked it and it never prompts with a login screen. I removed to reg key and it's back to normal.

    I'm curious, what version of Office are you guys using? I wonder if me not being on the latest (or simply a newer) version of Office is the reason mind broke completely. There's people using my servers right now but after a reboot tonight and blocking new connections, tomorrow I'll see if Office updates fix things.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-10-09T17:01:27+00:00

    Our 1001 errors stem from Workplace Join enabled on our VDIs and we should not have. We have been getting 1001 errors pretty consistently for a little over a month now. After this implementation, they have stopped and have so for approx 2 weeks. Here's what we noticed and what we did.

    Our environment uses multi-session servers. Server 2019.
    Some clients use profile containers, some use Citrix Profile Management. Both were having 1001 errors.

    Because we had workplace join enabled in our non-persistent environment, every time someone authenticated and workplace joined, a duplicate device entry was created with the Hostnames of all our non-persistent VDIs. I saw this in Microsoft Entra, under devices. We had hundreds of Stale Devices, all dupes of our VDI hostnames. And hundreds of unmanaged devices in the same state. I removed all of those.

    This article here clued me in to that and also the potential problems it may cause.

    https://learn.microsoft.com/en-us/azure/active-directory/devices/howto-device-identity-virtual-desktop-infrastructure 

    Quotation from the article:

    "Failure to manage stale devices can lead to pressure increase on your tenant quota usage consumption and potential risk of service interruption, if you run out of tenant quota. You should follow the guidance documented below when deploying non persistent VDI environments to avoid this situation."

    Also the registry entry it states to ensure that is set:

    "When using non-persistent VDI, if you want to prevent adding a work or school account, ensure the following registry key is set:
    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin: "BlockAADWorkplaceJoin"=dword:00000001"

    "

    I set that key, via GPO on our VDIs.

    After setting that registry key, new profiles authenticate without incident and more smoothly. There's no more attempt to WPJ. However, existing profiles that were created before the registry key above were set, still attempt to workplace join. With WPJ disabled via GPO, profiles in this state will attempt to WPJ, but eventually time out and auth successfully. (the little WPJ box just sits and spins for a minute or so) To address this, I made a batch script that deletes all the M365 authentication locations. This way we don't have to delete the entire user profile. The script definitely takes a more "scorched earth" approach. I run this within the logged-in user context. I then log off the user, log back in, attempt to authenticate again. It's usually successful. If not, I delete the entire profile under mail in control panel and try again.

    Here's the batch. Please use at your own risk:

    "
    :: @echo off

    setlocal

    :: Delete directories

    rd /s /q "%userprofile%\AppData\Local\Microsoft\IdentityCache"

    rd /s /q "%userprofile%\AppData\Local\Packages\Microsoft.AccountsControl_cw5n1h2txyewy"

    rd /s /q "%userprofile%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy"

    rd /s /q "%userprofile%\AppData\Local\Microsoft\TokenBroker"

    rd /s /q "%userprofile%\AppData\Local\Microsoft\OneAuth"

    rd /s /q "%userprofile%\Appdata\Local\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy"

    :: Search for and delete TokenBroker directories

    FOR /D /R "%localappdata%\Packages" %%D IN (*\AC\TokenBroker) DO (

    IF EXIST "%%D" (

    echo Deleting: %%D

    rd /s /q "%%D"

    )

    )

    :: Delete registry keys

    reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\AAD" /f

    reg delete "HKCU\Software\Microsoft\WindowsNT\CurrentVersion\WorkPlaceJoin" /f

    reg delete "HKCU\Software\Microsoft\Office\16.0\Common\Identity\Identities" /f

    reg delete "HKCU\Software\Microsoft\IdentityCRL" /f

    endlocal

    echo Script completed.

    pause
    "
    Note:

    -You'll need to disable the GPO "Prevent access to registry editing tools" for a bit if you want to prevent access denied when deleting those registry keys.

    Other things I've found:
    If you're including/excluding folders in your profiles after log off, make sure these two folders are included, or users will be asked to authenticate every fresh login.

    'AppData\Local\Microsoft\OneAuth'

    'AppData\Local\Packages\Microsoft.AccountsControl_cw5n1h2txyewy'

    That's it. Maybe that makes sense. I hope that helps someone. I saw someone post in this thread that their 1001 errors just went away. Maybe this wasn't the cause and MS fixed something on their side. Either way, WPJ should not be enabled in an Non-Persistant VDI env per Microsoft, so at the very least, we're no longer getting duplicate and stale devices in Entra and the auth process is as it should be.

    Summary:

    1001 errors seem to occur during the WPJ process. Does your env need Workplace Join? If not, turn it off with the reg key above, then fix your existing profiles by nuking all M365 auth locations, and reauthenticate.

    This fix appears to be working for us.

    For simplification I have narrowed down the specific changes that are required:

    Add from admin account:

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin: "BlockAADWorkplaceJoin"=dword:00000001"

    Sign out of all Office apps on affected user account.

    Open regedit on affected account and delete the following:

    HKCU\Software\Microsoft\Windows\CurrentVersion\AAD

    HKCU\Software\Microsoft\WindowsNT\CurrentVersion\WorkPlaceJoin

    Delete the following folders from affected user's appdata:

    %userprofile%\AppData\Local\Microsoft\TokenBroker"

    %userprofile%\AppData\Local\Microsoft\OneAuth"

    %userprofile%\AppData\Local\Microsoft\IdentityCache"

    Open Word, sign in, account should sign in without issue.

    After this all Office apps should now be signed in automatically or the sign in should work without issues.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments