Using Classic Outlook on Windows for personal email, calendar, and contact management
Hello Stephan,
For us the problem is with users with one mailbox as well as with multiple mailboxes. As with users with a personal mailbox and a shared mailbox.
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 Stephan,
For us the problem is with users with one mailbox as well as with multiple mailboxes. As with users with a personal mailbox and a shared mailbox.
We see that when we clean up the profile (vhdx) for a temp fix and reconfig the Outlook profiles the WAM authentication is forced over ADAL while the ADAL registry keys are in place to use ADAL. Also, this only seems to happen if multiple mailboxes have been added in addition to the primary mailbox (not shared mailboxes but additional "user" mailboxes).
Does anyone else experience this too?
We also had three different cases open between April and now.
However, Microsoft technicians were unable to solve the problem.
We use
Windows 2019 1809.17763.4851
Office 2308 16731.20234.
FSLogix
At first I suspected there was a problem with our infrastructure. However, replacing the firewall and changing the virus protection didn't help.
We also had problems with Edge login. However, that could be solved.
I suspect there are problems with the accessibility of the Exchange servers (information stores) in Office 365. Overload
At the company where i am 1 of the system managers are also having this problem with the 1001 error.
Mostly after someone has changed his/ her password.
We have this on our Microsoft RDS environment with roaming profiles
At the moment we use the solution where you remove the AAD Broker plugin.
After restarting outlook it works again and the user can refill in the password again.
When working with roaming profiles to remove the AAD Broker Plugin let the user logoff, login **** administrator to your server with the user profile disks (UPD) check which upd is from the user with the problem.
You can do that with a program called sidder. than mount the UPD from the user and remove the AAD Broker Plugin file from the appdata folder (UserName)\Appdata\Local\Packages
Than eject the profile disk and let the user login to the server again and check if outlook works again.
Hi Jay,
Glad you opened a case!
Could you let us know from time to time if you learn anything new about the problem?
For us, authentication and error 1001 seem to be getting worse every day.
Thank you in advance.