I want to report a problem and I’m panicking big time.
- I launch SCRIVENER and then chose my ms from “File>Open Recent"
I then get
- “Warning: This project was either not closed properly or is currently open on another machine. Please note that if the same project is open on two machines concurrently, data could be lost. Before the project can be opened, its search strings need re-synchronising. This process could take several minutes. Continue?”
- I click OK
- Synchronising Search Strings then starts.
- SCRIVENER crashes (aka “Quits unexpectedly“) while it’s doing this.
I click the relaunch button and then I’m back where I’m started at step 1. I cannot get back into my ms.
Like most of us, I suspect, SCRIVENER contains everything on this project. And I’m not being picky about it: it has until now - for years - been absolutely rock solid.
I’m running SCRIVENER 1.5.1 with OS X 10.5.6 on an Intel MacBook with 1 GB of memory.
Just before all this I had been scanning some of the entries in my RESEARCH folder in Scrivener. I deleted one of them as it was a duplicate. Nothing out of the ordinary.
What to do?
Zip up the project and send it to me at support AT literatureandlatte DOT com. Remember that even if the file is irretrievably corrupt (which I doubt), the contents are all still safe (ctrl-click on the file in the Finder and select “Show Package Contents” to see what I mean). It sounds like a bug in the synchronise search strings code, though, so it should just be a case of me seeing what it is to enable it to run through, then sending the fixed file back to you. There is a way to force synchronise search strings not to happen, too, but it’s best to let me look at the project first - I’ll tell you how to force things if I can’t fix it quickly.
Thanks and all the best,
Credit (and praise, adulation even) where credit’s due.
I sent the file to Keith at 5.40pm on May 18th. Within 40 minutes (!) he had opened the file, identified that it wasn’t a Scrivener issue, found out what and where the problem was (a web page in Research that crashes Safari) and emailed me back instructions on how to solve it. Which I’ve done. And I now have my magnum opus back again.
That sort of service at that sort of speed…? I’m gobsmacked.
Keith, thank you.
If you can work that fast would you like to write the rest of the damn book for me?
Glad to help, and thank you for the kind acknowledgement here.