We have exported a WorldServer Studio package (WSXZ) from our WorldServer environment. Once the translator attempts to open it in Trados Studio, she receives an error like:

'', hexadecimal value 0x02, is an invalid character. Line 54413, position 55.

Note: the type of hexadecimal value will vary. The same applies to the line number and the position.

The reason for the error is that the Terminology file (which is called terminology_data.tbx) inside the WSXZ package contains an invalid character. When Studio attempts to "read" this file and convert it to a Studio Term Database file and associate it to the WorldServer project, it fails to do so.

This is the workaround to fix the package:

1. Rename *.WSXZ package to zip and unzip it to a folder. You will find its content in the folder.
2. Find and open the file terminology_data.tbx with an XML Editor like Notepad ++  and refer to the error message you received in Studio. It will point you to the line where the issue occurs. Following the error provided in this example, it could be line 54413. Once you find that like, you should be able to see the invalid character in Notepad ++



Tip: if you don't want to use Notepad ++ or another XML Editor, a simple way to validate and XML content is to drag and drop the file into a Firefox Browser. In this case, since the file has the format/file extension *.tbx, rename it to *.xml, open Firefox as a Browser and drag the file into it. The validation error will appear, including the reference to the line number and a preview of the affected text. Based on this research, you will be able to find it in the TBX file itself and fix it:



3. Once you have found the affected text, remove the invalid character and save your change. For example, the character might look like this:   or like this - Following these two examples, after removing the invalid character, the words will display as protooncogén and/or proonóstico.
4. Re-run the validation just to be sure that no more errors appear.
5. ZIP all files and folder
6. Rename the ZIP file to *.WSXZ.By doing so, you have re-created the WSXZ package. 
7. Now open the newly recreated WSXZ package. It will work.

To prevent the issue from happening again, the TD entry in WorldServer should be fixed. Follow these steps.

1. In WorldServer, go to the termbase that contains the invalid character and search/find the entry or the affected entry definition text based on the data in the Studio package. If you are not sure which one it is, you can either check which Term Database is associated with the project from which the WSXZ was exported in WorldServer, or you check this property in the TBX file, next to where the invalid character is:

descrip type='td_name'>

for example:

descrip type='td_name'>Marketing Termbase</descrip>

2. Once you have opened the relevant TD from Tools > Term Databases in WorldServer, search for the relevant entry as found in the TBX file. In the Browser, it could look like this:



3. Edit the Entry and remove the invalid character. Note that the invalid character might or might not be visible in the Browser. If it is invisible, remove spaces or characters and re-enter them manually. It might also be part of a Term Entry Note. If so, you should be able to see it and remove it, as in the example above (#2)
4. Save your change in the TD Entry
5. Perform a new export to a WSXZ package and confirm that it can be opened in Trados Studio without error.