Error message

MultiTerm is unable to create the termbase. Not a valid file name 
OR
MultiTerm is unable to create the termbase. [Path] is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

when opening a WorldServer package in Trados Studio originating from a project whose project name contains Asian or other non-Unicode language characters (for instance the German "umlaut" or Russian characters), or a project containing source files with file names in non-Unicode characters. Renaming the WSXZ package will not help.

Workaround 1:
To be able to open the WSXZ package in Trados Studio on your computer, change the OS language to a non-unicode language (i.e. Russian or Chinese, depending on which characters were used in the project or file names) and restart the computer. Then try again.

Workaround 2:
Change the file default Studio project settings path to NOT include a folder that contains non-ASCII characters (or rename that folder)

Workaround 3:
Remove the TBX file (or other Multiterm-related files or folders) from the WSXZ package by following these steps:

1- Rename the *.WSXZ package to *.zip
2- Extract it to a folder with the same name. You can use any archive tool like WinRar, Winzip or 7Zip.
3- Open the folder. You will see the files and folders belonging to the WSXZ package.  Remove the TBX file and the xcs.xml file. Example:



4- After removing the 2 files, now select the remaining files and folders and “zip” them. If you use 7Zip, select all files and folders, right-click and select Add to archive using the same file name. For instance  “tasks_PROJECT_1401_EN-EL_projectname_el_GR_trados.wsxz.zip”. You can also give it a different name if you want.

5- Finally, rename the zip file to file extension *.wsxz:  tasks_PROJECT_1401_EN-EL_projectname_el_GR_trados.wsxz

6- Go to Trados Studio and open the fixed package without Term Database. No error will appear.

Note: you can export the Worldserver Term Database from WorldServer (TBX format) and use the Glossary Converter App to convert it to *.sdltb format. You will then be able to open the TermBase in Trados Studio and add it to your Worldserver projects' settings. This way, you will still be able to use the Term Recognition feature in Studio.

Workaround 4
If the issue is related to the WorldServer project or any file name containing special characters, as a WorldServer Administrator, cancel the project in WorldServer and create a new one using a project or file name with non-Unicode characters and re-export the package.

While the issue happens with a WorldServer package, this failure is entirely unrelated to WorldServer. MultiTerm is the non-Unicode application here. If you try to create a local termbase with a folder in the path that contains non-ASCII characters, like this for example: 

C:\Users\rhopley\Documents\WorldServer\Projects\tasks_タグマスタ180411依頼

and try to open it in Trados Studio, it will fail with this message:



In the example above, the filename is valid, but I have a folder with Japanese characters in it. That is what causes the error, although the termbase name and file name are ASCII only.