When trying to open the target translation in Microsoft Word of a document translated using Studios new in Microsoft Word 2007-2016 file type the following error is thrown:

We're sorry. We can't open E_target.docx because we found a problem with its contents.
The name in the end tag of the element must match the element type in the start tag.
Location: Part: /word/document.xml, Line X, Column: Y


 

Solution: Install Cumulative Update 5 for SDL Trados Studio 2015 SR2

SDL development addressed this issue in the Cumulative Update 5 for SDL Trados Studio 2015 SR2. We recommend that you install the Cumulative Update 5 (or higher) via the Check for Updates feature in SDL Trados Studio 2015 in the Help tab > Check for Updates.

If for any reason the automatic update feature is not working, you can download the latest Cumulative Update for SDL Trados Studio 2015 from our Knowledge Base:

Note: After you installed the Cumulative Update 5, you need to re-translate/open the source document with, preferable with the Translation Memory that already contains the translation units from the translation you made.

Workaround 1: Use "old" Microsoft Word File Type

Use the old Microsoft Word 2007-2013 file type instead of the new Microsoft Word 2007-2016 file type.

1. Open Studio and go to File > Options > File Types
2. Deactivate the new Microsoft Word 2007-2016 and activate the old Microsoft Word 2007-2013 file type in your settings.
3. Re-import the Document for translation via File > Open > Translate Single Document
4. Run the Batch-Task PerfectMatch so as not to lose any potential translations you have already made before noticing the issue.

Workaround 2: Remove Content Controls

If Solution 1 one die not solve the issue remove all content controls in the source document.

1. Open the source document in Microsoft Word
2. Remove all content controls by right clicking on them and selecting Remove Content Control
   
   
3. Once all content controls are removed, re-import the document for translation
4. Run the Batch-Task PerfectMatch so as not to lose any potential translations you have already made before noticing the issue.

This is a known issue where the problem is caused by a corrupt content control element, that leads to an invalid document.xml in the target DOCX to be create.
SDL development addressed this issue in the Cumulative Update 5 for SDL Trados Studio 2015 SR2.

If you work in SDL Trados Studio 2015 (which is not supported anymore), we recommend that you upgrade to Studio 2017 or 2019.

If for any reason you it is not possible to install upgrade, you can follow the workarounds described in the Resolution section.

Problem persists?

• If you have a valid Support and Maintenance contract: log into your SDL Customer Gateway and log a support request.
• If you do not have a Support and Maintenance contract but a Licensing or Installation issue: log your request also via the SDL Customer Gateway Portal and select the Licensing and/or Installation option in the form.

Technical issue but no PSMA?

• If you do not have a Support and Maintenance contract BUT encounter a technical issue, create a post via the SDL Community. In the SDL Community users help users and can answer/comment no problems you encounter.

Cannot find path in the resolution steps?

If you not see the files and folder path mentioned in this article it is an indication that you cannot see hidden files and folders. Please refer to following KB article for enable the view of hidden files and folders:

• Showing hidden files, folders and extensions on Windows operating systems