Members not able to access Project in Paratext 8

Question

We have recently migrated some of our projects from Paratext 7.5 to Paratext 8.
Last day, I received complaint from team members in two projects, that they are not able to access their projects in Paratext 8 after the migration process.
I removed their ids from ‘Users, Roles and Permissions’ and added them again, still it is not working.
Send and Receive is working for them, they are getting other resources and projects and firewall is not blocking any connections.

When I went to Paratext registry and checked the Project, I saw the following information.

Registration type: Translator Edition
Issued: 7/12/2017
Expires: never
Paratext GUID: ****
On Send/Receive server: Yes

But when I went to the Members tab, it has only my name, whereas Paratext 8 shows other users in ‘Users, Roles and Permissions’.
https://registry.paratext.org/projects/*******#members

I have also done S/R from my system several times, still the project is not accessible for team members.

Shall I take a backup, revoke the registration for old project and create a new project and add them? Or is there any other solution?

anon242407.

较早的帖子 - 以原始语言显示

Answer 1

Following up what anon397352 just shared - I checked with the developers and here is what anon397352 is referring to.

Close Paratext before making any changes to files outside of Paratext.

In the PT8 project settings.xml file there should be a line that look like this (do a search for ParatextRegistry):

<ParatextRegistryId>9ShqWKRH9hwzFbKhR</ParatextRegistryId>

You can find the Id by going to registry.paratext.org and selecting the project. When the project is selected you will see the Id in the address at the top of the window:

https://registry.paratext.org/projects/3cyuAtBkPEqkZSnMQ

So, for this language (a sample) the id code is: 3cyuAtBkPEqkZSnMQ

If the ParatextRegistryId is missing from the settings.xml file, then you should add it, save the file, and then do a Send/Receive with Paratext.

较早的帖子 - 以原始语言显示

Comments

Thanks @anon848905.

I have edited the PT8 project settings.xml file (added the missing line) and now it is working.

Thanks,

anon242407.

较早的帖子 - 以原始语言显示

---

Today I also experienced this problem. This happened to a new project that was created for a translator and registered correctly. When he added other team members, they never saw the project when they did the S/R.

I opened Settings.xml and there was no entry. I created it and put in the correct info per the instructions. It still would not show up in the other team member’s S/R.

I then looked at a known good Settings.xml file and compared it to the failing project Settings.xml file. The one that failed also was missing an entry named

I put in that line and got the GUID from the registry.

Then I had to go back to Users, Roles, and Permissions. It reported an error from the local computer and the Paratext Registry. It now only showed the Administrator. All the team members who had been added were no longer listed. I added them in and did a S/R and now the project would show as New in the other users S/R.

So grateful for this tip!
anon291708

较早的帖子 - 以原始语言显示

---

There is missing information in your email, probably the most important
part for others. It may have been stripped out.

. The one that failed also was missing an entry named ???

Blessings,

Shegnada J.

Language Technology & Publishing Coordinator, SIL Nigeria

Complex Script Layout Specialist, GPS Dallas

Skype: Shegnada.james.

([Phone Removed]

较早的帖子 - 以原始语言显示

---

Yes, I did it via the web page and it must have interpreted this as some code and hid it. I will try it again via an email.

Repeated with the obscured information entered without xml markers:

Today I also experienced this problem. This happened to a new project that was created for a translator and registered correctly. When he added other team members, they never saw the project when they did the S/R.

I opened Settings.xml and there was no entry ParatextRegistryId. I created it and put in the correct info per the instructions. It still would not show up in the other team member's S/R.

I then looked at a known good Settings.xml file and compared it to the failing project Settings.xml file. The one that failed also was missing an entry named Guid

I put in that line and got the GUID info from the registry.

Then I had to go back to Users, Roles, and Permissions. It reported an error from the local computer and the Paratext Registry. It now only showed the Administrator. All the team members who had been added were no longer listed. I added them in and did a S/R and now the project would show as New in the other users S/R.

So grateful for this tip!

    anon291708</p>

• On 8/23/2017 4:08 PM, Shegnada J.
  wrote:

Shegnada

August 23

There is missing information in your email, probably the most important

                part for others. It may have been stripped out.</p>

. The one that failed also was missing an entry named ???

Blessings,

Shegnada J.

Language Technology & Publishing Coordinator, SIL Nigeria

Complex Script Layout Specialist, GPS Dallas

Skype: Shegnada.james.

([Phone Removed]

---

Visit Topic or reply to this email to respond.

---

In Reply To

anon109032

August 23Today I also
experienced this problem. This happened to a new
project that was created for a translator and
registered correctly. When he added other team
members, they never saw the project when they did the
S/R. I opened Settings.xml and there was no entry. I
created it and put in the correc…

---

Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

较早的帖子 - 以原始语言显示

Answer 2

anon242407,

Make sure that the names being used by the PT8 registrations are correct. If when the users were registered for PT8 the PT7 codes were not used then there will not be a link to the names as in PT7. Make sure that the correct user names are being used in PT8.

The next question that comes to my mind is - how were the migrations done? Did one person migrate the project? After the migration was done did everyone else do a S/R? If the migration has failed and editing has not been done in Paratext 8 yet then I would suggest that you delete the project completely from Paratext 8 (make sure it is removed from the computer, server and registry) and then do the migration again.

In PT7, make sure that everyone has done a S/R and that the names are correct. Then one person should do the migration and everyone else should do a S/R when that is complete. Verify that the Users, Roles and Permissions are correct.

较早的帖子 - 以原始语言显示

Comments

Hi,

I had this problem twice with two of the projects that I was migrating. It seems that the Settings.xml file for the project was missing the Paratext registry ID. The Paratext support people gave me the correct registry id for the project and told what to add to the settings.xml file (one additional line) and then a send/receive fixed the problem.

I don’t know if this is the same problem with your project though.

anon397352

较早的帖子 - 以原始语言显示

Answer 3

I also have someone who is experiencing this problem. Here is their report (Baraka Lewa is the user)

Baraka works with Chonyi Project (CNT). His Paratext 8 is not able to open my projects/resources in Paratext via FileàOpen project/resource. The error we get says:

Paratext cannot perform this operation because a file (unknown) is missing.

Given that other users of CNT (such as myself) are able to do S+R for this project, and it operates normally, what is likely to be the problem?

较早的帖子 - 以原始语言显示

Comments

For that error message, the solution is usually to delete the project from the problem computer and then do send receive to collect it whole again from the server. Does that work?

Get Outlook for Androidhttps://aka.ms/ghei36

较早的帖子 - 以原始语言显示

---

If deleting the project and getting it again is not an option, please have the user use Help > Report a problem shortly after they get the error. The log included with the report should help us track it down and might provide a fix without requiring the user to re-create the project on their machine.

较早的帖子 - 以原始语言显示

---

The problem was solved by deleting a number of resources, one of which must
have been corrupted.

较早的帖子 - 以原始语言显示