[German]There are reports that users of the Office 365 suite are suddenly getting error 1001 when trying to log in. An IT service provider contacted me about this because this was occurring with their customers. However, there is a workaround on how to fix this.
Login error 1001
The logon error 1001 "Something went wrong (1001) seems to occur more often. For example, I came across this error description in this Microsoft forum post, which includes the dialog box shown below.
Below the above visible and "very purposeful" hint that "something went wrong", there are also hints for troubleshooting, but they are not that helpful either. The cause is probably mostly invalid OAuth entries or in the IdentityCache of the user profile, but this can be corrected by deleting the folders.
Outlook error in MS365 with Fslogix
German blog reader Maximilian contacted me on Facebook the other day because a customer was experiencing the problem outlined above. The affected users get error 1011 when trying to log in to Microsoft Office 365 or Microsoft 365. To this Maximilian wrote:
have at a customer with multiple session hosts, with M365 and Fslogix, the error that Outlook brings this error.
Here is also a possible solution, which has worked for us 4x out of 10.
The error comes sporadically with single users.
Maybe someone else has the error.
First of all, thanks for the tip – I'll pass it on here in the blog. Anyone from the readership who is affected by this error? If so, does the following solution help, or are there other approaches?
Solution: Delete authentication folder in profile
Maximilian still sent me the link to the article Office 365: Sign in Error 1001 on NewPaltz, where the following solution was outlined for the login problem described above:
- Close all open Office applications, including Teams.
- Then navigate to the following folder and delete or move the OneAuth and IdentityCache folders to another location.
The folders in the following path are hidden and may need to be allowed in Explorer by viewing system folders:
The same solution is proposed within thjs Microsoft forum post. This should clear the OAuth credentials and the IdentyCache. When the Office applications are then restarted, they should request a new login, which will then (hopefully) be performed without errors.
Addendum: Microsoft has confirmed the issue – see Office 365 Sign in Error 1001: Microsoft releases a workaround
Cookies helps to fund this blog: Cookie settings