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-26T13:16:24+00:00

    Just to add to this as well that today we've started getting users that are already logged on getting Outlook flashing when trying to retrieve data but again bouncing them onto a different server seems to fix it and it's not linked to a certain server so for example user A can be on server A with the problem and we bounce them onto Server B and it all works whereas User B could be on Server B and get the problem so we bounce them onto Server A and this fixes it. I've also tried to setup 2 new users in Outlook and both are now showing "advanced setup" when it should pick up their settings and log on even though we've got SSO enabled and then they error so it's getting worse every day.

    It still seems that the Volume Licence version of Outlook we installed to test still works though so it does appear linked to the Click to Run version, not sure if anyone else has a Volume Licence edition they can test this theory with just in case it's not relevant ?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-09-26T13:15:34+00:00

    POTENTIAL FIX:

    I started to suspect the problem is with an Office 365 update, so last night I downgraded the Office install on 1/4 of our host machines.

    This morning, I'm happy to report that all users on the downgraded machine are able to access Outlook without issue, while several users on the machines with the newest version of O365 are still having trouble.

    To downgrade, uninstall Office from your host machine and reinstall using the Office Deployment tool.

    Here is the working XML configuration for us:

    <Configuration>

      <Add OfficeClientEdition="64" Channel="Broad" Version="16.0.8431.2270">

        <Product ID="O365ProPlusRetail">

          <Language ID="en-us" />

        </Product>  

    </Add>

      <Updates Enabled="FALSE" />

      <Display Level="None" AcceptEULA="TRUE" />

    <Property Name="AUTOACTIVATE" Value="1" />

    <Property Name="SharedComputerLicensing" Value="1" />

    </Configuration>

    The command to install is then:

    setup /configure config-file.xml

    Obviously the <Updates Enabled=FALSE" /> section is critical so that Office won't auto-update itself.

    Version 16.0.8431.2270 is quite old, so this isn't a permanent fix as it may open up your environment to security risks. Over the coming days and weeks I'd like to, perhaps with the help of the community, find a newer version of Office that is free from this bug.

    Hope this works for everyone. Let me know either way.

    -Tom

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-09-26T12:44:22+00:00

    Here to add to the growing list of people experiencing this issue.

    We have 2 RDs servers, both 2019, no issues on server 1, around 5 out of 20 users experiencing this issue on server 2.

    We use a combination of folder redirection and old school roaming profiles, no FSlogix or UPDs.

    We have tried every suggestion out there, ADAL and WAM registry entries, rebuilding outlook profile, clearing credential manager, reinstalling Office, rebuilding local profile and V6 profile, we even built a brand new server and the same issue occurs.

    Been tearing my hair out for months on this going back and forth with Microsoft support trying to find a solution, so far nothing really works.

    At the moment we have server 2 restricted for logins and we increased the resources on server 1 to smooth the performance as its handling all of the users until we can resolve this.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-09-26T12:25:25+00:00

    It is different because it seems that windows server 2019/2022 includes Web Authentication Manager or Web Account Manager, this component is not included on windows server 2016 or earlier.

    Regards,

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-09-26T10:29:22+00:00

    Hi,

    we use regular user profile disks and we also encounter this problem.

    And we arent the only ones

    Was this answer helpful?

    0 comments