Problems with Mobile One Note App -

Question

Problems with Mobile One Note App -

Sandra Leon 0

Sign In link takes me to a Microsoft sign in page. The screen immediately displays and error. "Something went wrong. [9hehw]". The screen doesn't display any fields to enter login ID or password. The message advises me to contact my administrator (I'm an ordinary person, no a corporation).

On my phone, I dropped the cache and data, uninstalled the OneNote application, then reinstalled it. My notebooks can be found, so no problem there. However, the message remains: "Working offline." No sign in is possible, because of the Something went wrong error message.

Here are more details for the sign in error message I'm currently seeing:

Message: Access denied for the resource

Tag: 9hehw

I have the same issue mentioned in this thread. Please advise how to fix this problem. I have used this app without problems for more than 10 yrs. If it persists on Friday, September 4th, 2026; I will need to terminate my subscription to MS 365 and get another notetaking app. Need it fixed ASAP.

0 comments

1 answer

Your answer

Answer 1

Hi Sandra,

Thank you for reaching out.

I’m sorry for the disruption, especially after you have already cleared the app data, uninstalled OneNote, and reinstalled it.

Please try signing in with the same Microsoft account using the OneNote desktop app on a Windows PC or Mac. If sign-in works there, allow your notebooks to synchronize completely. Then restart OneNote on your Android device and check whether the “Working offline” message disappears.

If the desktop app also displays “Access denied for the resource” with tag 9hehw, please reply with the exact error shown. Please do not remove any notebooks containing changes that have not yet synchronized.

I would also like to acknowledge that there is an ongoing incident affecting some users when utilizing multiple Microsoft 365 services. This incident may be contributing to the sign-in and synchronization issues you are experiencing.

User's image

The engineering team has isolated a common failure pattern across affected requests associated with authentication and protocol connectivity. They’re analyzing service telemetry to identify the underlying source of impact and validate potential remediation options. In parallel, they’re continuing to assess the scope of impact and monitor for any additional affected scenarios.

I hope you found the answer helpful, and I would greatly appreciate it if you could mark it as accepted. This helps highlight the solution for others who may be searching for similar information in the community. Your contribution not only supports fellow users in finding the right guidance more quickly, but also helps build a more resourceful and collaborative space for everyone.

Thank you for your kindness and contributions to the forum. Wishing you a great day ahead.