Forum Discussion
Error when logging in to Microsoft 365 on terminal server
Hello,
Our users always get the error "Something went wrong [1001]" when they log on to the terminal server in the office.
Exact error:
Correlation Id: ef49199c-b608-4072-ad5d-baf4cbf7974b
Timestamp: 2023-12-18T08:13:06.000Z
DPTI: 73973fd5b9d2753a457aaf864c9888b1c8da5765dad4214810fb6394a21243aa
Error Tag: 62ubh
Error Code: 0
We have already set Enable ADAL to 0 in the registry, executed the OLicenseCleanup script and run the following Powershell command already provided by Microsoft:
if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) { Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown } Get-AppxPackage Microsoft.AAD.BrokerPlugin
13 Replies
It worked for a little while now but the same error returned now. Does anyone have any other ideas?
- We are getting the same error with no resolution.
The fixes provided by Microsoft do not work. Please try cached credentials, make sure system date and time
Hi Ottmin,
here are some suggestions that might help:
Reinstall the Office 365 application:
Uninstall and then reinstall the Office 365 application on your Remote Desktop Services server. This could resolve any issues related to the application itself.Check for updates:
Ensure that the Office 365 application on your Remote Desktop Services server is up to date.Clear AppData: Close all Microsoft applications, navigate to the AppData folder (C:UsersyourusernameAppDataLocalMicrosoft), and move the OneAuth and IdentityCache folders to your desktop. Afterward, restart Outlook and sign in again.
Outlook 365 application error 1001, mail is not syncing - Microsoft Q&A
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.If the post was useful in other ways, please consider giving it Like.
Kindest regards,
Leon Pavesic
(LinkedIn)Unfortunatly this did not work.
However I tested using the credentials in another user and could log in to for example Excel.
So it has to be something with the users.
Hi Ottmin,
thanks for the additional information.Here is additional suggestion to try:
Clear the OneAuth Data:
Navigate to the %localappdata%MicrosoftOneAuthaccounts folder on the affected user's machine. Identify files with GUID names and try renaming or moving them to a different location. Afterward, attempt to sign in again.
Another account from your organization is already signed in on this computer - Microsoft 365 Apps | Microsoft Learn
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.If the post was useful in other ways, please consider giving it Like.
Kindest regards,
Leon Pavesic
(LinkedIn)
