I have Trados Studio 2021 SR2 - 16.2.12.9338.
Every month I import an xliff package from client's World Server to translate.
This time, when I try to import, in the Preparing Package for Import stage, I get the "Object reference not set to an instance of an object" error and cannot import the package for translation. I tried creating a new package from the WS and got the same result. I tried restarting Trados, same result.
How do I fix this so that I can translate the files?
Thanks.
Teresa
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
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?
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?
Translate
