Hello David Adams ,

Could you please post the full error stack please- as this error on its own is very generic.

The following article explains what information we need to be able to try and help

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/4159/how-to-get-help-quickly-in-the-sdl-community-technical-forums

Hello David Adams ,

Could you please post the full error stack please- as this error on its own is very generic.

The following article explains what information we need to be able to try and help

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/4159/how-to-get-help-quickly-in-the-sdl-community-technical-forums

Hello Steven,

Many thanks for the response to my query that you posted.

I apologise for not responding sooner to this posting from you. I did attempt to send you an answer, but I'm not sure that I used the correct protocol. I hope I have got it right now (after reading the "How to Get Help Quickly" article that you suggested I should look at. I have put an @ followed by your name at the top of this message, in the hope that that is what is needed.

My response included the error stack, but again my attempts to attach it were not necessarily successful and I finally copied and pasted it into the body of my message.

What would be the best way to proceed? Should I start the whole process again, perhaps?

Best regards,

David

David Adams

David Adams said:

My response included the error stack, but again my attempts to attach it were not necessarily successful and I finally copied and pasted it into the body of my message.

The easiest way to attach the stack trace is to save it as a file to your desktop and then attach the file.  If you save it in a text file and give it an xml extension it is rendered nicely so we can read it easiily.

However, having said all of that it probably won't help much as you still need to deal with the problem of getting your target file out.  

To troubleshoot files try this article:

How to troubleshoot problematic files : gateway.sdl.com/.../communityknowledge

More often, the solution to these problems is resolved like this:

• Open the source file again using the "Translate Single Document" process
• Save it to create a single file project
• Try to save target now before you do anything.
• If it works go onto the next step, but if it doesn't then you need to consider the more advanced trouble shooting steps in the KB article
• Pretranslate the file using your Translation Memory
• Save the target file

If none of that helps, and if you are allowed to share the file you can send me the fully translated sdlxliff and the original source file and I'll happily take a look.

Regards

Paul
pfilkin@sdl.com