Fast scalable distributed SCM stopped working during send/receive

Question

I’m trying to help a translator who isn’t able to complete a send/receive for his project in paratext 8. He and I successfully did a S/R with his “notes” project and his “back translation” project (the wisdom of these being separate projects is another discussion altogether), but the main translation project gives this error:
Fast scalable distributed SCM (revision control, version control) system a cessé de fonctionner. ("…has stopped working.")
Un problème est à l’origine du dysfonctionnement du programme. Fermez le programme.
A problem is at the root of the program’s misbehavior. Close the program.
I’ve already tried repairing Paratext, then I’ve tried uninstalling it and reinstalling it twice, and the problem persists. Does anyone have any pointers on how to overcome this? A web search told me that this really refers to the mercurial version control module for python, but surely this would have been reinstalled when I reinstalled paratext, right?

Edit: I forgot to mention that this happens both with a paratext server send/receive and with a USB drive send/receive. Thus, we have no obvious way to propagate his changes out of his machine.

Publicación antigua - se muestra en su idioma original

Answer 1

wxiev4u3.djj.txt.zip (523 Bytes)

After further digging, I’ve found there are errors when verifying the project repository (see attached). Surely this is related to my problem, but I don’t know what tools are available to resolve the verification errors.
I’d appreciate any help at this point, even if it’s just an email address of someone to communicated directly with.

Thanks,

n8_in_car

Publicación antigua - se muestra en su idioma original

Comments

Unfortunately, the project’s history has become corrupted on his machine. There is no easy way to fix it besides deleting it and having him get it again via a S/R.

If the translator has no changes that he needs to S/R, then it’s fairly simple: use Project > Delete Project to delete it off their machine and then do a S/R to get it back.

If the translator has changes that they have not S/R’d yet, then it’s a bit more complicated. To keep their changes, you need to do the following:

1. Create a backup of the project on their machine (File > Backup Project to File).
2. Delete the project (Project > Delete Project).
3. Use S/R to get the project back.
4. Restore the project from step #1 into another, temporary project.
5. Use Compare Texts (Tools > Compare Texts) to compare the changes in the temporary project and move the changes to the main project.

Publicación antigua - se muestra en su idioma original

---

This is helpful. I believe he has many changes, but at least I can get his work into a temp project and see what exactly I’m dealing with. Thanks.

Publicación antigua - se muestra en su idioma original

---

I forgot to mention that if the translator created/updated any project notes, it should be safe to shutdown Paratext and copy the Notes_{UserName}.xml file from the temporary project to the main project (but the notes file for that translator, only!).
Unfortunately, any other changes (e.g. to Biblical Terms, Wordlist, etc.) will have to be re-done manually.

Publicación antigua - se muestra en su idioma original