Batch Task “Pretranslate”/ ”Word Count” API call fails randomly

Question

After migrating to Trados Studio 2021 from SDL Trados Studio 2017, we have come across the following major issue in the implementation of our automated processes (using the Trados public APIs): 
 Batch Task &ldquo;Pretranslate&rdquo;/ &rdquo;Word Count&rdquo;: randomly fails with the following exception : 
 &ldquo;Unexpected exception when configuring file multiFileConverter for task 'Word Count': Failed to create an instance of translation provider 'sdltm.XXX/ 
 &ldquo;Unexpected exception when configuring file multiFileConverter for task 'Pre-translate Files': Failed to create an instance of translation provider 'sdltm.file:///P:/PathToTheTM/nameOfTheTm.sdltm'..&rdquo; 
 
 This issue has been replicated on our side using a simple Filebased Project with 2 simple docx translatable files, an empty FileBased TM while running the batch task &ldquo;Pretranslate&rdquo; on a loop. 
 
 As you can see, this problem occurs both with FileBased and ServerBased TMs. 
 Through trial-and-error, we have noticed the following: 
 
 The problem occurs only with projects that have more than one translatable file. 
 The problem does not occur if the batch task is applied for each translatable file separately. 
 The problem will occur after running the task a couple of times. The first few times the task is run, there is no issue. 
 Once the problem occurs, it keeps occurring until either a long time has gone by or the PC is rebooted (even if after the problem occurs we try to run the batch task for each file separately). 
 
 Details of the Exception fetched From Visual Studio: 
 System.IndexOutOfRangeException 
 HResult=0x80131508 
 Message=Index was outside the bounds of the array. 
 Source=Sdl.Core.PluginFramework 
 StackTrace: 
 at Sdl.Core.PluginFramework.ObjectRegistry`2.CreateObjects() 
 
 This exception was originally thrown at this call stack: 
 Sdl.Core.PluginFramework.ObjectRegistry<TExtensionAttribute, TExtensionType>.CreateObjects() 
 
 This is a serious issue with a major negative impact on our productivity. Can anyone from RWS give me an official answer on what to do? This was working perfectly fine until the upgrade to Trados 2021. Is this going to be fixed soon on an upcoming update? Is there a way to circumvent the problem in the meantime? 
 Thank you in advance! Paul Andrea-Melinda Ghisa

Emanuel Albu · Answer

Hi, Theodoros Kastanis !

I added this code sample in which I automatically create projects from different folders using a template and place them all, pretranslated, in a new location.

The way to use the app is by adding the following command line arguments when calling it:

.\PretranslateProjectsCreatedFromTemplateSample.exe "<pathToTemplate>" "<pathToFolderWithTranslatatableFiles>" ... "<pathToFolderWithTranslatatableFiles>" "<pathToWhereTheProjectsWillBeCreated>" "<numberOfTimesTheOperationWillBeDone>" "s"

You can add as many folders containing translatable files as you wish between the template path argument and the destination folder argument.

The issue is not reproducible in this sample anymore.

See if there's something different in the sample and add it to your code to test whether the issue still persists.

Emanuel Albu · Answer

Hello Theodoros Kastanis ! 
 
 Unfortunately, it seems like a workaround will have to do for now. 
 
 We discovered a similar issue for another team recently, but we were unable to identify the root cause after a preliminary investigation. Until we have more concrete information, we recommend the following workaround. 
 
 Introduce a fail-safe action to automatically restart the process of running the project automation tasks when it discovers a failed attempt. This should open a new instance of the project and not use the same instance of the project with the failed attempt. 
 
 You can find a code sample for this here .

Daniel Brockmann · Answer

Just as an update here for everyone, this was tracked as CRQ-30444 and was addressed in Studio 2022 SR1 CU7 and higher. Another robustness fix was done for Studio 2022 SR2 (in December 2023). So hopefully this has been addressed in the meantime.

Patrick Andrew Hartnett · Answer

Hi Theodoros Kastanis thank you for your feedback and the sample project; appreciated. 
 Theodoros Kastanis said: I am not quite sure if the code sample was supposed to be working as is, since I found some “bugs” that I had to fix in order to successfully run it. 
 Can you please create a PR with the bug fixes that you applied against the public project example on github that Emanuel Albu provided to you? It isn't often that we get third-party developers wanting to get involved, contributing to the sample projects, with the objective of helping other developers in solving problems/ workarounds. 
 
 Theodoros Kastanis said: I am under the impression that the time required for the resolution of such a serious bug is not properly investe 
 Although I understand your frustration in not having a solution or workaround to resolve this -> contrary to what you are suggesting, we have reorganized our priorities to review the problem you are reporting. 
 
 Theodoros Kastanis said: I will repeat myself and remind you that the fact that the same bug -referenced in a previous message of mine- was reported almost seven months ago and no resolution was found makes me very very nervous. 
 We are reviewing the issue you have reported here, in these days. Have you reported this same issue in another form on the community; pls add the link here for reference. 
 
 Theodoros Kastanis said: Until the full resolution of the bug, a workaround that works is mandatory. 
 'Mandatory' might be a poor choice of wording here, unless you are ordering us to provide you with a workaround. Are you ordering us to provide you with a workaround? 
 
 Let's recap to understand where we are: 
 
 We reviewed the problem that you presented, given the conditions you disclosed about your process. 
 We have been able to reproduce the problem in at least one occasion where the proposed solution by Emanuel Albu resolved the issue. 
 We presented this as a potential solution so that you could confirm if it resolves the problem on your system 
 You have reported that the proposed solution doesn't resolve the problem on your system. 
 
 Correct? 
 
 My Review: 
 I have taken time this evening to review this issue, using your sample project and confirm that I can reproduce the same issue you are reporting. Sometimes it occurs once, other times all the time. I don't see a work around for this without reviewing the abstract levels from the Trados Studio solution. 
 For now, I will escalate this issue to the Studio Team, but it might be that we pick this up and collaborate with the Studio team to resolve. We'll circle back to you once we have more concrete information. 
 + Daniel Brockmann , Robert Cornea 
 Reproducible on Trados Studio 2021 SR2+ and 2022 
 
 Tech Notes: 
 After reviewing the sample project that you provided above, I would recommend to include the execution of the batch task within an iteration of the project target languages, as follows: 
 var targetLanguages = studioProject.GetProjectInfo().TargetLanguages;
foreach (var targetLanguage in targetLanguages)
{
	var targetFiles = studioProject.GetTargetLanguageFiles(targetLanguage);
	var task = studioProject.RunAutomaticTask(
 targetFiles.GetIds(), AutomaticTaskTemplateIds.PreTranslateFiles);
	//[...]
} 
 Note: this will not solve the problem you have discovered, but will enable you to separate execution of the batch tasks by target language.

Lydia Simplicio · Answer

Hi Theodoros Kastanis 
 Having the complete stack trace error would be helpful. Can you please save it to this post for further assessment. 
 In the meantime, I have moved this post to the relevant teams for their attention. 
 Regards 
 Lyds

Patrick Andrew Hartnett · Answer

Hi Theodoros Kastanis , 
 Thank you for reporting this issue. 
 I have added an item on our board to followup + attempt to reproduce given the conditions that you have provided above. I will circle back to you when I have more information. 
 Internal Tracking id: SDLCOM-3739 
 Note: I might reach out to you if I need more input or sample code.

Trados Studio Developers > Studio Developers Q&A

Batch Task “Pretranslate”/ ”Word Count” API call fails randomly

Top Replies