• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 2 replies
  • Subscribers 48 subscribers
  • Views 1049 views
  • Users 0 members are here
Options
Related

Server-based Translation Memories - Maintenance

Nadine Kontny

Hello,

In our company, all translators work with SDL Trados Studio Professional 2019 SR2. All our TMs are located on a server (SDL Trados GroupShare 2020 SR1). We always work with translation projects to which we connect the server-based TMs.

Recently, serveral colleages have been getting the error message "TranslationProviderThrewException" when they try to update the TM via the Batch task "Update Main translation memories". As we do not find a solution, we want to try to re-index and recompute our server-based TMs.

My question is whether it's possible to perform these tasks while the TM in question is used. Meaning while my colleagues are translating in projects to which the TM is connected.
Or is it preferable to ask all colleagues to disconnect the TMs from their projects before we start the maintenance?

Thank you very much for your help.

Nadine
emoji
Rate translation
×
Suggest better translation
×
  • 0

    Hello Nadine,

    The issue in question was reported as a defect in the older versions of Groupshare 2020, however it should of been fixed in Groupshare 2020 SR1 (which you have) and the latest version of Studio 2019. 
    https://gateway.sdl.com/apex/communityknowledge?articleName=000012095

    You should also consider upgrading to the recent Groupshare 2020 SR1 Cu5 or CU6 as well as making sure you have the latest release of Studio 2019 or 2020 and try again.

    It is safe to run a re-index/recompute during work hours as it shouldn't create to much of an impact. Worst case it would lead to a longer time between getting TU results from the specific TMs. I am however unsure if this will resolve the issue and if the problem remains the same after reindexing and making sure to have latest Studio 2019 version, then it is recommended that you raise a case with support for further investigation on the issue.

    Best regards,
    Sorin
    emoji
  • +1 in reply to Sorin Gurzau

    Hello Sorin,

    Thanks a lot for your reply.
    Yes, an older version of Groupshare could indeed be the problem, I will check with the people responsable for the server...

    Meanwhile, I have dared to run the re-index/recompute tasks and it worked without problems. But it hasn't solved our problem with the error message.

    What I did as well, I've exported the content of the problematic TM, created a local TM and imported the tmx in this TM to see if it worked find. Then I've created a new TM on the server and imported the tmx. I've told all the people who had the error message to test whether they could upload their projects to the newly created TM, and it worked :-) So far there have been no more error messages. No idea if this is the final solution to our problems, but for the moment it works. If the message comes up again, we'll probably really have to contact the SDL support...

    Kind regards,

    Nadine
    emoji