Unable to Generate Target Translations - Lost 3 Weeks of Work!

Question

Hi all, 
 I'm in big trouble! I completed translating a 30K words file in Studio 2015, and now I can't generate the target file to deliver to the client. The source is ".xlf". Import and translation went fine, but when I select "Generate Target Translations" I receive the following error: "Collection was modified; enumeration operation may not execute." 
 I tried the follwing steps: 1. Create a new project from the original .xlf and apply the translation memory. Works fine until I want to create the target translations: same error as above 2. Create a new SDLXLIFF only from the original .xlf (via "Open Documents") and apply the translation memory. Works fine until I want to create the target translations: same error as above 3. Create a new SDLXLIFF only from the original .xlf (via "Open Documents") without my TM, then just select "Copy All Source to Target" to populate the target segments. And even then I'm not able to create the translated file. Same error as above. 
 I'm lost. I can't believe that I have worked for the bin for 3 weeks! I mean, I didn't do anything fancy with the file. I did not join or merge segments or anything like that. And after having tried steps 2 and 3 above, it is quite obvious that Studio can't handle the file, but does tell me so only when it's too late! 
 Is there any way/workaround I can use to create my translations??? I don't even want to think about what to tell my client, if I have to start from scratch, in a different tool. 
 Thanks and regards, Stefan

Paul · Answer

Hi Stefan, 
 
First off, can you open the XLF without pretranslating it and just save the target immediately (use the translate single document approach for this). If you can't do that then we need to see the source and figure out why not. 
 
If you can, then once the file is open, add your TM, pretranslate and see if the file will save. Sometimes doing this as opposed to working through the Project will recover a file. 
 
If you still can do it, can you send me the fully translated sdlxliff and the original source and I'll be happy to take a look and try to recover the target for you. 
 
Regards

Paul · Answer

ok - can you send me the XLF and the fully translated sdlxliff? pfilkin@sdl.com

Paul · Answer

The issue in all these cases seemed to be an unsegmented xlf to begin with. So if you can achieve this and then pretranslate you may be able to resolve the problem. You may have to ask your client to do it.

Paul · Answer

I mean the original XLF needs to be fully segmented. If it's not then Studio will attempt to complete it and may do this in a different way to that expected as it has no idea where the original came from. If iot's fully segmented to start with then there shouldn't be a problem. This is most likely why you can't save the target even when you just open the XLF and save immediately. It's a good check to round trip files, especially large ones, before you start translating as this is the way to find out early if there will be a problem. If you don't know the file won't save then Studio won't either until you try it. 
 
In the other cases once the files were offerred as fully segmented XLF then they worked. So I'm obviously guessing as you can't share the file, but without seeing it I can't think what else may help. Perhaps someone else will have an idea. Even if I ask our support team they will ask for the source file.

Trados Studio > 1. Trados Studio

Unable to Generate Target Translations - Lost 3 Weeks of Work!