RTF reader failed loading doc. .../.../..6rtf

[robert_lazet]

I love to write in Scriv ever since 6 years ago. But yesteryear it started to give problems.
So I am writing in word now…wanted to go back to Scriv. Started a new novel, after 14 chapters I saved it and went to bed.
This morning I wanted to start it up again and it came with…

Win 10

Document Loader
Could not load document
RTF reader failed loading doc. xxx/xxx/xx…6rtf
Error unmatched { in rich text file. (The accolade was in between to high marks)
Question came if I wanted to go on anyway…With Yes the txt is loaded but unable to
manipulate the cursor.

Now I saved the file on an usb stick. That might be a reason.
If I closed the Scriv prog and starts it again, It comes with the same failcode.
If closed and use recent project’, from a another location on the HD, there is no problem.
If closed and use open other project from usb stick…then the problem occurs in the now problemfile.

[archetypo]

I’m having the exact same problem. I’m only working on one platform, though. (Windows 10)

Message reads: “Unmatched ‘{’ in Rich Text Format”

No matter what I do the file is closed automatically.

Saving it under a different name does not help.

Restarting the computer does not help.

Any ideas

[steveshank]

If Scrivener cannot load a simple file, the most likely reason is that the file was corrupted. For example, if you bought a book, and looked inside, and there were ink marks all over the text making it impossible to read, then the issue is not with the English language, but with later corruption of the book.

If you save a document to disk, then everything must be saved exactly right. Each bit is precise. Therefore, you want to have:

1. good solid hardware
2. Save only to your internal drive. The most reliable device you can. Do not save directly to an online service or a USB drive, particularly not a thumb drive which are notoriously unreliable.
3. After it is saved, you can copy somewhere else.
4. Make multiple backups on another media.
5. backup your backups

One of the Techs here presented a possible recovery path for you. It was so useful, I copied it.

What I would do is make a copy of the “search.indexes” file one directory level up from where you were, then open the copy in a plain-text editor (Notepad++ would do well, it might be a bit messy in Notepad). Search for the binder title of the item you wish to recover. If all is well you should find a relatively recent version of the text as it was saved into the search index when you last manually saved. You’ll just need to copy and paste it from within a little simple markup. Formatting will be lost, since this is a search index and not a word processing storage format.

Of course if you not only saved to an unreliable device but also didn’t do saves during the writing process, then the file is likely gone.

Something should be able to be recovered from your backups.