Using Classic Outlook on Windows for personal email, calendar, and contact management
Hi Grim,
Unfortunately no other solution has been found yet. a downgrade is necessary and since then we have had no more 1001 errors.
Regards
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.
Hi Grim,
Unfortunately no other solution has been found yet. a downgrade is necessary and since then we have had no more 1001 errors.
Regards
HI Ian,
This is also only happening with additional account in outlook?
We never have the issue when there is only one account mapped in the outlook.
thx for your reply.
Kind regards
We had this problem about 2 months ago for a couple of weeks and then it stopped for us on it's own but last week it's come back however we have changed the version and release of Office on our RDS servers without success BUT we have 6 RDS servers, 4 of them are covered by FSLOGIX and a broker
and 2 are independent using local profiles and the one's using local profiles never had ANY issues so certainly for us it looks all down to FSLOGIX so i disabled the ability to roam identities, ran GPUPDATES and then rebooted all and straight away all worked fine for the past 6 days. We'd had a few residual people having to log back in when opening Outlook but then once logged in they've been fine.
It seems different setups and different people may have different issues but in a 2022 RDS scenario with FSLOGIX profiles and Office 365 app for business (or Enterprise - any version) then this has fixed it for us (at least for now)
I did also run the 2 commands to re-register these packages but i didn't run these on the non-FSLOGIX servers and again they've had no issues so i think we can discount these as being the fix for us (unless they fixed something that the FSLOGIX servers had broken)
Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown
Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown
Dear Stephan,
We have the same exact scenario with one of our customers where this is happening with additional mailboxes.
So not with the primary mailbox.
Did you find any ohter solution then downgrading the office? Is this still working as expected after the downgrade?
Thanks
@JMSA85 Can I just confirm that you're simply just running the WPJCleanUp script on every logon per users. Is that how you've set this up?
We have this issue on a number of RDP solutions and would love to finally solve it.
Just as a heads-up, WPJCleanUp has done wonders so far, did not encounter other 1001 issue after running it in users sessions.
@WhoaDukeOfAwesome, I did not create a script yet, I started by letting a shortcut on the desktop pointing to the exec and instructed our users to run it if any 1001 issues. I was just being safe, as that could be quickly removed if that created any other side issue.
Now, I would deploy it at a larger scale by simple running the executable in user context, at logon, and only a single time as it doesn't need to be run at every login if BlockWorkplaceJoin registry has been properly set up.
OK, thanks. One other thing, after applying this, does it affect anything on the RDP servers? For example, are the users forced to log onto their O365 account upon every RDP session?