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-10-11T14:11:52+00:00

    I installed the 15.39 update and at first saw no difference. Digging a little further, however, I was able to get things resolved with this version.

    In recent prior builds, I would get the error 0xE0000007 and it would be associated with the notebook name (Household, Reference, etc.). I had two of my nine notebooks erroring out. With this new build, I noticed the error code now showed the sections that were a problem. Interesting observation 1: it was some old sections where the problem was occurring, not the ones with recent notes.

    Using the new information, I created new sections in the notebook for each of the problematic sections, copied all the pages from the problematic sections to those new ones and then let the sync do its thing. The new sections with copied content synced correctly. Interesting observation 2: I was getting ready to delete the old sections as the last step in the process, but after the new sections synced, the olds ones stopped erroring too. Go figure. Deleted them anyway for good measure.

    After all that, everything is now syncing correctly. I went to my iPad and with a quick refresh, those started working as well. It's not quite a perfect fix, but it got the job done.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-10-11T14:55:45+00:00

    I JUST did the upgrade to 39.  The first sync did take several minutes to complete, but it did finish with NO ERRORS!  Other than the several minutes to sync one notebook, all tests that I did completed successfully.  I made change from different devices and all synced properly.  No errors showed.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2017-10-11T17:20:04+00:00

    With much fear and trepidation, I also tried .39.

    The sync seems to be considerably slower (not syncing real time as it did before) but so far no errors.  In my case I'm just using old notebooks, instead of creating new ones.

    Not sure I like the slow sync, but it might be the price to pay to get rid of the errors??

    Crossing fingers...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-10-11T17:59:54+00:00

    Thank you Peter and the others who tested 15.39!  You inspired me to update to 15.39 as well.  I have not experienced any sync errors so far in my three notebooks.  The sync time did not seem any slower than 15.38 which was throwing errors.  I've made some changes to pages, moved pages between sections, etc. and no errors

    so far.  Crossing my fingers.  If this version includes a fix for this issue, I wish that Microsoft was more transparent about this in the OneNote for Mac 15.39 release notes since they say nothing.

    Was this answer helpful?

    0 comments No comments