• State Not Answered
  • Replies 5 replies
  • Subscribers 48 subscribers
  • Views 887 views
  • Users 0 members are here
Options
Related

Error message "Translation provider threw exception" in Trados Studio 2024 (18.0.2.3255)

Nadine Kontny

Hello,

We are a public service of about 20 translators and we work with Trados Studio since 2009.

First of all, a brief description of how we work: Some weeks ago, we went from SDL Trados Studio 2019 to Trados Studio 2024. All our TMs are server-based and stored on a SDL Trados GroupShare server (GS 2020 SR1). When translating a text, everyone creates a translation project on his own computer and works with an project TM. After finalisation of the project, the server-based TM is updated with the translation.

In the last weeks, some of our translators got the error message “Translation provider threw exception” when they tried to update the main TM with their translation.

We already had this problems some years ago, in 2022, I think. What we did then was upgrade all our TMs (in a pretty complicated way) but it worked and everything ran smoothly again. [We upgraded the TMs like this: export the TM content in a tmx-file; create a file-based TM on C:/; import the tmx-file into this new TM; a small orange triangle appeared with this TM; right click on this TM, then “Upgrade TM”; export the content of this TM in a tmx-file; create a new server-based TM; import the latest tmx-file into this new server-based TM]

Now, the error message has reappeared and we thought we do the same as before and upgrade the TMs again. Perhaps it has something to do with the TM structure of the new version, or you have to do it all x years in order to “refresh” the TMs, who knows…

So, last week, we upgraded all our server-based TMs in the same way than in 2022 and it seemed to work for some days. Unfortunately, the error message has returned and we really don’t know what we could do to solve this problem.

All in all, there are 7 TMs on our server, with various sizes (524,000 units, 136,000 ; 73,000; 53,000; 49,000; 23,000 and 1,000). Perhaps, there is not enough storage space on the server, I have no idea Here’s a screenshot of the system configuration on our server:

Screenshot of a system configuration for Trados Studio showing usage statistics for Project Server, Online Editor, Translation Memory Server, and MultiTerm Server.

We really would appreciate any help you could give us. Many thanks in advance!!

Desperate regards from Belgium,

Nadine

Generated Image Alt-Text
[edited by: RWS Community AI at 1:05 PM (GMT 1) on 7 Apr 2025]
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    "Probability score": 0.8

    "Question improvement suggestion": Please provide the full error message, including any error codes, and specify any recent changes to the system or software. Also, it would be helpful to know if any troubleshooting steps have been taken apart from upgrading the TMs.

    In the meantime, based on the information you have provided, here is a suggested answer to your question:

    Hello Nadine,

    It seems like you're experiencing a recurring issue with the "Translation provider threw exception" error message in Trados Studio 2024. I understand how frustrating this can be, especially when it disrupts your workflow.

    Based on your description, it seems like you've already tried upgrading your TMs, which resolved the issue temporarily. However, since the error has reappeared, it might be due to other factors.

    Here are a few steps you can try:

    Step 1: Run the batch task again. Sometimes, simply retrying can resolve the issue.

    Step 2: Restart Trados Studio and try to run the batch task again.

    Step 3: Try importing the sdlxliff file(s) from the project directly into the TM.

    If the above steps don't work, you can try the following:

    Step 4: Create a new project with the same language pair.

    Step 5: Create a new file-based TM and add it to this project.

    Step 6: Add all the sdlxliff files from the project or projects that the batch task failed on as source files.

    Step 7: Run the batch task "Update Main Translation Memories", making sure you select all the segment statuses you want to be in the TM.

    Step 8: Create a TMX export from this file-based TM and import that TMX into your Trados GroupShare TM.

    Alternatively, you can use the Update Main TM function from the Trados GroupShare Web User Interface. Open the Trados GroupShare Project in the Web User Interface and use the "Download all files" button and select "Include TM Update". Or select the Files you want to, and use the "Download Selected Files" button > "Target version for x files" > "Include TM update".

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

    RWS Community AI
    emoji
  • 0 in reply to RWS Community AI

    Further development of our problems with server-based TMs:

    People still can’t update the main TM on the server.

    What is more, we can’t modify any content in this TM. When we try this (e.g. in order to correct a typing error), the following error message appears:

     Error dialog box in French showing a System.AggregateException with HRESULT -2146233088 and a 500 Internal Server Error.Error dialog box in French with details of an exception including a public key token.

    Error dialog box in French displaying a System.Net.Http.HttpRequestException and a 500 Internal Server Error.Error dialog box in French with details of a System.Net.Http exception including a public key token.

    My next idee was to create a new empty TM on the server (as a temporary working tool for the colleagues until our actual TM is working properly again) but no chance. The same error message pops up, we no longer can create server-based TMs Frowning2.
    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 8:06 AM (GMT 1) on 17 Apr 2025]
  • 0 in reply to Nadine Kontny

    Hi  ,

    I don't know if this is already solved, but have you tried rebooting the server? I seem to recall that we had the same problem and that this helped in our case.

    Best regards,

    Katharina
    emoji
  • 0 in reply to Katharina Schuhmann

    Hi Katharina Schuhmann,

    thanks a lot for your answer.

    We have solved our problem in the meantime, it had indeed something to do with the server. In fact, we've created new containers on the server where we store our TMs and this worked. We've also upgraded all our TMs.

    See also:  RE: "500 (Internal Server Error)" and "Translation provider threw exception" (Trados Studio 2024, SDL Trados GroupShare Server 2020 SR 1) 

    Best regards,

    Nadine 
    emoji
Reply Children