User has a corrupt repository - deletes the project locally, but S&R is not working afterwards.

Question

A project for which I'm an administrator is having the following issue.

A user (who also has administror rights) had an issue with a corrupt repository. I suggested he delete the local copy of the project, then retrieve it through S&R. 

(After doing this I found this thread: https://support.bible/10403/corrupt-repository?show=10403#q10403, which confirms this is the thing to do in this case.)

However, after deleting the project, he gets a message "Unable to Send / Receive" when he tries to retrieve the project through send/receive.

The problem is not his PT account as such (for other projects he is a user of, S/R works OK), not the project in question as such (on my computer, S/R for this project works OK)

I wondered if it would help to remove the user from the project and add him back in again. However, I'm not sure what would happen to his history (editing history, assigned notes etc.) in that case.

This issue is a bit urgent, so any help would be appreciated. Thank you in advance!

Paulus Kieviet, SIL Pacific Group

Answer 1

For the record - this has now been solved. It seems to have been caused by an inadvertent shutdown during Send/Recv, and then when the project was deleted (in order to get a fresh copy from the server), it didn't get removed completely, and was still hanging around.

We're not sure which of these 3 actions eventually solved it, but this is what we did:

1. Removed the (old/deleted) project folder from the Temp Files folder [tried to restart paratext and do a S/R, but it continued to show the Unable to Send/Recv message.

2. Shut down the computer and restarted Windows

3. Started Paratext while holding Shift in order to reset the Paratext settings

That eventually worked and so the user is up and running again.

Related issue...? We noticed that the main "My Paratexts 9 Projects" folder was being synchronized using GoogleDrive -- NOT a good idea, and this might have been the reason for the initial corruption! So we disabled that folder from being synchronized.

Comments

Thank you so much, Mark!