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
    2024-02-01T08:22:38+00:00

    Hello

    In our case, 4 RDS 2022 environment, FSLOGIX.

    We did all the Office updates version 2312, Fslogix 2.9.8612.60056.

    Then we changed the registry keys

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

    Then, in Entra, we went to delete the records of the users concerned on the RDS workstations

    After that, log off the user and delete the Fslogix profiles and odfc

    Then reconfiguration of the user's environment on the RDS

    And since no more error 1001 among our users (while we had between 8 and 12 calls per day out of 70 people)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-02-01T08:36:33+00:00

    So i read into that the deleting FSLOGIX profiles which would then remove any kind of roaming error and start it fresh again. Did you get any errors with JUST changing the registry key and deleting in Entra or did you also remove the FSLOGIX profile each time ? Be interesting to see if anyone has fixed theirs with JUST the Registry and Entra fix ?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-02-01T09:08:34+00:00

    In the analyses we were able to do, we noticed that the users had 1 or more RDS servers on which they had no problems, the latter had a record in Entra.

    As long as users were connecting to these machines, there was no problem, but as soon as they changed "Error 1001".

    I had found a piece of information that said that registering RDS servers in Entra didn't work very well, so we decided to do the tests below, rather than registering all servers for each user.

    So we tested the following scenarios:

    1 – just the change in the registry key : no change

    2 – then update the applications (with scenario 1) : no change

    3 – Just delete the Entra record without modifying the profile and the ODFC : the problem comes back

    4 – Deletion of the Entra record and deletion of only the Fslogix profile : this worked the same day and as soon as the user changed the reference server the error reappeared

    5 - Deleting the Entra record and deleting only the profile and fslogix ODFC : and since then no more worries

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-02-01T09:45:37+00:00

    We use regular user profile disks stored on a file share VM as mentioned in an earier reply.

    We now only get calls about the Outlook 1001 error after a user changes their domain logon password. We use Azure AD Sync.

    To fix it for the user we do the following:

    1. Sign out of RDS fully
    2. Re-open Outlook and try clicking in the bottom right where it will either say disconnected or need password. Click that and follow through what it says, multiple times if necessary (it goes through the MFA/password entry process multiple times).
    3. If the 1001 error pops up close Outlook again and re-open it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-02-01T09:51:56+00:00

    So the Roam Identity is in the Profile and not in the ODFC and this seems to have fixed it for us (again I'm only going on the fact it stopped the problems straight away and we've had no more) and we haven't needed to delete ANY profile off at all so has anyone else fixed this but still had the Roam Identity enabled ?

    It does seem to be a slightly different fix for different scenarios.

    Also have we seen this happen to ANY rds environment that doesn't use profiles disks (either FSLOGIX or UPD) or a broker ?

    I'd be interested to find that out as again we've had no problems at all with the same users logging onto our other 2 RDS servers locally (i.e normal local profiles stored on the RDS servers)

    Thanks

    Was this answer helpful?

    0 comments