There are 2 possible reasons for this error:
Reason 1: You are opening a WSXZ package in Trados Studio 2019 or 2021 from a project using a source or target language with a language code that Trados Studio does not recognize.
Solution: The resolution is to map the WorldServer language code with the Studio language code. Here are some relevant articles with instructions:
WorldServer - Language Tagalog not compatible with Trados Studio - "Invalid language code is detected: tgl-PH" or "The process cannot access the file 'WorldServer_fd949c40-d94d-4a5f-b09f-0d2cc3cf5705.ldb' because it is being used by another process."
WorldServer - Error when saving, exporting or opening a WSXZ package in Trados Studio - Culture name xxxx is not supported.' or 'Culture not supported. Parameter name: name xxxx is an invalid culture identifier'
Reason #2- Term Database attributes with different Internal (API) Name but the same External (UI) Name is created for TD Entry and TD Term on the WorldServer side creating a duplicate that is not "tolerated" by Multiterm. This causes the conversion of the TBX file inside the package to *.sdltb format to fail while opening the package in Trados Studio.
However: The issue should be resolved starting from Trados Studio 2021 with the WorldServer Compatibility Pack for Trados Studio version 16.2.1724. However, if you still encounter this issue in Trados Studio 2021 or 2022, make sure that the root cause is not #1. Anyway; if you can exclude reason #1 and are still encountering the issue, read the following information:
Main resolution to be applied in WorldServer:
This resolution explains how to fix the actual root cause of the issue in WorldServer to prevent the problem from happening again.
Duplicated External (UI) Name and/or Internal (UI) Name for the Applicable Object Types TD Entry and TD Term should be avoided. Note that WorldServer currently allows such duplicates in two different Applicable Object Types. However: this causes issues for Trados Studio since the Termbase definition resulting from such duplicates is not supported in Studio or Multiterm. This is why Trados Studio cannot open a package including a Termbase with such a TermBase definition.
- In WorldServer, go to Management > Administration > Customization
- Next to Custom Component Type, in the drop-down menu, select Attributes
- Search for attributes of Applicable Object Types TD Entry and TD Term and check for duplicate Internal or External Name
- If you find one or more duplicates, rename one of the two names slightly, for instance by adding a "_" to the name
- Once this is done, re-export the affected project or task and open the WSXZ package in Trados Studio
- If the error appears again, you might have missed a duplicate attribute. Check again and repeat the process until the exported WSXZ package can be opened.
Workaround #1 to be able to open the WSXZ package quickly if required:
- Change the WorldServer package file extension from *.wsxz to *.zip.
- Extract the file
- Remove the TBX and the XCS files
- ZIP the content and rename it to *.wsxz
- Open it in Trados Studio.
IMPORTANT: be aware that when applying this workaround, you will remove the Term Database entirely from the package. The Studio project created from the changed package will not contain any Termbase.
After removing the Term Database from the package, you can convert the TBX file inside the exported package to a SDLTB (Multiterm format) Term Database and associate it with the WorldServer Studio project via Project Settings. You need Multiterm Desktop installed on your computer to apply this procedure. Follow the steps described in this article:
How to convert a TBX file from a WSXZ package to SDLTB format to be used in Trados Studio
Workaround #2
This workaround explains how to fix the WSXZ Studio package by keeping the Term Database. Note: this is quite technical, time-consuming and not always easy to apply:
1. Change the WorldServer package file extension from *.wsxz to *.zip.
2. Extract the file.
3. Open xcs.xml file on any text editor.
4. Find the element ' termNoteSpec name ' and 'descripSpec name ', you will see that the value of their dataCatId is the same. For instance 'Term Context' or 'Business Area'.
Note that the element name or type and the dataCatID may vary. What is relevant is that the dataCatID is duplicated.
Here are 2 examples:
termNoteSpec name='termContext' dataCatId='Term Context',
descripSpec name='Term_Context' dataCatId='Term Context'
termNoteSpec name='businessArea' dataCatId='Business Area'
descripSpec name='Business_Area' dataCatId='Business Area'.
5. Change every occurrence of a value of the above elements' attribute 'dataCatId' to any different name, for instance ‘Term Context2’ or ‘Business Area2’.After the change, they will display like this:
termNoteSpec name='termContext' dataCatId='Term Context',
descripSpec name='Term_Context' dataCatId='Term Context2'
termNoteSpec name='businessArea' dataCatId='Business Area'
descripSpec name='Business_Area' dataCatId='Business Area2'.
6. Save and close the XCS file.
7. Compress all of the extracted files to a zip file.
8. Change the zip file name extension to *.wsxz.
9. Open it in Studio. It will open without error.
Please note that there is no need to revert those two elements' dataCatId value to the original state to upload the return package back to WorldServer since the Return package contains only the bilingual translated file and not Termbase file.
