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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-12-28T23:16:01+00:00

    Hi everyone

    First of all I wanted to thank you all for sharing this wealth of information here.

    I was going crazy trying to figure this out and was happy when I finally found this thread which described all the problems I was having.

    I work for an MSP and I'm dealing with this problem in several client environments.

    My setups are similar to what everyone described before, this is where it's the worst

    • RDS 2019 (or 2022)
    • Office 365 (16.0.17029.20068)
    • FSLogix Profile Container (2.9.8162.60056

    Funny enough not all of our clients have this issue, some haven't had a single sign-in issue, in others it keeps popping up everywhere.

    I have tried several possible solutions before I found this thread but what seemed to help was to block the Workplace Join and delete all the stale devices in Entra.

    So far I only have results from test accounts, since it's the middle of the night here right now.

    I think I'll try updating Office as well.

    I'll keep you posted

    Thanks
    Philip

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. 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
  3. Anonymous
    2024-01-02T10:46:06+00:00

    Buenos días.

    Mismo problema, aun sin solución aparente de momento.

    Aporto datos:

    Hemos conseguido una solución algo CUTRE, copiar el contenido de la carpeta "C:\Users%username%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC" con una directiva al inicio de sesión, a una carpeta de red accesible.

    Parece que no copia el contenido de esa carpeta en entornos RDS con granja, como es nuestro caso.

    robocopy "C:\Users%username%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC" "\SRVNAME\ac%username%\AC" *.* /e /s /xo /COPY:DATSO

    robocopy "\SRVNAME\ac%username%\AC" "C:\Users%username%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC" *.* /e /IM /COPY:DATSO

    No es una solución que me guste, pero ha conseguido igualmente miminizar los errores, tanto de 1001, como de petición de password constante en el entorno de RDS en Granja.

    Saludos.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-01-09T15:58:26+00:00

    I tried all of the below but non of these resolved the issue

    • Initial Workaround: Deleted two JSON files from the Outlook Appdata user folder, followed by signing out and back in from:
      • C:\Users%username%\AppData\Local\Microsoft\Outlook\16\
      • *** Email address is removed for privacy ***
      • *** Email address is removed for privacy ***
    • Secondary Step: When the initial workaround was inconsistent, we removed the same JSON files along with the 'OneAuth' and 'IdentityCache' folders, then repeated the sign-out/in the process:
      • C:\Users%username%\AppData\Local\Microsoft\OneAuth\
      • C:\Users%username%\AppData\Local\Microsoft\IdentityCache\
    • Further Measures: If the previous actions failed, as extensively discussed in this thread, we signed the user out, deleted the 'Microsoft.AAD.BrokerPlugin' folder from the User Profile Disk, and then reconnected to the RDS.
    • Last Resort: Attempted to recreate the user session.

    I then added the below regkeys and removed any entries within Microsoft Entra dating back before 2020 and the issue was resolved

    We are now investigating a solution that involves blocking the 'WorkplaceJoined' option by adding the following registry keys:

    • HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin
      • DWORD: BlockAADWorkplaceJoin Value: 1
    • HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin
      • DWORD: AutoWorkplaceJoin Value: 0

    This was on 2 x RDS servers, no reboot was required. This fixed it for all users after around 30 minutes of adding the rekeys

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-01-10T11:15:18+00:00

    This was my solution:

    Create the following regkey on all RDS session hosts:

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin

    DWORD: BlockAADWorkplaceJoin Value: 1

    Remove the FSLogix profile for the users and recreated the FSLogix profile.

    Was this answer helpful?

    0 comments