Getting the error "Object referece not set to an intance of an object" when attempting to migrate an auxilliary project

Question

I’ve been helping a user with the registration\migration process. We were able to migrate the actual project as well as a back translation, but when we attempted to migrate an auxilliary translation, we were presented with this error

Can you advise us on how to resolve it? Thank you.

Answer 1

It looks like your My Paratext 8 Projects\languageNameToCode.xml file may have gotten corrupted. Could you e-mail the file to me at [Email Removed] so we can look at it and then delete it (make sure Paratext is not )? Hopefully the migration will succeed after it’s deleted.

Comments

To close the loop, after we deleted the file languaenametocode.xml, we were able to migrate the project

Answer 2

A “Object reference not set…” error is very generic and impossible to diagnose without more details. Please use Help > Report a Problem if it happens again.

Comments

I just did. The case number is FB 584389

Answer 3

Sorry I wasn’t clear, but please use Help > Report a Problem from Paratext 8.0 (ideally right after the error happens). The FB 58438 report that was sent appears to be from Paratext 7.5.

Comments

Help and report in Paratext 8 would not let me associate the problem
with the project as the project doesn’t exist in 8. If it doesn’t
matter, I’ll ask the user to do it again, but pick "it doesn’t apply to
this problem.

Does this send some sort of state of Paratext or other information?

MSEAIT/LT

---

MSEAIT/LT:

Does this send some sort of state of Paratext or other information?

Yes, Paratext logs errors along with other information to help us diagnose problems. That log file is sent to us when using Help > Report a Problem.

---

Okay, we just re-ran the migration on the project (failed again) and then sent the problem report number ptxs-576
Thanks,
MSEAIT/LT

Answer 4

You must make sure P8 is not when you delete My Paratext 8 Projects\languageNameToCode.xml as @anon291708 suggested.

My particular issues were caused by unrecognized language identifiers in the back translation projects. If you correct those before upgrading you will save yourself some hassle.