Hello all, I had this same problem except it was happening with one file that was part of a project I created locally on my computer. The file path names were not long and they did not contain any characters except an underscore. All four of the files have the underscore in the file name, but only one of the files got the error when trying to "Generate target translation" and also using the "Export files" option. The files open for editing without issue. 

The only thing that sets that one file apart is that I merged a few segments in it. I resolved the issue by adding a "-2" to the file name and adding it to the project as if it were a new file. The TM then filled in the matches, and I simply didn't merge the segments this time. It exports just fine now, so in my case this is clearly an issue with Studio (I'm using the 2022 version, fully updated) and merged segments. Not the first time I've had issues with merged segments. I've saved the error details if anyone wants to take a look.

Hello all, I had this same problem except it was happening with one file that was part of a project I created locally on my computer. The file path names were not long and they did not contain any characters except an underscore. All four of the files have the underscore in the file name, but only one of the files got the error when trying to "Generate target translation" and also using the "Export files" option. The files open for editing without issue. 

The only thing that sets that one file apart is that I merged a few segments in it. I resolved the issue by adding a "-2" to the file name and adding it to the project as if it were a new file. The TM then filled in the matches, and I simply didn't merge the segments this time. It exports just fine now, so in my case this is clearly an issue with Studio (I'm using the 2022 version, fully updated) and merged segments. Not the first time I've had issues with merged segments. I've saved the error details if anyone wants to take a look.