"TranslationProviderThrewException" error in Studio 2015

Hi everyone

I've got a 10000 word project I need to complete by Wednesday and currently the Studio 2015 doesn't want to allow for SDL Language Cloud or Google Translate pre-translations.
The TM file that was supplied with the project is minute, so it's not helping much.

I have tried the options in thread http://www.proz.com/forum/sdl_trados_support/241441-translationproviderthrewexception_error_when_analyzing_pretranslating.html, but it's not helping/relevant to what I'm seeing.

Please could someone help me.
Many thanks,
Nathanael

Parents Reply Children
  • Hi Paul

    With "MT results in the editor window interactively" I assume mean the live lookups that appear when you click into the next target segment. I currently have the TM, Language Cloud and Google Translate added and selected as my MT options.

    When Google Translate is added is gives the following error message:

    "An error has occurred whilst using the translation provider Google Translate. The remote server returned an error an error: (403) Forbidden."

    When I attempt a full-scale pre-translate with all 3 of the above MT options selected, I get the following error message:

    I'm currently using a SDL Trados Studio 2015 (Trial) version, build 12.0.4996.3

    I'm hoping to get my licence tomorrow. I don't know whether that will change anything.

    I've tried creating and using Google Translate API's for both Server and Browser and the same things happens.

    The other two options for creating Google Translate API's, viz. Android and iOS, don't seem to fit the category for the type of software Trados Studio is.

  • It sounds as though your problem lies entirely with using Google Translate. Maybe try these things:

    1. Check your API key for Google is correct
    2. Try it without using Google at all

    Regards

    Paul

    Paul Filkin | 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