Trados 2022 SR1 Api Automatic Task (Pre-translation) failure: Unexpected exception when configuring file multiFileConverter for task 'Pre-translate Files': Failed to create an instance of translation provider.

Question

I am able to successfully PreTranslateFiles using a file-based TM using SDK API Trados 2022 17.0.0.11594. 
 namespace Sdl.Sdk.PreTranslateFiles
{
 using System;
 using Sdl.Core.Globalization.LanguageRegistry;
 using Sdl.ProjectAutomation.Core;
 using Sdl.ProjectAutomation.FileBased;
 public class PreTranslateFiles
 {
 public void Create(
 string SdlProjectFilepath,
 string SdlTargetLanguage
 )
 {
 FileBasedProject ThisSdlProjectObject = new FileBasedProject(SdlProjectFilepath);
 this.RunAutomaticTask(ThisSdlProjectObject, SdlTargetLanguage);
 ThisSdlProjectObject.Save(); 
 }
 private void RunAutomaticTask(FileBasedProject ThisSdlProject, string TargetLanguageCode)
 {
 ProjectFile[] targetFiles = ThisSdlProject.GetTargetLanguageFiles(LanguageRegistryApi.Instance.GetLanguage(TargetLanguageCode));
 AutomaticTask preTranslate = ThisSdlProject.RunAutomaticTask(targetFiles.GetIds(), AutomaticTaskTemplateIds.PreTranslateFiles);
 }
 }
} 
 However, when using SDK API Trados 2022 SR1 17.1.6.16252 , although other AutomaticTasks (ConvertToTranslatableFormat, CopyToTargetLanguages), the PreTranslateFiles fails. 
 Checking the SDLPROJ file (Tasks), I can see the error: 
 Unexpected exception when configuring file multiFileConverter for task 'Pre-translate Files': Failed to create an instance of translation provider. 
 I have checked that the TM is uplifted/re-indexed, and also tried a different TM, however it still fails with the same error. 
 Can anyone offer any troubleshooting tips? 
 Thanks

Patrick Andrew Hartnett · Accepted Answer

Hi Samuel Baldus , thx for sharing your code and being available for a sync/meeting yesterday to align/demonstrate these issues. 
 Here are my latest findings after reviewing this issue. 
 
 Processing automation tasks are successful after adding the binding redirects to the app.config; you also confirmed this. 
 The reason you are seeing the additional Info messages in the console output is because you have choosen to receive and write to std output (console) the processing messages from your app.config. If don't need these, then simply remove the implementation of Log4Net from your project. 
 I confirm that the Info messages that are written to std output do not interfere with the automation tasks themselves + they are not written to the project file. I suspect that the messages that you are seeing in the project file are from an automation execution prior to updating the app.Config file with the binding redirects? Note: If you look/check from you screenshots above, the error messages that are written in the project file are different to info processing messages that are written to console output. 
 
 Can you please check/confirm again with a new project. If the issue persists, we can schedule another sync/meeting.

Community Jira · Answer

An issue has been created on Jira with the internal tracking nr. CRQ-34704

Patrick Andrew Hartnett · Answer

Hi Samuel Baldus , I've been able to reproduce and identify a possible issue with resolving Microsoft.Data.SqlClient, Version=4.1.0.0 with the latest release of Trados Studio SR1 outside of the Studio context (e.g. standalone apps). I'll udpate the documentation with some tips on how to deal with these later on. In the meantime can you please test on your end if adding these binding ridirects to your configuration file resolves the issue?

Trados Studio Developers > Studio Developers Q&A

Trados 2022 SR1 Api Automatic Task (Pre-translation) failure: Unexpected exception when configuring file multiFileConverter for task 'Pre-translate Files': Failed to create an instance of translation provider.

Top Replies