This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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 all,
I just created a Microsoft support request through our distributor. MS support responded with extra questions: I provided information and a link to this discussion. I'll keep you all posted.
I will be working on this issue tomorrow morning and attempting to downgrade Office per these findings. I will let everyone know how it goes.
Have completed testing with a newer version that goes back to around March this year. Version 2301 - build 16.0.16026.20200 does not seem to be affected by this bug and can be considered production ready.
Office Deployment Tool configuration file:
<Configuration>
<Add OfficeClientEdition="64" Channel="Current" Version="16.0.16026.20200">
<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>
Downgrading FSLogix did not work for us, so we're considering downgrading Office to be the fix for now. Office auto-updates have been disabled and all future updates will be processed manually and tested before mass deployment.
It's interesting that going back to the March version doesn't seem to exhibit the problem, as from what I've read for a lot of people on forums etc. the issues did start around March time. We don't appear to be having the problem as frequently at this stage as others on here, so it wouldn't be worth us downgrading.
If you felt like it, and had the time, I guess you could install subsequent updates from March onwards one at a time to see if you can pinpoint which update caused the problems to start occuring.
I sure wish Microsoft would hurry up and fix the bug though.
Just to add ours to this but we have the same issue....always random people however we find simply bouncing them onto another server fixes the issue (albeit temporarily) so I would agree that it's some sort of authentication issue however I tested the same environment using a Volume Licence install of office (instead of the click to run) and have had no issues in testing however we don't have a paid for Volume Licence to continue using this version but having worked at MSP's for 20 years I've found a lot of these types of issues (including one's we've had recently whereby it shows random users as not licenced when they are) is down to the Office click to run program and Microsoft have never fixed it so we've always put the Volume Licence copy of office on customers servers and never get these types of issues but I work for internal I.T now so we don't have a licence to use full time.
Unfortunately (like I suspect a lot of you) we can't keep a user "not working for a day or two" while we do some background digging on it as our staff need to be able to work so although bouncing them fixes the issue when then in fact remove all evidence of the issue for troubleshooting.
Hi everyone,
Does anyone have more information on this 1001 issue?
In the meantime, we have found another temporary fix so that you don't have to delete the entire user profile (saves a lot of work).
Please note that these folders cannot be deleted while the user profile is in use/when the user is logged in.
Regards.