• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 2192 views
  • Users 0 members are here
Options
Related

Unexpected exception when configuring file multiFileConverter for task 'Update Main Translation Memories': Failed to create an instance of translation provider... SDL Trados Studio Source: Update Main Translation Memories

Jouni Jakonen

Hi, I wonder if anyone has ideas why the following happens with some of our GroupShare 2017 memories:

 

We are using third party ERP to run translations jobs through Studio and GroupShare, and there are automated work flows that create the projects, Studio packages and run finalizations. With some of our GroupShare memories we get following type of errors in connection with Finalization or Pre-translation and when using Studio template (or so it seems):

 

Exception caught while executing job AutomatedActionsJob: Error during execution of actions: SDL Trados Studio has returned an error. Please read details: SDL Trados Studio Message: Unexpected exception when configuring file multiFileConverter for task 'Update Main Translation Memories': Failed to create an instance of translation provider 'sdltm.groupshare.address/. SDL Trados Studio Source: Update Main Translation Memories:

 

Is this related to the use of API calls and Studio templates? This does not happen always, but seems to be related to certain server memories.

 

Any ideas and comments why this happens?

 

Thanks

Jouni
emoji
Rate translation
×
Suggest better translation
×
  • 0

    Hi Jouni,

    We've come across this error several times already, albeit with file-based memorys.
    The error is remedied by updating/re-indexing the memories, then re-running the job.

    I wonder if the "needs re-indexing" status of a memory can be read via API, which would enable you to catch that error before it happens.

    Best,
    Andreas
    emoji
  • 0 in reply to Andreas Galambos

    Thanks Andreas for your quick response! I actually had used this remedy, and it does help sometimes, but not sure if this is always the case, and I have managed to witness cases where we get the error for one memory and at later point it works (and no updating/re-indexing done), but this is not that exact, so not sure. I found some conversation in other forums regarding this, and in RWS article there is following fix comment: "Fixed an issue where Studio API for project automation failed with error "Failed to create an instance of translation provider" when trying to initialize TM provider. (CRQ-31088) [from: "https://gateway.sdl.com/apex/communityknowledge?articleName=CUs-Studio2022], and I have pending issue regarding this fix with RWS Support and hope to get more information. It is also not clear if this is an issue with GroupShare or Studio, current assumption is that it is related to Studio and API calls.

    Jouni
    emoji
  • 0

    here is the same problem, and quite sporadically.
    The TM is not found. If you start the process again a little later, the process runs cleanly.
    It is not the TM, because it is always reachable. There are also always other languages and/or TMs affected, which work immediately afterwards again without problems.
    The TMs are group share managed. Groupshare does not report any errors, and as said, the TMs are always available and also editable.

    File::Unexpected exception when initializing task 'Analyze Files': Failed to create an instance of translation provider 'sdltm.server/

    This happens sometimes in "Analyze File" and sometimes in "Pretranslate" task.But mostly when analysing files

    We are running Studio 2022 CU7 and GroupShare 2020
    emoji
  • 0 in reply to Markus Wiedenmaier

    was now able to catch this when debugging. 1st run works. 2nd run exception, 3rd run works... 

    Unexpected exception when configuring file multiFileConverter for task 'Pre-translate Files': Failed to create an instance of translation provider 'sdltm.server/ ?orgPath=%2FEN&tmName=TM_de-DE_en-US

    at Sdl.ProjectAutomation.FileBased.AutomaticTasksProcessor.<>c__DisplayClass8_1.<HookUpAutomaticTaskMessageEvents>b__1(Object sender, ExecutionMessageEventArgs args)
    at Sdl.ProjectApi.Implementation.ExecutionResult.OnMessageReported(IExecutionMessage message)
    at Sdl.ProjectApi.Implementation.ExecutionResult.AddMessage(ExecutionMessage xmlMessage)
    at Sdl.ProjectApi.Implementation.ExecutionResult.ReportMessage(String source, String message, MessageLevel level, Exception exception)
    at Sdl.ProjectApi.Implementation.ExecutingTaskFile.ReportMessage(String source, String message, MessageLevel level, Exception exception)
    at Sdl.ProjectApi.Implementation.TaskExecution.ContentProcessingTaskImplementation.TaskFileExecuter.Parse(String targetFilePath)
    at Sdl.ProjectApi.Implementation.TaskExecution.ContentProcessingTaskImplementation.TaskFileExecuter.Execute()
    at Sdl.ProjectApi.Implementation.TaskExecution.ContentProcessingTaskImplementation.RunFileExecuter(Object state)
    at Amib.Threading.Internal.WorkItemsGroupBase.<>c__DisplayClass41_0`1.<QueueWorkItem>b__0(Object state)
    at Amib.Threading.Internal.WorkItem.ExecuteWorkItem()


    Failed to create an instance of translation provider 'sdltm.server/. => Source: Sdl.ProjectAutomation.FileBased
    Index was outside the bounds of the array. => Sdl.Core.PluginFramework

    Here are the messages of the inner exceptions:

    Failed to create an instance of translation provider 'sdltm.server/ ?orgPath=%2FEN&tmName=TM_de-DE_en-US. => Source: Sdl.ProjectAutomation.FileBased
    Index was outside the bounds of the array. => Sdl.Core.PluginFramework