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

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
×
Parents
  • 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
Reply
  • 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
Children
No Data