0 票
763 次瀏覽

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
image

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

舊文章 - 以原文顯示
Paratext 由 (478 點) 提出
已重新顯示 | 763 次瀏覽

4 個回答

0 票
最佳回答

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.

舊文章 - 以原文顯示
由 [Expert]
(16.7k 點) 提出

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

舊文章 - 以原文顯示
0 票

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.

舊文章 - 以原文顯示
由 [Expert]
(16.7k 點) 提出

I just did. The case number is FB 584389

舊文章 - 以原文顯示
0 票

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.

舊文章 - 以原文顯示
由 [Expert]
(16.7k 點) 提出

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

舊文章 - 以原文顯示

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

舊文章 - 以原文顯示
0 票

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.

舊文章 - 以原文顯示
由 (184 點) 提出

相關問題

0 票
1 個回答 291 次瀏覽
Trying to migrate a back translation project to Paratext 8 and have run into a problem where we get as reason for the ... . The ticket reference is PTXS-17256 Thank you, MSEAIT/LT
MSEAIT_LT 478 提出 已提問 7月 31, 2018
0 票
4 個回答 465 次瀏覽
I have Paratext 8.0.100.4 and FLEx SE 8.3.10.43048 2017/11/09. The Paratext project and FLEx ... system.ArgumentExcpetion CreateLexemeForm.cs:46 Any ideas? Thank you, MSEAIT/LT
MSEAIT_LT 478 提出 已提問 11月 27, 2017
0 票
2 個回答 468 次瀏覽
I have a user who always gets this message on startup (first line translated from French): "The project on your ... window is closed, the error still appears on Paratext startup.
jeffh 1.4k 提出 已提問 11月 22, 2023
0 票
1 個回答 354 次瀏覽
I try to migrate from 7.5 to 8 in in Kuvi project. I try to follow the steps in proper way. I was able to register ... three times still it is showing same. How can I migrate to 8.
anon480013 162 提出 已提問 6月 22, 2017
0 票
1 個回答 393 次瀏覽
I have a user who has a notes project for his consultant checking. He types one or more notes per verse into the ... | Papua New Guinea [Email Removed].pgmailto:[Email Removed].pg
SIL LSS PNG 411 提出 已提問 10月 5, 2017
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
And let us consider how we may spur one another on toward love and good deeds, not giving up meeting together, as some are in the habit of doing, but encouraging one another—and all the more as you see the Day approaching.
Hebrews 10:24-25
3,053 個問題
6,013 個回答
5,677 則評論
2,032 位使用者