Using Classic Outlook on Windows for personal email, calendar, and contact management
7 reports of the issue today from 7 different people, including 4 who have never had the issue before.
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.
7 reports of the issue today from 7 different people, including 4 who have never had the issue before.
We're getting regular reports of the issue again now.
When a user changes their domain/Microsoft logon password they always get the 1001 error/yellow exclamation mark the next day without fail.
We advise those users to switch to webmail for the rest of the day and try Outlook the following morning. Often Outlook will be working the next day, but not always and we then have to go through the usual procedures to fix.
We're also still seeing the issue occur at random where no password change has occured. Sometimes signing them out of their RDS and signing back in fixes it, but again not always.
It's also still affecting some users more than others.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
I think we'll all have to continue doing what we have been doing in terms of fixing it (temporarily) for users.
Personally I don't believe AV is the cause - we use the standard built-in Defender on our session hosts and still had the issue.
The number of reports of the issue has dropped for us. Users now seem to only be getting the issue the day after they change their logon passwords. And in most cases if they use webmail for that day and try Outlook the next day it starts working fine without any intervention.
I've heard users run into this in their computers but very rarely due to it not being a shared computer.
Thank God they finally acknowledged this. My ticket with Microsoft is asking the same logs since day one. They then ask me new sets of logs but this time they wanted AV to be removed (not disabled) from the system. Let's see how things go. :)