Error using DeepL Translation Provider Plugin

Hello!

I have not been able to add the DeepL MT translation provider in Studio to my active translation memory list in a project. It fails to activate.

I have tried removing and re-installing the plugin several times.

The error message is (in Spanish, the exact words may be different in English): "The translation memory provider "DeepL Translation provider" could not be opened and has been deactivated".

I have a subscription and a valid API Key.

The same configuration seems to work fine in my old PC.

I am using Trados Studio2021 SR2 - 16.2.8.9097 and the version of the plugin is Version 5.8.26.0 for Studio 2021.

Thanks in advance for pointing me in the right direction, since I do not know where to look for the problem.

emoji
Parents
  • Hello

    The latest version of Studio is Trados Studio 2021 SR2 - 16.2.9.9198 not that it should matter.

    Please can you clarify, when you launch the  DeepL app and you want to authenticate your API, is the API field empty or populated?

    We are aware of an issue whereby it works if you have a pre-populated API key but then you include a space then immediately remove the space (basically update the API key field)
    Does that work for you?

    Another area to look into is C:\Users\[username]\AppData\Roaming\SDL\SDL Trados Studio\Studio16 where you have some bin files.
    One of them is TranslationProviderCredentialStore.bin

    Looking forward to your update

    Lyds

    Lydia Simplicio | RWS Group

    _______
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • Thanks, Lydia.

    I updated my Studio version (I did not notice that I had not checked for updates after installing in a new PC!) just in case, but Deepl does not get enabled anyway, same problem.

    The API field is populated with a new API key I copied and pasted from my DeepL account, and the key does not seem to be the problem (if you input an incorrect key, a red error notice comes up).

    I do have two different bin in my Studio 16 folder, TranslationProviderCredentialStore.bin and TranslationProviderCredentialStore.bin2 (I suppose the two different API keys I tried were store...).

    I removed all the rest of the plugins I had installed, plus all the TMs I was meaning to use in the same project, and I also changed the interface language to English, just to try,  to no avail.

    Any other ideas will be very much appreciated!

    Adela

    emoji
Reply
  • Thanks, Lydia.

    I updated my Studio version (I did not notice that I had not checked for updates after installing in a new PC!) just in case, but Deepl does not get enabled anyway, same problem.

    The API field is populated with a new API key I copied and pasted from my DeepL account, and the key does not seem to be the problem (if you input an incorrect key, a red error notice comes up).

    I do have two different bin in my Studio 16 folder, TranslationProviderCredentialStore.bin and TranslationProviderCredentialStore.bin2 (I suppose the two different API keys I tried were store...).

    I removed all the rest of the plugins I had installed, plus all the TMs I was meaning to use in the same project, and I also changed the interface language to English, just to try,  to no avail.

    Any other ideas will be very much appreciated!

    Adela

    emoji
Children