Hello Peggy Lin 

Are you able to add your own Termbases to the project? 

If so, this is possibly due to incorrect characters in the path.

Perhaps this article may help-

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0037824

Hello Steven,

Thanks for your reply. I can add my own termbases to a project without problems. The error I encountered is from a WorldServer Package. The WS Package has to be opened in Trados so as to create a return package, but I can't have the Package opened due to the MultiTerm error. Please see the capture below.

My client could open the packages without issues, and the filenames of Termbases in the opened Packages are like this: WorldServer_b0a3b094-2191-4d46-aed9-3c56026ac621.sdltb.

It would be great if there are solutions to this. Thank you.

Regards,

Peggy

Don't know if this will solve your problem as I've never had it before. I notice in the error message that it's trying to create a termbase with Asian characters in it. You can maybe try this as a workaround.

WorldServer packages can be "unzipped" to a folder using 7-zip, or opened directly in 7-Zip as an archive. If you open it in the Archive Viewer, or whatever's it called, maybe there is a file in there called terminology_data.tbx:

You can either try deleting this file from the archive or perhaps editing the title of the termbase so that Studio can read it. 

Granted, I've never tried this, but maybe it'll work (make a backup of the package first if necessary!)

Good luck!

Don't know if this will solve your problem as I've never had it before. I notice in the error message that it's trying to create a termbase with Asian characters in it. You can maybe try this as a workaround.

WorldServer packages can be "unzipped" to a folder using 7-zip, or opened directly in 7-Zip as an archive. If you open it in the Archive Viewer, or whatever's it called, maybe there is a file in there called terminology_data.tbx:

You can either try deleting this file from the archive or perhaps editing the title of the termbase so that Studio can read it. 

Granted, I've never tried this, but maybe it'll work (make a backup of the package first if necessary!)

Good luck!