Error "Could not load file or assembly 'Sdl.MultiTerm.Client.Terminology.UI, Version=17.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888' or one of its dependencies." when opening WorldServer package

Hi Folks,

Problem as stated. This is a showstopper. Two packages from the same client, neither will open.

My Trados and MultiTerm are bang up to date with all patches and services packs installed:

  • Studio: Trados Studio 2022 SR1 - 17.1.8.17828
  • MultiTerm: MultiTerm 2022 SR1 - 17.1.2.2434

I suspect it's a backwards-compatibility issue as my MT is way ahead of the client's version.

Any other ideas?

Thx,

Ed

emoji
  • Hello Ed,

    I understand that you're having trouble opening WorldServer packages in Trados Studio 2022 SR1. This issue might be due to a compatibility problem with MultiTerm. Here's a step-by-step guide to help you resolve this issue:

    Step 1: Close your Trados Studio and MultiTerm applications if they are currently running.

    Step 2: Visit the RWS AppStore and look for the latest WorldServer Compatibility Pack for Trados Studio.

    Step 3: Download the compatibility pack. When prompted to select your Trados Studio version, choose 17.1.8.17828 (2022 SR1) and proceed.

    Step 4: Once the download is complete, you will receive a file named "WorldServer Components.zip". Unzip this file.

    Step 5: Ensure that your Trados Studio 2022 SR1 is not running. Double click on the installer named "WorldServer Components.msi" and proceed with the installation. This process should only take a few seconds.

    Step 6: After the installation is complete, reopen your Trados Studio 2022 SR1. You should now be able to open WorldServer packages without any issues.

    If the problem persists, it might be a good idea to check the version of MultiTerm used by your client. If their version is significantly older, it might be causing compatibility issues.

    I hope this helps! If you have any other questions, feel free to ask.

    Best regards,

    RWS Community AI

    emoji
  • Hi Trados AI,

    That was indeed the right answer. Both packages imported once I downloaded the update for WorldServer compatibility.

    I'm impressed ;-)

    Thx,

    Ed

    emoji