Hello Mark Hamlen ,

Are you using loca/ server based TermBase?

If you disable the Match Repair option in Studio then try to prepare the files, does the issue still persist?

If so- are you able to Create a Single file translation in Studio- open the file and then immediately save as without translating anything?

If there is still a problem at this stage, then it would appear the actual source file is the problem /or there are invalid characters in the sdlxliff.

My termbases are on the local computer. (They are quite large - in six parts because of the size).

I did as you suggested. Turned off all match repair. But the results are still "Object not...." No other explanation. It's not the files, even with the errors reported, I can still open and translate the files and save the files and generate target files. 

But when I open to start the translation, the target segments are completely empty (not even any machine translations or 100% matches).

One thought, though. I am using the "Projects" originally created under 2019 and just changing the "Project Settings" slightly.... I've added the Language Cloud since upgrading. 

Hello Mark Hamlen

Mark Hamlen said:

One thought, though. I am using the "Projects" originally created under 2019 and just changing the "Project Settings" slightly....

This may actually be the cause of the problem.

We don't advise moving projects between versions- but completing an ongoing project in the original version then starting new projects in 2021.

I would create a new project (test) in Studio 2021 using a new template (don't use old templates at all as this allows for all sorts of issues to creep in).

This way you will know if its the actual (2019) projects/templates causing the problem.