Cannot save any project all of a sudden

[Andrea Instone]

Dear Julian,

I only updated Jutoh a few days ago and all went well. But now I cannot save or sometimes even load projects. The help panel pops up and telling me what to do about a corrupted file (which confuses my even more as I don't use any cloud service).

I tried importing the file into an new project (nothing happens, nothing is being imported). I made a new epub from the manuscript I want to work on in Jutoh and made it a new project. It worked nicely and even said all was well - I used übersetzen and überprüfen (translate or convert and check) and it said no mistakes.

And then one chapter could be opened and all of the others could not saved and the whole project was corrupt again.

I tried again. I removed the check from temporary files, hoping that maybe not having it, could help.

I deleted the chapters that would not open, made new ones and copied the text piece by piece.

I got this in the log, but cannot understand what goes wrong.

01.03.2025 17:08:09: pxObjectStore::HasTable - SQLITE_IOERR_FSTAT[1802]: disk I/O error
01.03.2025 17:08:09: pxObjectStore::RowExists - SQLITE_IOERR_FSTAT[1802]: disk I/O error
01.03.2025 17:08:09: pxObjectStore::RowExists - SQLITE_IOERR_FSTAT[1802]: disk I/O error
01.03.2025 17:08:12: pxObjectStore::RowExists - SQLITE_IOERR_FSTAT[1802]: disk I/O error
01.03.2025 17:08:13: pxObjectStore::RowExists - SQLITE_IOERR_FSTAT[1802]: disk I/O error
01.03.2025 17:08:16: pxObjectStore::RowExists - SQLITE_IOERR_FSTAT[1802]: disk I/O error
01.03.2025 17:08:16: pxObjectStore::RowExists - SQLITE_IOERR_FSTAT[1802]: disk I/O error
01.03.2025 17:08:17: pxObjectStore::RowExists - SQLITE_IOERR_FSTAT[1802]: disk I/O error

I am rather desperate and don't know if the software I use for writing and making the raw epub is the culprit or me or if a made a mistake while downloading the latest jutoh?

Help please, I am getting a tiny bit desperate right now :)

All the best for now!

Andrea

[Julian Smart]

Hello Andrea,

Sorry to hear this. It sounds as though you may have been using Jutoh in a cloud folder, without Jutoh being aware of it. Syncing can cause corruption of the file, which is not cloud-folder friendly. You can tell Jutoh which are cloud folders via Preferences/Projects/Match pattern.

Unfortunately if the project is corrupt, that won't help. You can rename the .jutohbak file to a .jutoh file, copying it to a location you know definitely isn't a cloud folder, and opening it, but this backup is overwritten every time you open the corresponding .jutoh file and so may also be corrupt by the time you realise there's a problem.

If all else fails and you don't have a backup, you can create a new project and import the Epub file, although it may require some formatting to get back to where you were.

Make sure any projects you are editing are either definitely not in a cloud folder, or Jutoh knows it's a cloud folder as above. Then it will edit the file in a temporary folder and copy the edits back to the main file when the project is closed. There's a slim chance Jutoh will accidentally use a cloud location for the temporary edits, but you can see where it's currently editing via Project Properties/Metadata/Project/Information/Folder and check this is not a cloud folder. If it is, then you will need to ensure your project is definitely not stored in a cloud folder.

Best regards,

Julian

--
You received this message because you are subscribed to the Google Groups "anthemion-jutoh" group.
To unsubscribe from this group and stop receiving emails from it, send an email to anthemion-jut...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/anthemion-jutoh/87cdcad0-203f-4a9e-9dbb-0e7ed6ca44a0n%40googlegroups.com.

[Andrea Instone]

Somehow my answer got lost? Now I forgot what I wrote :D

No cloud in sight, never use them. Trying again now. Will do it live in here.

Made a new epub, deleted the project, opened new epub in Jutoh as new project. Had a look at every chapter, all there, all can be opened.

Oh, I remember. I used a saved style made from the first, then corrupted file - might this be my stupid mistake?

[Julian Smart]

Hi Andrea,

Hopefully you got my reply to your private email. Glad to hear the new project is OK. I suppose if you imported styles from a corrupted project file it might cause problems, but I wouldn't have thought so because the data itself is separate from what can be corrupted (the containing SQLite file) and if the styles had contained corrupted data it probably would have crashed Jutoh rather than caused SQLite errors.

Regards,

Julian

To view this discussion, visit https://groups.google.com/d/msgid/anthemion-jutoh/0209732d-b942-49f5-9d39-ff9e6fb77976n%40googlegroups.com.

[Andrea Instone]

Did not get the eMail, will have a look in the junk file :)

But right now it seems to work so I think it must have been the other software that caused the problem.

I wish you a very nice evening, perhaps again with a glass of wine and a good book!

Thanks a lot as usual and all the best, 

Andrea

[Andrea Instone]

Hi again,

the same mistake again and again and still no cloud in use. I wanted to replace one style with another and got the message that the files could not be saved. And now I think if it might have to do with the program that made the epub I import to jutoh? (If it is the other program I already know that I won't get any help from them :D )

But what can I do to work on the file? I am a bit lost ...

Thanks for your help as always

Andrea

[Andrea Instone]

Edit: I tried starting a new project from scratch and I could not save it, got the same message. I tried to save it where all my novels are saved - not a cloud.

[Julian Smart]

Hi Andrea,

Sorry to hear this. Do you think you could let me know the drive location where the problem is happening? Can you maybe try a different location? Some screenshots would be helpful - you can send them to jul...@anthemion.co.uk.

Thanks,

Julian

To view this discussion, visit https://groups.google.com/d/msgid/anthemion-jutoh/f98edf8d-33c5-4c3c-a1a1-fcd4b608f7abn%40googlegroups.com.