Using Classic Outlook on Windows for personal email, calendar, and contact management
Hello,
no new cases since 02 October.
We just pass the M365 updates
fingers crossed
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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) :
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 :
Using Classic Outlook on Windows for personal email, calendar, and contact management
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.
Hello,
no new cases since 02 October.
We just pass the M365 updates
fingers crossed
Hi Steven,
I created the MS support ticket regarding one of our (multiple) customers who are experiencing this issue.
The customer's environment:
RDS: 2 x Windows Server 2019 Version 1809 (OS Build 17763.4851)
Microsoft FSLogix Apps: 2.9.7979.62170
Microsoft 365 Apps for enterprise - 16.0.16731.20234
For now, I have not changed anything (the advised MS workarounds) because we had less customer complaints in the past few days. I suppose Microsoft fixed the issue in the backbone or in the Microsoft 365 Apps (security) update of October 10?
Only one customer seems to keep experiencing this issue.
Hi AFABIA,
For now, I have not changed anything (the advised MS workarounds) because we had less customer complaints in the past few days. I suppose Microsoft fixed the issue in the backbone or in the Microsoft 365 Apps (security) update of October 10?
Only one customer seems to keep experiencing this issue.
I'll keep you posted.
Hello Guys
My update since 1 Week and more no more issue with 1001 Error after we downgraded the Office.
But i forget one important point pay attention if you use the config.xml on the :
16.0.16026.20200 -> MS Teams is not included ;)
Unfortunately, I tried the NoDomainUser key but I was still able to get the error 1001 after deleting these folders and opening up outlook:
The 4th step provided by Microsoft support to you appears to be contradicting with the "Roam Identity" key. Excluding the AAD Broker Plugin and Token Broker folders defeats the purpose of the "Roam Identity" registry key, isn't it?
To add to this, you appear to still be using older version of FSLogix.
Lastly, to everyone else, after FSLogix upgrade and enabling Roam Identity, we've experienced less cases of error 1001 but we still get it like once a week. Fix is to delete the 5 folders mentioned above and sign them out and back in to the RDS.