Teresa Sumiyoshi 

Teresa Sumiyoshi said:

Every month I import an xliff package from client's World Server to translate.

As there is nothing such as a "XLIFF package", just to make sure: are you opening a WS package with the ending WSXZ (which may well contain a XLIFF file among others)?

And do you open the package using this button in the Home section of your ribbon?



If yes, when exactly does the error come up? 
Is this happening only with this WS package or also with others?

Does it make a difference whether you set the option to "Generate translation and analysis statistics" or not?

If it happens with other packages, I suggest you (1) reinstall the WorldServer add-on and/or (2) run a RESET of your Studio instance. 

Sorry, my fault for not expressing this properly. It is a WS package ending in WSXZ. I clicked on Open WorldServer Package. I made sure that the box for Custom TM import settings is unchecked and "Generate translation and analysis statistics" is checked (per instructions from my Project Manager, it's the way we've always done it).

Not only do I get the error when opening this month's package, I also get the error when trying to open packages from previous months, which I was able to open in the past.

In the Package Import Preparation stage, it says "[Calculating translation progress]" and then briefly displays something about termbase and then the error is displayed.

I tried uninstalling and reinstalling Trados, but I get the same error.

Per your suggestion, I tried reinstalling the WS add-on - same error. I also did a reset of Studio (renaming the 3 folders). Same error

In this case, I suggest you reinstall the WorldServer add-on. Install the latest version that shows up in the integrated AppStore,

I edited my reply because your response had not yet shown up. I did reinstall the WS add-on. I still get the same error at the same stage

Teresa Sumiyoshi said:

Not only do I get the error when opening this month's package, I also get the error when trying to open packages from previous months, which I was able to open in the past.

What did you change between the time when this function worked and when it started failing?
Did you upgrade your version of Studio? Or of MultiTerm?
Has WS been upgraded on the customer's side?

And just to clarify, I downloaded the latest WS add-on version for Trados 2021 (not the one for Trados 2022). I really appreciate your help, because this is super frustrating. I simply opened a WS package in the same way that I have done every month and for some unknown reason I get this error, even though nothing has changed since last month. My project manager confirmed that he was able to open the package with Trados 2021. My computer, OS (Windows 11), Trados version, etc. are the same as last month, but suddenly I cannot open any WS packages.

I was going to suggest that you send me the package to check if I can open it, but as you say that your PM can open it, the problem is probably not with the package but with your environment. 

If a RESET did not help, I suggest you try a repair of Studio and ideally also of MultiTerm because the problem may be linked to a termbase included in the package (you mentioned that Studio "displays something about termbase" before the error comes up).

Alternatively, just to be able to deliver the job until the problem gets solved, you could extract the SDLXLIFF file from the package (it is a ZIP file), translate it and repack it into the package to be able to deliver.

I was going to suggest that you send me the package to check if I can open it, but as you say that your PM can open it, the problem is probably not with the package but with your environment. 

If a RESET did not help, I suggest you try a repair of Studio and ideally also of MultiTerm because the problem may be linked to a termbase included in the package (you mentioned that Studio "displays something about termbase" before the error comes up).

Alternatively, just to be able to deliver the job until the problem gets solved, you could extract the SDLXLIFF file from the package (it is a ZIP file), translate it and repack it into the package to be able to deliver.

Thank you. I will try a repair as you suggest. (I assume I can google instructions because I don't even know what "MultiTerm" is. I wish I could read whatever flashes on the screen about "termbase", but I've tried multiple times and simply can't read it before it disappears and the error message appears. 

When I search my apps in the Windows Control Panel, there is nothing called MultiTerm. Also, for Studio, it only offers me the option to Uninstall (Modify is greyed out). I don't see anything that offers a Repair choice

MultiTerm Desktop is the application that is used to maintain a termbase. It is usually installed alongside with Studio.

So maybe the problem is that application has disappeared? Is it something that I can find in the Appstore and reinstall?

Unfortunately, Microsoft has created a mess with the new Settings function. It does not show the repair option. It works however if you use the old Control Panel to do this.
The instructions below will help:

PDF

It is not in the AppStore, but in your RWS customer account. You can download the installer from there and simply run it. It does not need any activation key.  
Make sure you install the same version as Studio, in your case 2021.

Found it in my account. Thanks. I will download now. (How did it disappear???)

Ugg. I still get the same message. "[Calculating translation progress]"-> "[Processing termbase... {I can't read quick enough}" -> "Object reference not set to an instance of the object"

So I ran the repair (it offered that option after clicking on uninstall), but I still get the same error message at the same point. I have to leave for an appointment now, but I will be back in a few hours. Thanks again for trying to help.