Error importing notes from format: onenote 2010

Operating system

Windows

Joplin version

3.5.13

Desktop version info

Joplin 3.5.13 (prod, win32)

Gerät: win32, Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
Client-ID: e49a7c0aae864a14b7e48b748c96c3c9
Sync-Version: 3
Profil-Version: 49
Unterstützter Schlüsselbund: Ja
Alternative Instanz ID: -

Revision: 0c1511f

Backup: 1.5.1
Freehand Drawing: 4.2.0

What issue do you have?

I want to import some notebook files (onepkg) from OneNote 2010 but something does not work...
see screenshot ... there are a lot of errors like this in the console.
Any ideas how to fix this?

Body

  • Input format: one
  • Output format: md

Errors

Error: Malformed OneStore data: Non-zero jci field. Was 49 (in parser\src\local_onestore\common\object_declaration_with_ref_count_body.rs:35)

Location:
    renderer\src\lib.rs:50:27 (near page [None])

Screenshots

Log file

log.txt (49.9 KB)

Does the "Non-zero JCI field" error still occur if:

  1. A new, empty OneNote 2010 section is created.
  2. That section is exported on its own.
  3. The just-exported section is imported into Joplin?

Ok, I created a new empty section inside the same notebook saved it and imported it into Joplin.
It worked without any issues.

Next, I created a new and also empty new notebook and tried to import that too but got theses errors…

Thanks for testing!

If sections are exported individually from the other notebook (as .one files rather than a .onepkg file), can Joplin import them?

I just tried that and it seems that it is possible, with some loss in formating though. :face_with_diagonal_mouth:
The errors occur when I try saving and then importing complete note books…
Is there some fix for this? While it appears to be possible to import the sections individually it would be somewhat cumbersome. :sweat_smile:

Since the export was created from OneNote 2010, a workaround might be to import the .onepkg file into a newer OneNote version, re-export it, then import the just-exported file into Joplin.

The importer has previously also had issues with importing revisions. It might also help to create a copy of the notebook, clear revision history, then re-export.

There are some OneNote import-related bug fixes in the latest pre-release (see pre-releases), but I don't think any are related to the issues reported above.

I will play around a bit with this method for the individual sections and see how it goes.
I will also take at the idea about the revisions…
Importing into a newer onenote version is not on the table since 2010 was the last version that worked only locally. Since version 2013 it requires a MS account… :face_vomiting: So, no thanks.
Thanks for the help.