Error Code: 0xE0000007 in OneNote

Anonymous
2017-09-01T19:18:46+00:00

I have one section of one notebook in OneNote that keeps coming up with Couldn't Sync and showing the Error Code: 0xE0000007. I have gone through all the steps shown online:

Open the OneNote online, then open the Notebook section and use 'Open in OneNote' to open it on my desktop. Then try to sync - failed

Copy (not Move) all of the notes in the affected section to a newly minted section, delete the original section and sync the new one - failed

So I tried making some minor changes in the section, re-synced, got the 'Couldn't Sync' error, but when I check back online all of the changes I made have synced. Why am I getting this error?

Microsoft 365 and Office | OneNote | For home | Windows

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.

0 comments No comments
Answer accepted by question author
Anonymous
2017-11-10T23:36:04+00:00

Hello --

We have posted a self-help article that may help you solve this problem.  It is titled "Resolve the 0xE0000007 error ("We ran into a problem syncing your notebook") in OneNote".  Here is the link to the article.

Denise

OneNote Team

Was this answer helpful?

0 comments No comments

77 additional answers

Sort by: Oldest
  1. Anonymous
    2017-11-08T07:36:09+00:00

    I cannot open my password locked page cos of this error.

    this is affecting onenote app on my android, iphone, ipad, and the store app on my windows laptop.

    it doesn't affect webpage onenote or the office onenote 2016

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-11-08T16:30:42+00:00

    I'm unable to get to new notes taken. I've tried the "close and re-open" and copying the problematic section to a new section.  Now on iPad won't even load the section (spins forever) and gives the Error code: 0xE0000007 on the laptop.  15.38 codebase.

    What is the ETA on a fix, MSFT?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-11-11T00:23:30+00:00

    Will this issue be permanently fixed by Microsoft soon?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-11-12T16:56:03+00:00

    You may ask, but ... This issue exist at least for 6 months now and Microsoft hasn't done much to fix it, besides writing an incomplete "self-help article".

    Was this answer helpful?

    0 comments No comments