Outlook 365 app error 1001 on RDS environment ( FSLogix)

Anonymous

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

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

Anonymous

2023-10-02T14:33:53+00:00

Have completed testing with a newer version that goes back to around March this year. Version 2301 - build 16.0.16026.20200 does not seem to be affected by this bug and can be considered production ready.

Office Deployment Tool configuration file:

<Configuration>

<Add OfficeClientEdition="64" Channel="Current" Version="16.0.16026.20200">

<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>

Downgrading FSLogix did not work for us, so we're considering downgrading Office to be the fix for now. Office auto-updates have been disabled and all future updates will be processed manually and tested before mass deployment.
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2023-10-02T15:22:52+00:00

Have completed testing with a newer version that goes back to around March this year. Version 2301 - build 16.0.16026.20200 does not seem to be affected by this bug and can be considered production ready.

Office Deployment Tool configuration file:

<Configuration>

<Add OfficeClientEdition="64" Channel="Current" Version="16.0.16026.20200">

<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>

Downgrading FSLogix did not work for us, so we're considering downgrading Office to be the fix for now. Office auto-updates have been disabled and all future updates will be processed manually and tested before mass deployment.

It's interesting that going back to the March version doesn't seem to exhibit the problem, as from what I've read for a lot of people on forums etc. the issues did start around March time. We don't appear to be having the problem as frequently at this stage as others on here, so it wouldn't be worth us downgrading.

If you felt like it, and had the time, I guess you could install subsequent updates from March onwards one at a time to see if you can pinpoint which update caused the problems to start occuring.

I sure wish Microsoft would hurry up and fix the bug though.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-10-02T15:30:48+00:00

I will be working on this issue tomorrow morning and attempting to downgrade Office per these findings. I will let everyone know how it goes.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-10-02T15:37:15+00:00

I wouldn’t expect that to get any better. Microsoft has little incentive to devote resources to these cheaper (and what they consider) legacy options, when the have recurring revenue on new products like Azure Virtual Desktops.
Was this answer helpful?

0 comments No comments
Anonymous

2023-10-04T06:44:52+00:00

Hi Thomas

thank you for the solution, This is just a confirmation your solution works perfectly, I just changed yesterday our servers with the office in march Patch, after a clean install from the office and a new installation from the XML file the error was gone.

Thanks Again

Giuseppe
Was this answer helpful?

0 comments No comments