Migration of Back Translation fails

Question

The Back Translation is setup correctly in PT7 and primary translation migrated fine.

Error Message: “Object Reference not set to in Instance of the object. If you are unable to resolve this problem, contact your support…”

I ran the project verify in PT7 and there were no errors found.

Answer 1

No, I think the problem can be worked around. I think there might be a couple issues here.

The first is that the project in question is not set as a back translation project. To have this work correctly in Paratext 8.0, I think it would be best if the project was first changed to be a back translation of the correct base project in Paratext 7.x. This can be done by changing the setting at Project > Project Properties and Settings > General tab > Type of project.

However, I don’t think that problem is causing the exception.

I was able to migrate your project just fine, so I think the exception is caused by a bad value in the C:\My Paratext 8 Projects\languageNameToCode.xml file. Could you try deleting this file to see if that fixes the migration problem?

Answer 2

Please use Help > Report a problem right after it happens to report this issue to us.
It’s unlikely to be a problem with your project.

Answer 3

I did report the problem

Answer 4

If this is likely a software issue, then I assume it may take a while and I should delete the PT7 primary project and have them continue in PT7 for now. Correct?
listentwice

Answer 5

It wasn’t originally a BT but I changed it to a BT and then did a S/R.

Today I went back and double checked the Project Settings says it is a BT.

Answer 6

I will attempt to go back on Monday and delete that file and try again. I’m not sure how long they are in town.

Is it a problem that you are seeing it still as a Std Translation, but I see it as a Back Translation?

Comments

listentwice:

Is it a problem that you are seeing it still as a Std Translation, but I see it as a Back Translation?

No, I probably just pulled the wrong repository off the S/R server (I couldn’t tell who was the admin).

EDIT: I just verified that that was the issue. I pulled the admin’s copy and it is a back translation. But that also means that I migrated the wrong copy, so I’m trying again.

EDIT 2: The migration still worked with the correct copy, so I still think it’s likely to be a problem with that file.

Answer 7

I deleted that file and migration was successful. Thanks!

Any idea what caused the bad value in that file?

Comments

Unfortunately, I don’t have any ideas. It probably would have been better if I had told you to rename it and send the bad file to us to look at.