Operating system
Windows
Joplin version
2.10.19
What issue do you have?
I have exported my notebook to JEX file which resulted in 7GB. I then did a clean install of the latest version 3.2.13 and tried to import the JEX file in. After an hour or so the import fails with error "Missing required property: type_:". I since have tried it multiple times and the error remains.
I thought that it got to be something with the latest version so I reinstalled 2.10.19, but the import fails again!
I've turned on debug mode, but there's nothing useful in there!
What should I do?
Is there any additional information in the console? joplinapp.org/debugging
I'm uploading the log files
debugconsole.log (102.4 KB)
log.txt (28.4 KB)
Thanks, but unfortunately the log doesn't show any information regarding this error. I see if I can replicate it here and add a proper error message. You'd want to know what file exactly is failing so that you can exclude it but the log doesn't give this info at the moment
What can cause a file to malfunction? something like newlines CR LF? Maybe if you can tell me I can extract the JEX into its files and do a global replace, since the error does not poinpoint which file is at fault
Actually it looks like you have an empty file in your archive, because after the second colon it should print the file content but in your case it's empty. So maybe search for an empty file or a particularly small file. The JEX file is a tar archive so you can rename it to tar and extract the files.
I'm going to create another release of the desktop app that will also print the filename, which will help find it. It will be available within the next few hours
Could you please give this release a try and see if that helps?
I've just downloaded and will try. it'll take an hour or so. I'll let you know. thank you!
Gotcha! the new version spat out the filename! What should I do next? Untar JEX, delete the file in question, and tar it again?
Yes that would work. Also would you mind sharing that file that wasn't working? And is it a .md file? It's surprising that it ended up in the archive.
I opened the jex file with 7zip and located the file in question; a 0 size md file. Then I thought to check for other 0 size files and I found thousands. I then did an in-archive delete of them using 7zip. I then set to import the archive.
After many hours it ended up importing 905 notes out of the 30K originaly.I don't know, something is off. Fortunatelly I have the original .config directory backed up so I haven't lost anything. I will try again and let you know. I'm also trying to upload here such a file of 0 size but I'm getting error "sorry the file you trying uploading is 0 size" something
Looking at the original.config directory, I find many files under the resources folder of 0 and 1K size. Can I safely delete them and then export the notebook to jex file to try again?
Also how can I find the empty files if any inside the notebook from the Joplin menu?
You don't need to delete the files in your config folder and probably shouldn't as it might break your setup. The problem in your case is that the metadata was 0 even though there should have been something even for a 0-byte resource.
If you export again a JEX file does it always create these 0-byte files? Also is it possible that your drive is faulty? Do you have an antivirus running?
What does 0 metadata mean? Is that info stored in the database?
I have an antivirus on, but it hasn't created a problem in older jex exports/imports.
Is there a way to purge the dataabse of empty metadata/file before exporting?
Right now I'm doing again an export with the latest joplin version and will try again
There's no such thing as 0 metadata. If the entry is in the database it's going to be exported as a non-zero byte file that will contain things like title, creation date, etc. even if the content is empty.
Same for empty resources (for example an empty text file) - there would be an empty "blob" (which is the resource raw content) and that's fine as well as a non-zero metadata file that contains the mime type, file size (0), etc.
So the empty .md files you see is an error and should not happen.
Maybe try to run a chkdsk on your disk too, just to be sure it's really not faulty?
Can I inspect the database.sqlite for corruption? Which tables and fields should I look for that could be problematic?
If the app can open it, it's not corrupted. It's during export that it seems there's a problem
Success! At last the import succedeed and all note were recovered! Thank you Laurent for your help!
So exporting the notes again worked without having to do anything differently?
The only difference is that I exported them with the latest 3+ version and then re-imported them from a clean slate, rather than exporting them with version 2.10.19 which was producing the problematic jex.
