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-26T18:32:12+00:00

    We are also recently getting this same issue with same error 1001.

    Here are some facts about our issue :

    Rebooting the whole server currently was fixing the issue for some times.

    This issue was affecting sometimes many users sometimes wholes users.

    For Outlook we also experienced this message :

    Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed.

    While troubleshooting and since this is for an RDS in production and reboot every time isn't a very good definitive solution I still at least also found what it could be related in our environment and what was also working as an workaround:

    In powershell we runned :

    Get-AppxPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

    This force to register all modern application to register using the system xml manifest file.

    This said, It is probably not required to register whole list of all Application, I just didn't had chance to find those who are directly related to our issue but at least this workaround for us isn't to delete complete profil or reboot a whole server.

    We'll probably open a case with Microsoft directly for this also, since this issue seems not to just be related to our environment.

    FYI: here we are also using RDS 2019 server with O365 and User profil Disk.

    Thanks,

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-09-26T17:15:53+00:00

    Just to be sure, with the very last version of FSLogix (which has the issue)

    • Did you have updated adml/admx files ?
    • Did you have enabled the following parameter : Roam Identity

    Regards,

    • Adml and admx files were updated not exactly with the latest but the latest ones from sometime in August (don’t know exact version).
    • roamidentity was enabled with value 1.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-09-26T15:11:36+00:00

    Just to be sure, with the very last version of FSLogix (which has the issue)

    • Did you have updated adml/admx files ?
    • Did you have enabled the following parameter : Roam Identity

    Regards,

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-09-26T14:02:37+00:00

    Hey everyone,

    I've been dealing with this issue for over 3 weeks now on an entirely new RDS deployment but think we may have "fixed" it. Here's my setup details, troubleshooting steps, and solution.

    Setup

    • 4x RDSHs running Windows Server 2019 Datacenter, 1x RDCB
    • Latest version of FSLogix (was 2.9.8612.60056 at the time)
    • Office 365 version of Office, x86, deployed via Office Deployment Tool (sharedcomputerlicensing=1)

    Symptoms and Troubleshooting

    • Office would not remember people's credentials at random intervals. Some people were fine for a few days before asking again, others would need to enter their credentials every login.
    • Sometimes, when the user authenticates, they'd be greeted with "Something went wrong, Error 1001" message with no more helpful details. Closing the error and Office, then reopening, they were fine to continue working.
    • Easiest way to tell it wasn't working was to open Word or Excel > Account and see account had "Fix me" button to sign in again. Outlook would open most of the time even if Word/Excel said "Fix me" but would eventually stop opening until credentials were entered at some point.
    • Creating new FSLogix profiles for users would temporarily alleviate the issue for a few days but it would always come back.
    • Tried newer RoamingIdentity reg key for FSLogix but made no difference.
    • Tried Office 2019 VLSC instead of Office 365 Office but made no difference.
    • Users that did not use FSLogix were not affected by this issue.

    Solution (Workaround until they fix it) SEE EDIT BELOW

    We eventually found another client we support with the same exact setup that did not have the issue, noted their FSLogix version, and downgraded it on all our RDSHs, and the last 2 days, no one has reported being asked for credentials again. There's still time for it to mess up but so far, it's looking positive.

    We downgraded to FSLogix version 2.9.8228.50276. This was our fix/workaround until Microsoft figures their stuff out.

    Hope this helps!

    EDIT: As of this morning, users started getting prompted for credentials again and worse, got stuck in Error 1001 loops when opening Outlook. I guess this didn't fix things...

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-09-26T13:31:08+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

    I'll give this a go tonight....i know in the past when we've had mass issues with Licencing or Authentication issues at clients (i don't work for MSP's anymore) that installing the Volume Licence edition of Outlook on RDS servers has got rid of pretty much every problem so i suspect you're right in it being a click-to-run issue

    Was this answer helpful?

    0 comments